Changes by Kuba Wieczorek faw...@gmail.com:
Removed file: http://bugs.python.org/file12420/zipfile_extract_dirs_r2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4710
Kuba Wieczorek faw...@gmail.com added the comment:
Here is a revised version of the patch with directories support for
write(). It works like UNIX zip program so if a directory path is passed
to the function, it stores only the directory itself (without the contents).
This time without tests
Changes by Kuba Wieczorek faw...@gmail.com:
Removed file: http://bugs.python.org/file12433/zipfile_dirs_support.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4710
Changes by Kuba Wieczorek faw...@gmail.com:
Added file: http://bugs.python.org/file12435/zipfile_dirs_support.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4710
New submission from Kuba Wieczorek faw...@gmail.com:
This behaviour has been known of course for quite long time. I suppose
this is not intentional so I've played a bit with this and I hope you'll
consider some little change.
Currently, if a ZIP archive contains some subdirectories
Kuba Wieczorek faw...@gmail.com added the comment:
I'm not sure if it would make sense to save current
extract()/extractall() behaviour and implement new with another function
because current one is simply faulty. And if it's about BC breaks then
well... it may be introduced in 3.0 line, I think
