➜
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.
Created on 2009-11-16 18:28 by mark.dickinson, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg95356 - (view) | Author: Mark Dickinson (mark.dickinson) *  |
Date: 2009-11-16 18:28 | |
In Python 2.x we have: >>> "%.0d" % 0 '' >>> "%.0d" % 0L '0' In Python 3.x: >>> "%.0d" % 0 '0' I think the 2.x behaviour for int comes directly from C's sprintf behaviour: section 7.19.6.1, p8 of the C99 standard says: "The result of converting a zero value with a precision of zero is no characters." I'm not sure which the more sensible behaviour is, but in 2.x, int and long should behave in the same way. Fixing long to behave like int seems both simplest and least likely to break existing code. |
|||
| msg95567 - (view) | Author: Terry J. Reedy (terry.reedy) * |
Date: 2009-11-20 21:25 | |
I agree with the 'should' (behave same way), but changing nothing will break no code. Given that the purpose of 2.7 is to aid 3.x migration, an argument could be made for matching the 3.x behavior. |
|||
| msg113561 - (view) | Author: Mark Dickinson (mark.dickinson) * |
Date: 2010-08-10 21:34 | |
Out of date for 2.x. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:54 | admin | set | github: 51584 |
| 2010-08-10 21:34:40 | mark.dickinson | set | status: open -> closed resolution: out of date messages: + msg113561 |
| 2009-11-20 21:25:50 | terry.reedy | set | nosy:
+ terry.reedy messages: + msg95567 |
| 2009-11-16 19:23:34 | mark.dickinson | set | title: int/long discrepancy when formatting zero with ".0d" -> int/long discrepancy when formatting zero with "%.0d" |
| 2009-11-16 18:28:38 | mark.dickinson | create | |