[issue10631] ZipFile and current directory change

2020-06-02 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue10631] ZipFile and current directory change

2020-06-02 Thread Zackery Spytz
Zackery Spytz added the comment: Python 2 is EOL, so I think this issue should be closed. -- nosy: +ZackerySpytz ___ Python tracker ___

[issue10631] ZipFile and current directory change

2017-03-24 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- priority: normal -> low versions: -Python 3.3, Python 3.4 ___ Python tracker ___

[issue10631] ZipFile and current directory change

2015-02-05 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Fixed in issue14099 for 3.5. Do you think that this solution should be backported Martin? An alternative solution of this issue would be to convert relative path to absolute path in ZipFile constructor. -- versions: -Python 3.2

[issue10631] ZipFile and current directory change

2012-12-03 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The patch from issue14099 is intended to fix this issue. -- nosy: +alanmcintyre ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10631 ___

[issue10631] ZipFile and current directory change

2012-12-02 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- components: +Library (Lib) nosy: +serhiy.storchaka versions: +Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10631

[issue10631] ZipFile and current directory change

2012-12-02 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10631 ___

[issue10631] ZipFile and current directory change

2010-12-12 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: So, Martin, are you then arguing that this should in fact be considered a bug in ZipFile? The documentation for the constructor says Open a ZIP file, where file can be either a path to a file (a string) or a file-like object. Reading

[issue10631] ZipFile and current directory change

2010-12-11 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10631 ___ ___ Python-bugs-list

[issue10631] ZipFile and current directory change

2010-12-05 Thread Hirokazu Yamamoto
New submission from Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp: Is this intended behavior? Creating zipfile.ZipFile with relative path and changing current directory, relative path is resolved from new directory not from the directory object was created. F:\py3k Python 3.2a4+ (py3k, Dec 3

[issue10631] ZipFile and current directory change

2010-12-05 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: I don't know, but I wouldn't call it a bug either. In general it's not recommended to change the current directory except at the very beginning of your application. -- nosy: +pitrou ___ Python tracker

[issue10631] ZipFile and current directory change

2010-12-05 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: More formally: it's unspecified. I'd like to propose this general principle: If you pass a relative path to some library that gets stored in the library, it's unspecified whether the cwd is consider at the point of passing the path or at

[issue10631] ZipFile and current directory change

2010-12-05 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: So, Martin, are you then arguing that this should in fact be considered a bug in ZipFile? The documentation for the constructor says Open a ZIP file, where file can be either a path to a file (a string) or a file-like object. Reading