Thanks. I think I can live with that restriction. :-) I do not read/write to the same zip file in the same process. Anthony On Mon, May 5, 2014 at 4:10 PM, Gregory P. Smith <greg at krypto.org> wrote: > > On Mon, May 5, 2014 at 2:52 PM, Anthony Tuininga < > anthony.tuininga at gmail.com> wrote: > >> On Mon, May 5, 2014 at 3:50 PM, Paul Moore <p.f.moore at gmail.com> wrote: >> >>> On 5 May 2014 22:32, Anthony Tuininga <anthony.tuininga at gmail.com> >>> wrote: >>> > So my question is: can I safely make use of this "feature"? It has >>> remained >>> > in place since at least Python 2.6 but I don't want to assume anything. >>> > Please advise! Thanks. >>> >>> I believe this is a 100% supported feature of Python (since 2.6, as >>> you mention). Some of the zip import/run features have unfortunately >>> been underdocumented, and I suspect that this is simply one of those. >>> >>> Paul >>> >> >> That's great news. Thanks! >> >> Anthony >> > > There is at least one caveat to using a .zip file for the standard > library: http://bugs.python.org/issue19081 > > Never change the .zip file in use by a running process. > > -gps > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140505/c20f2aa2/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4