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 ezio.melotti, lars.gustaebel, pbienst
Date 2010-01-15.13:14:28
SpamBayes Score 4.1692096e-05
Marked as misclassified No
Message-id <1263561270.0.0.451273813189.issue7693@psf.upfronthosting.co.za>
In-reply-to
Content
I suppose you do not have a real problem here. I thought your problem was that you want to use unicode pathnames as input and output to tarfile. You don't need that.

You want to transfer an archive from one system to another. You can do that with tarfile already. Python 3.x's tarfile does the same as Python 2.x's tarfile, except that in 3.x *all* strings are unicode strings.

If you have different encodings on these systems, that should not be a problem unless these encodings are not compatible with each other. If you want to use a tar archive created on a utf-8 system on a iso-8859-1 system that is no problem, as long as you use the pax format and all the utf-8 characters used are also valid iso-8859-1 characters.
History
Date User Action Args
2010-01-15 13:14:30lars.gustaebelsetrecipients: + lars.gustaebel, pbienst, ezio.melotti
2010-01-15 13:14:29lars.gustaebelsetmessageid: <1263561270.0.0.451273813189.issue7693@psf.upfronthosting.co.za>
2010-01-15 13:14:28lars.gustaebellinkissue7693 messages
2010-01-15 13:14:28lars.gustaebelcreate