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 lars.gustaebel
Recipients jaraco, lars.gustaebel, python-dev, terry.reedy, vstinner
Date 2011-12-25.11:26:25
SpamBayes Score 1.3621787e-10
Marked as misclassified No
Message-id <1324812386.49.0.433530613029.issue13639@psf.upfronthosting.co.za>
In-reply-to
Content
I think we should wrap this up as soon as possible, because it has already absorbed too much of our time. The issue we discuss here is a tiny glitch triggered by a corner-case. My original idea was to fix it in a minimal sort of way that is backwards-compatible.

There are at least 4 different solutions now:

1. Keep the patch.
2. Revert the patch, leave everything as it was as wontfix.
3. Don't write an FNAME field at all if the filename that is passed is a unicode string.
4. Rewrite the FNAME code the way Terry suggests. This seems to me like the most complex solution, because we have to fix gzip.py as well, because the code in question was originally taken from the gzip module. (BTW, both the tarfile and gzip module discard the FNAME field when a file is opened for reading.)

My favorites are 1 and 3 ;-)
History
Date User Action Args
2011-12-25 11:26:26lars.gustaebelsetrecipients: + lars.gustaebel, terry.reedy, jaraco, vstinner, python-dev
2011-12-25 11:26:26lars.gustaebelsetmessageid: <1324812386.49.0.433530613029.issue13639@psf.upfronthosting.co.za>
2011-12-25 11:26:25lars.gustaebellinkissue13639 messages
2011-12-25 11:26:25lars.gustaebelcreate