This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | eric.smith |
|---|---|
| Recipients | eric.smith |
| Date | 2008年03月17日.03:06:53 |
| SpamBayes Score | 0.038341187 |
| Marked as misclassified | No |
| Message-id | <1205723214.61.0.782969937957.issue2264@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think the best way to handle this is to add a new format code to PyOS_ascii_formatd, which implements this behavior. There can be no backward compatibility issues, because PyOS_ascii_formatd currently ensures its format specifier type code is in ['e', 'E', 'f', 'F', 'g', 'G', 'n']. I'm going to use 'Z' (for lack of a better code) to mean "implement the default behavior from PEP 3101". |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月17日 03:06:54 | eric.smith | set | spambayes_score: 0.0383412 -> 0.038341187 recipients: + eric.smith |
| 2008年03月17日 03:06:54 | eric.smith | set | spambayes_score: 0.0383412 -> 0.0383412 messageid: <1205723214.61.0.782969937957.issue2264@psf.upfronthosting.co.za> |
| 2008年03月17日 03:06:53 | eric.smith | link | issue2264 messages |
| 2008年03月17日 03:06:53 | eric.smith | create | |