Message150260
I just took a look as the 3.2 tarfile code and see that it always (because self.name is always unicode) does the same encoding, with 'replace', referencing RFC1952. Although there are a few other differences, they appear inconsequential, so that the code otherwise should behave the same. Reading further on codec error handling, I gather that my previously understanding was off; non-Latin1 chars will just all appear as '?' instead of raising an exception. While that is normally useless, it does not matter since the result is not used. So I agree to call this fixed. |
|
Date |
User |
Action |
Args |
2011-12-26 07:46:51 | terry.reedy | set | recipients:
+ terry.reedy, jaraco, lars.gustaebel, vstinner, python-dev |
2011-12-26 07:46:51 | terry.reedy | set | messageid: <1324885611.67.0.916792501152.issue13639@psf.upfronthosting.co.za> |
2011-12-26 07:46:51 | terry.reedy | link | issue13639 messages |
2011-12-26 07:46:50 | terry.reedy | create | |
|