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 gvanrossum
Recipients gvanrossum, kristjan.jonsson, loewis, terry.reedy
Date 2009-01-16.17:33:26
SpamBayes Score 0.343288
Marked as misclassified No
Message-id <1232127209.42.0.93716124871.issue4927@psf.upfronthosting.co.za>
In-reply-to
Content
I think this is my fault.  I should have used the proper repr() of the
filename in the repr() of a file object from the beginning, then this
wouldn't have been a problem.

I think we should let this rest for Python 2.x (except for fixing the
test suite).  Fortunately this is gone in 3.x for any number of reasons.

Here's my "proof" that we should let it rest.

If nobody were parsing the repr() of file objects, then we could easily
fix this.  However, the reason this was brought up in the first place is
that people *are* parsing file object repr()s.  So now fixing it would
create backwards compatibility problems.  I'd rather live with an
inconsistency (until 2.x is dead) than introduce more backwards
incompatibility into 2.7.
History
Date User Action Args
2009-01-16 17:33:29gvanrossumsetrecipients: + gvanrossum, loewis, terry.reedy, kristjan.jonsson
2009-01-16 17:33:29gvanrossumsetmessageid: <1232127209.42.0.93716124871.issue4927@psf.upfronthosting.co.za>
2009-01-16 17:33:27gvanrossumlinkissue4927 messages
2009-01-16 17:33:26gvanrossumcreate