zip module password

[Michele Petrazzo]

Is there a method for add a password to a file created by zip module?

Thanks,
Michele

 

[Peter Hansen]

Is there a method for add a password to a file created by zip module?

This link
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=698833&group_id=5470
suggests that there is no such support in the standard zipfile module
yet, but that a patch has been available for some time (but has
not yet been accepted).

Google found this, and other notes on the topic...

-Peter

 

[Giovanni Bajo]

This link
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=698833&group_id=5470
suggests that there is no such support in the standard zipfile module
yet, but that a patch has been available for some time (but has
not yet been accepted).

"has not yet been *commented*" or even looked at would be more appropriate. In
fact, it is no wonder that it is my sole contribution to Python -- I found the
lack of responsiveness so depressing.

 

[Thomas Heller]

"has not yet been *commented*" or even looked at would be more appropriate. In
fact, it is no wonder that it is my sole contribution to Python -- I found the
lack of responsiveness so depressing.

Here's one possible way to push it further:

http://mail.python.org/pipermail/python-dev/2004-October/049495.html

Thomas

 

[Giovanni Bajo]

Here's one possible way to push it further:
http://mail.python.org/pipermail/python-dev/2004-October/049495.html

I am sorry for Martin, but this looks like total bullshit to me. I am *not*
qualified to review Python patches because I am not a Python developer. If I
review 10 patches, my work could be totally useless, if not even dangerous for
Python itself. I could easily miss blatant bugs, suggest wrong things,
understand interface decisions wrong. It would be a total waste of time for me;
plus, some real Python developer would have to double-check my work, because it
would be completely fool for them to just blindly trust my reviews. And if they
carefully double-check my work, they could spend that very time by reviewing
the patches themselves.

Usually, you get involved in development by submitting small patches, getting
reviews and comments, learning by your errors, and understanding things as you
go. If the only way to get a review is to produce 10 reviews out of *no*
experience, you do not have time to learn. Plus, it is really surprising to me
that the Python team is so developed-starved to ask random people whose
experience is totally unknown to review patches on their behalf.

If they need more developers, they could stop improving Python for some months,
just how long it takes them to review all those patches. Nobody would scream
and they might end up with a bunch of new wannabe developers to help them.

 

[Fredrik Lundh]

In fact, it is no wonder that it is my sole contribution to Python -- I found the
lack of responsiveness so depressing.

if you want people to use your modified zip module, wrap it up and make it
available via PyPI:

http://www.python.org/pypi

if you have other contributions, wrap them up and post them to PyPI. the
"I'll only contribute to the standard library" approach doesn't work.

</F>