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 rhettinger
Recipients christian.heimes, gvanrossum, nascheme, noam, rhettinger, tim.peters
Date 2007-12-18.10:25:42
SpamBayes Score 0.0054882383
Marked as misclassified No
Message-id <1197973543.87.0.869201515539.issue1580@psf.upfronthosting.co.za>
In-reply-to
Content
Right, there are plenty of exceptions to the suggestion of exactness. 
Still, I find the current behavior to be more helpful than not 
(especially when trying to explain the examples I gave in the previous 
post).

I'm concerned that the tone of the recent discussion shows a strong 
desire to just get something checked-in despite dubious benefits and 
despite long standing invariants.

It is a bit cavalier to declare "we can give up float(repr(x)) == x 
across different platforms."  Our NumPy friends might not be amused. If 
a PEP on this were circulated, I'm sure we would receive some frank and 
specific feedback.

Likewise, I find it questionable that shorter reprs are helpful. Is 
there any evidence supporting that assertion?  My arguments above 
suggest short reprs are counter-productive because they mask the cause 
of problems that might otherwise be self-evident.  Of course, it's 
possible that both could be true, short reprs may help in some cases 
(by masking oddities) and may hurt in other cases (by masking the 
underlying cause of an oddity or by making a false psychological 
suggestion).
History
Date User Action Args
2007-12-18 10:25:43rhettingersetspambayes_score: 0.00548824 -> 0.0054882383
recipients: + rhettinger, gvanrossum, tim.peters, nascheme, christian.heimes, noam
2007-12-18 10:25:43rhettingersetspambayes_score: 0.00548824 -> 0.00548824
messageid: <1197973543.87.0.869201515539.issue1580@psf.upfronthosting.co.za>
2007-12-18 10:25:43rhettingerlinkissue1580 messages
2007-12-18 10:25:42rhettingercreate