[issue37064] Feature request: option to keep/add flags to pathfix.

2019-09-06 Thread Patrik Kopkan
Change by Patrik Kopkan : -- pull_requests: +15371 pull_request: https://github.com/python/cpython/pull/15717 ___ Python tracker <https://bugs.python.org/issue37

[issue37064] Feature request: option to keep/add flags to pathfix.

2019-08-27 Thread Patrik Kopkan
Change by Patrik Kopkan : -- pull_requests: +15225 pull_request: https://github.com/python/cpython/pull/15548 ___ Python tracker <https://bugs.python.org/issue37

[issue37064] Feature request: option to keep/add flags to pathfix.

2019-05-27 Thread Patrik Kopkan
Patrik Kopkan added the comment: Example: pathfix.py -i /usr/bin/python ./directory --> would change the shebang of every script in this directory recursively to #! /usr/bin/python. That's handy but if you would have script like this: #! /usr/bin/env -flags and wanted to keep the fl

[issue37064] Feature request: option to keep/add flags to pathfix.

2019-05-27 Thread Patrik Kopkan
Change by Patrik Kopkan : -- keywords: +patch pull_requests: +13497 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13591 ___ Python tracker <https://bugs.python.org/issu

[issue37064] Feature request: option to keep/add flags to pathfix.

2019-05-27 Thread Patrik Kopkan
New submission from Patrik Kopkan : Hello, Pathfix is nice simple tool for changing shebang lines. However, it is lacking a way how to keep/add flags making this tool impractical sometimes. -- messages: 343622 nosy: pkopkan priority: normal severity: normal status: open title: Feature

[issue36458] Compile errors --without-threads

2019-03-27 Thread patrik
patrik added the comment: Not a problem. I wanted to record the issue just in case someone else encounters it, and also because there seems to have been a history of issues with the no-threads option. Happy to hear its sorted in 3.7

[issue36458] Compile errors --without-threads

2019-03-27 Thread patrik
New submission from patrik : Compiling python 3.6.8 configured with --without-threads (no other options) fails, with undefined references to PyGILState_GetThisThreadState in pylifecycle.c, and PyGILState_Ensure and PyGILState_Release in object.c. I used Louis' fix from issue #247

[issue13487] inspect.getmodule fails when module imports change sys.modules

2017-09-16 Thread Patrik Simons
Patrik Simons added the comment: I cannot reproduce. In fact I cannot even get list(d.items()) to raise RuntimeError: dictionary changed size during iteration for any dict d. -- ___ Python tracker <https://bugs.python.org/issue13

[issue13487] inspect.getmodule fails when module imports change sys.modules

2017-08-07 Thread Patrik Simons
Patrik Simons added the comment: list(sys.modules.items()) still raises RuntimeError: dictionary changed size during iteration when another thread imports a module. I would assume dict.copy() is thread-safe so a working fix could use sys.modules.copy().items() I hit this bug when printing

[issue1116520] Prefix search is filesystem-centric

2016-12-25 Thread Patrik Iselind
Patrik Iselind added the comment: Is it enough to include everything in the Lib folder, excluding __pycache__, site-packages and the test folder in Lib? Would that be representative enough? Patrik Iselind Den 2016-12-25 kl. 17:31, skrev Brett Cannon: > Brett Cannon added the comm

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: OK, for now. Let's disregard my idea that stderr is swallowed. At some point these test might have worked under coverage. I was more thinking to bisect cpython. Perhaps i can find a revision that works. Patrik Den 24 dec 2016 20:26 skrev "Ned

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: @nedbat, do you know of a revision where coverage doesn't influence the tests? If so, which one? Perhaps i can perform a bisect search to find when this went bad. I'm testing the latest tip/head. So that's one par

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: Sure, here you go. $ ./python ../coveragepy debug sys -- sys --- version: 4.3a0 coverage: ../coveragepy/coverage/__init__.py cover_dirs: /home/irina/patrik/coveragepy

[issue29047] Where are the test results stored?

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: My GitHub PR got closed. So closing this issue as well. -- resolution: -> rejected status: open -> closed ___ Python tracker <http://bugs.python.org/i

[issue1116520] Prefix search is filesystem-centric

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: What about the performance penalty for zipping stdlib? is it significant? When would you like to zip stdlib? For embedded systems with limited disk space? Patrik Iselind On Sat, Dec 24, 2016 at 6:34 PM, Patrik Iselind wrote: > > Patrik Iselind add

