Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue39883>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue38200>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue38938>
___
___
Python-bugs-list mailing list
Unsubscribe:
bbayles added the comment:
I'm currently having difficulty getting either cx_Freeze or PyInstaller to work
with Python 3.8, which is hindering testing. I also no longer have easy access
to a Windows environment.
If I change the implementation to use -m instead of -c would you be able
bbayles added the comment:
Thanks for the note. I've merged in master and fixed a conflict in the test
file.
In an earlier rev I tried to do the argument parsing without ast.literal_eval,
but found it awkward to support all the ways [1] can manifest. You might have a
better idea?
[1
Change by bbayles :
--
pull_requests: +9533
___
Python tracker
<https://bugs.python.org/issue28806>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue34202>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue34182>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
keywords: +patch
pull_requests: +7917
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34182>
___
___
Python-
Change by bbayles :
--
keywords: +patch
pull_requests: +7907
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34179>
___
___
Python-
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue34179>
___
___
Python-bugs-list mailing list
Unsubscribe:
bbayles added the comment:
I realized that the Python 2 solution was adapt-able after all; I've
re-submitted as GitHub PR 8360.
https://github.com/python/cpython/pull/8360
--
___
Python tracker
<https://bugs.python.org/issue34
Change by bbayles :
--
pull_requests: +7895
___
Python tracker
<https://bugs.python.org/issue34132>
___
___
Python-bugs-list mailing list
Unsubscribe:
bbayles added the comment:
I took a shot at this, but closed my PR when I found that it introduced a
different regression.
After playing with it for a bit, I think that this commit [1] is a bit
problematic because it uses lexer.instream.readline(), which can make the line
number
Change by bbayles :
--
keywords: +patch
pull_requests: +7856
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue34132>
___
_
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue34132>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue33939>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
nosy: +bbayles
___
Python tracker
<https://bugs.python.org/issue22454>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by bbayles :
--
keywords: +patch
pull_requests: +7228
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue22454>
___
___
Python-
bbayles <bbay...@gmail.com> added the comment:
I think you'll find that your link points to the exception class `SkipTest`,
which does start with a capital level.
This is distinct from the `skipTest` method of `unittest.TestCase` objects,
which starts with a lowercase
bbayles <bbay...@gmail.com> added the comment:
Is there someone who might be in a position to review the PR? It's pretty short.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +6343
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32362>
___
__
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5964
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32362>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33069>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue30528>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5857
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
bbayles <bbay...@gmail.com> added the comment:
Two things I'm familiar with that should probably be mentioned in the Library
updates:
* bpo-32102: New argument capture_output for subprocess.run
* bpo-21417: Added support for setting the compression level for
zipfile.ZipFile.
-
bbayles <bbay...@gmail.com> added the comment:
da, would you mind if I add a test and a news entry to your patch and submit it
as a Github pull request?
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33034>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue31528>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue28788>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32933>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32974>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32959>
___
___
Python
bbayles <bbay...@gmail.com> added the comment:
I made a comment about that in the pull request that went unchallenged ([1]),
but I'm happy to change it.
[1] https://github.com/python/cpython/pull/5385#pullrequestreview-92055354
--
___
bbayles <bbay...@gmail.com> added the comment:
This was fixed in issue 21417, in Github PR 5385:
https://github.com/python/cpython/pull/5385
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
bbayles <bbay...@gmail.com> added the comment:
This is fixed in 3.7 with the `text` parameter. See GitHub PR 4049:
https://github.com/python/cpython/pull/4049
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://
bbayles <bbay...@gmail.com> added the comment:
I've made a pull request that clarifies things in the docs.
As csabella notes, there are some more differences that could be pointed out.
The 'subcalls' and 'builtins' arguments could be explained as well.
Nonetheless, I think the PR do
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5659
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
bbayles <bbay...@gmail.com> added the comment:
I'm afraid that profile.Profile and cProfile.Profile behave pretty differently,
and there's not a good way to bring the methods from the C version to the
Python version.
The example at [1] shows a cProfile.Profile object being instan
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5626
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32146>
___
__
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5361
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
bbayles <bbay...@gmail.com> added the comment:
In working on a patch I convinced myself that a better change might just be to
document that you can use the *preset* keyword for LZMA compression instead of
*compresslevel*.
--
___
Python tracke
New submission from bbayles <bbay...@gmail.com>:
In [1] (issue 21417), support for setting an archive (or its files) compression
level was added to the zipfile module.
That currently works for the ZIP_DEFLATED and ZIP_BZIP2 compression methods,
but not for ZIP_LZMA. This is because z
bbayles <bbay...@gmail.com> added the comment:
I presume it's too late to get my pull request in for 3.7, but perhaps we could
get a note in the documentation for this before release?
That could be as simple as:
.. warning::
The ``'spawn'`` and ``'forkserver'`` start m
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5232
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
New submission from bbayles <bbay...@gmail.com>:
tarfile.open() allows for specifying both a compression type and a compression
level. However, the compresslevel parameter doesn't work when using the xz
modes.
import tarfile
good_archive = tarfile.open('/tmp/dummy.tar.gz',
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5222
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue21417>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5176
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32304>
___
__
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5175
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32304>
___
__
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5136
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32502>
___
__
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32102>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32502>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
nosy: +bbayles
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32304>
___
___
Python
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5110
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5101
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5049
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
bbayles <bbay...@gmail.com> added the comment:
I ran into this issue, and found references to it on StackOverflow [1] and
GitHub [2] as well. I found that the problem applies to both the 'spawn' and
'forkserver' start methods on Linux.
I made an attempt to implement dancol's fix abo
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5016
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32248>
___
__
Change by bbayles <bbay...@gmail.com>:
--
keywords: +patch
pull_requests: +5015
stage: needs patch -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by bbayles <bbay...@gmail.com>:
--
pull_requests: +5006
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue32248>
___
__
63 matches
Mail list logo