Kevin Hendricks <kevin.hendri...@sympatico.ca> added the comment:

Final patches against the trees make no sense as no developer has decided which 
way they want to actually handle the problem. 

My patch is only one way and I note it may not be the way the owners of the 
code want.

Also, this patch is very straight forward (one hunk) and should apply to 2.6, 
2.7, and 3.1 (although I have not tried it with 3.1) with only line offsets.

So if the owner of this code actually looks that the patch and the bug report 
and makes a decision on how they want to handle this issue and they like the 
patch I have suggested, then I would be happy to diff it against whatever 
zipfile.py versions he/she wants.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10694>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to