[issue1116520] Prefix search is filesystem-centric

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: How much smaller would the stdlib for 3.5 become if you compress it with zip? -- nosy: +patriki ___ Python tracker <http://bugs.python.org/issue1116

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: I'd like to clarify that the file i just attached, no-stderr.diff, is in no way a suggestion for a fix. It's just my way of conveying what i see. -- ___ Python tracker <http://bugs.python.o

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: For clarity, this is what i get in the test_exceptions test when i've applied the attached diff. $ ./python -m test -v test_exceptions == CPython 3.7.0a0 (default:8e311f109b22, Dec 24 2016, 12:26:43) [GCC 5.4.0 20160609] == Linux-4.4.0-53-generic-x

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: yes, I'm sure. i printed markings around where the text should have been. Patrik Den 24 dec 2016 17:37 skrev "Ned Batchelder" : > > Ned Batchelder added the comment: > > Are you sure the code that tried to print to stderr was ev

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: report doesn't contain any text when run under coverage. something made the text not appear... Patrik Den 24 dec 2016 16:39 skrev "Patrik Iselind" : > > Patrik Iselind added the comment: > > i use the latest code. perhaps somethi

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: i use the latest code. perhaps something for introduced after 3.6? Patrik Den 24 dec 2016 13:51 skrev "Ned Batchelder" : > > Ned Batchelder added the comment: > > I doubt very very much that coverage.py is stealing stderr. Many many &g

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: I've been looking into test_exceptions, why it fails. The reason seems to be that when the tests are executed under coverage, then they get nothing on the line that says the following in test_unraisable(). ```python report = stderr.getvalue() ``` So cov

[issue29048] Coverage influence tests, make some of them fail

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: As an example, the difference for test_exceptions: $ ./python ../coveragepy run --pylib --source=exceptions Lib/test/regrtest.py test_exceptions Run tests sequentially 0:00:00 [1/1] test_exceptions Exception ignored in: .BrokenDel.__del__ of .BrokenDel object

[issue29047] Where are the test results stored?

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: Cannot figure out how to add the link to the GitHub PR field. Adding link here instead. https://github.com/python/devguide/pull/88 -- ___ Python tracker <http://bugs.python.org/issue29

[issue29047] Where are the test results stored?

2016-12-24 Thread Patrik Iselind
Changes by Patrik Iselind : -- pull_requests: -7 ___ Python tracker <http://bugs.python.org/issue29047> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29047] Where are the test results stored?

2016-12-24 Thread Patrik Iselind
Patrik Iselind added the comment: Made a pull request for this -- pull_requests: +7 ___ Python tracker <http://bugs.python.org/issue29047> ___ ___ Python-bug

[issue29047] Where are the test results stored?

2016-12-22 Thread Patrik Iselind
Patrik Iselind added the comment: Great, thanks! Patrik Den 22 dec 2016 15:01 skrev "Eric V. Smith" : > > Eric V. Smith added the comment: > > https://github.com/python/devguide/blob/github/runtests.rst > > -- > nosy: +eric.smith > > ___

[issue29048] Coverage influence tests, make some of them fail

2016-12-22 Thread Patrik Iselind
Patrik Iselind added the comment: The fixes for test_ssl and test_subprocess seem strange to me. All they do is sweep the messages under the rug. Then there is not really any point with the 'with' block, is there? Without coverage those tests passed so i cannot really see how th

[issue29048] Coverage influence tests, make some of them fail

2016-12-22 Thread Patrik Iselind
Patrik Iselind added the comment: Are the tests that altered the execution environment something to bother with at all? Perhaps something for another issue? -- ___ Python tracker <http://bugs.python.org/issue29

[issue29047] Where are the test results stored?

2016-12-22 Thread Patrik Iselind
Patrik Iselind added the comment: Is this something we could clarify in the docs? I'd like to try and dip my toes in this. Where can i find the source for https://docs.python.org/devguide/runtests.html ? -- ___ Python tracker

[issue29046] Coverage related documentation missing

2016-12-22 Thread Patrik Iselind
Patrik Iselind added the comment: Agree -- resolution: -> not a bug status: open -> closed ___ Python tracker <http://bugs.python.org/issue29046> ___ ___

[issue29048] Coverage influence tests, make some of them fail

2016-12-22 Thread Patrik Iselind
New submission from Patrik Iselind: I checkout the latest tip from scratch. When i run the tests i get the following results: % ./python -m test -j [...] 376 tests OK. 1 test altered the execution environment: test_site 27 tests skipped: test_bz2 test_ctypes test_curses test_dbm_gnu

[issue29046] Coverage related documentation missing

2016-12-22 Thread Patrik Iselind
New submission from Patrik Iselind: Is it possible to do coverage -j8 or similar? Cannot find any documentation on this. Coverage takes so long on the tests... I checked https://docs.python.org/devguide/coverage.html -- assignee: docs@python components: Documentation messages: 283824

[issue29047] Where are the test results stored?

2016-12-22 Thread Patrik Iselind
New submission from Patrik Iselind: I cannot find any documentation on where the test results are stored. Looked at https://docs.python.org/devguide/runtests.html -- assignee: docs@python components: Documentation messages: 283825 nosy: docs@python, patriki priority: normal severity

[issue27978] Executor#shutdown with timeout

2016-09-06 Thread Patrik Dufresne
New submission from Patrik Dufresne: Would be nice to add a new parameter to timeout if the shutdown take too long. def shutdown(self, wait=True, timeout=None): with self._shutdown_lock: self._shutdown = True self._work_queue.put(None) if wait

[issue21009] Potential deadlock in concurrent futures when garbage collection occurs during Queue.get

2016-09-06 Thread Patrik Dufresne
Patrik Dufresne added the comment: I've encounter this issue. To easily avoid this issue, I've change `queue.put(None)` to `queue.put(None, block=False)` to work around this. -- nosy: +Patrik Dufresne ___ Python tracker <http://bu

[issue14119] Ability to adjust queue size in Executors

2016-09-06 Thread Patrik Dufresne
Patrik Dufresne added the comment: Any update on this subject ? Also had to monkey patch the implementation to avoid consuming all the system memory. -- nosy: +Patrik Dufresne ___ Python tracker <http://bugs.python.org/issue14

[issue26269] zipfile should call lstat instead of stat if available

2016-02-02 Thread Patrik Dufresne
New submission from Patrik Dufresne: To mirror the behavior in tarfile, zipfile should make a call to stat instead of lstat if available. Failure to do so resolved into an "IOError No such file or directory" if the filename is a symbolik link being broken. As such, the creation of t

[issue26253] tarfile in stream mode always set zlib compression level to 9

2016-01-31 Thread Patrik Dufresne
New submission from Patrik Dufresne: When using tarfile.open(mode='w|gz'), the compression level is hard-coded to 9. Seed _Stream._init_write_gz(): self.zlib.compressobj(9, 1. In regards to zlib, I would start by replacing the value of 9 by zlib.Z_DEFAULT_COMPRESSION. This is t

[issue24110] zipfile.ZipFile.write() does not accept bytes arcname

2016-01-30 Thread Patrik Dufresne
Patrik Dufresne added the comment: Manage to work around this issue by using surrogateescape for arcname and filename. For me it's no longer an issue. -- ___ Python tracker <http://bugs.python.org/is

[issue23252] Add support of writing to unseekable file in zipfile

2016-01-30 Thread Patrik Dufresne
Patrik Dufresne added the comment: While this path provide support to create Zip file for non-seekable stream. It doesn't support reading a file from a non-seekable stream. -- nosy: +Patrik Dufresne ___ Python tracker <http://bugs.py

[issue25997] Tarfile.add with bytes path is failing

2016-01-03 Thread Patrik Dufresne
Patrik Dufresne added the comment: It's a bit tricky, but with help of surrogateescape I get the expected result. I'm closing this bug. Thanks -- status: open -> closed ___ Python tracker <http://bugs.pytho

[issue25997] Tarfile.add with bytes path is failing

2016-01-02 Thread Patrik Dufresne
Patrik Dufresne added the comment: > Is the tarfile module designed to support bytes for file names in general? > The documentation doesn’t seem to mention bytes anywhere relevant. This seems > more like a new feature rather than a bug to me. I'm using bytes in Unix to represen

[issue10757] zipfile.write, arcname should be allowed to be a byte string

2016-01-02 Thread Patrik Dufresne
Patrik Dufresne added the comment: This bug is very old, any development on the subject. This issue is hitting me trying to port my project (rdiffweb) to python3. It received a lot of broken filename with invalid encoding and I need to create a meaningful Zip archive with it. Currently, it

[issue24110] zipfile.ZipFile.write() does not accept bytes arcname

2016-01-02 Thread Patrik Dufresne
Patrik Dufresne added the comment: I'm converting my project into python3. I'm encountering issue with zipfile encoding. Look like, it only support unicode path. This is a huge issue since path are, by definition, bytes. You may store a file name with an invalid character without is

[issue25997] Tarfile.add with bytes path is failling

2016-01-02 Thread Patrik Dufresne
New submission from Patrik Dufresne: With python 3.4, Tarfile doesn't properly support adding a files with bytes path. Only unicode is supported. It's failing with exception similar to: tar.add(os.path.join(dirpath, filename), filename) File "/usr/lib/python3.4/tarfile.py&