Akira Li added the comment:
If lzma._BUFFER_SIZE is less than 2048 then all example files are
decompressed successfully (at least lzma module produces the same
results as xz utility)
--
Added file: http://bugs.python.org/file37241/decompress-example-files.py
Changes by Akira Li 4kir4...@gmail.com:
Removed file: http://bugs.python.org/file37240/decompress-example-files.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21872
___
Michael Foord added the comment:
Looks good, thanks for the quick response.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22894
___
___
Changes by Gregory P. Smith g...@krypto.org:
--
assignee: gregory.p.smith -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22910
___
___
Gregory P. Smith added the comment:
I suspect flakiness is due to parallel test execution. Is some other test
possibly executing at the same time removing __pycache__ directories or .pyc
files to recreate them (test_compileall?)? If the test were adjusted to point
to a .py file of its own
Gregory P. Smith added the comment:
fyi - tracking the new issue koobs reported in http://bugs.python.org/issue22910
--
nosy: +gregory.p.smith
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20123
Bernard Spil added the comment:
Hi,
I think this can be found in LibreSSL's opensslv.h
An ifdef LIBRESSL_VERSION_NUMBER should work
See
https://github.com/libressl-portable/openbsd/blob/master/src/lib/libssl/src/crypto/opensslv.h
_ssl.c includes crypto.h which in turn includes opensslv.h
Serhiy Storchaka added the comment:
Actually TarFile already works with non-seekable streams. Use TarFile.open()
with mode='r|*' or like.
On other hand I'm not against the make non-compressed ZipExtFile seekable. It
can be helpful in case when ZIP file is used just as a container for other
Serhiy Storchaka added the comment:
I hesitate about applying the patch to maintained releases. On one hand,
besides interface (even non-documented details) left the same, the patch
changes interiors too much for ordinal bug. I don't see how it can break
something, but this doesn't guarantee
Serhiy Storchaka added the comment:
So what the patch (with mitigated tests) is more preferable?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22687
___
David Wilson added the comment:
While in spirit this is a bug fix, it's reasonably complex and affects a
popular module -- I'm not sure it should be applied to 2.x, and probably not in
a minor release of 3.x either. Would it make sense to include as part of 3.5?
(That said, I'd love to see
Brett Cannon added the comment:
LGTM
--
assignee: brett.cannon - serhiy.storchaka
stage: patch review - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19720
___
Brett Cannon added the comment:
I have a patch to silence the exception and I'm running the test suite now.
I'm planning to keep this to a 3.5 fix and not changing the semantics in Python
3.4 as the fix is a little different from the standard directory in sys.path
is invalid since '' is
Marc Schlaich added the comment:
AFAIS this would break all existing code for yield-based coroutine schedulers
(Tornado, Twisted, Trollius, monocle, ...) when a coroutine is exited with
`raise StopIteration` in client code.
And this seems like a lot, a quick GitHub code search gives various
Roundup Robot added the comment:
New changeset 8558fff73032 by Brett Cannon in branch 'default':
Issue #22834: Have import suppress FileNotFoundError when the current
https://hg.python.org/cpython/rev/8558fff73032
--
nosy: +python-dev
___
Python
Brett Cannon added the comment:
Along with fixing this I also updated the import reference to mention how the
current working directory is handled.
Thanks to Martin for the report and everyone for their input!
--
resolution: - fixed
stage: - resolved
status: open - closed
versions:
Chris Angelico added the comment:
Marc, are those all cases where the raise StopIteration is actually inside a
generator? If so, it can be trivially replaced with return. Yes, it'll break
that way of spelling it, but it's a completely mechanical transformation, and
making the change won't
Marc Schlaich added the comment:
Yes, all yield-based coroutines are generators. I know that there is a backward
compatible upgrade path, but this might have a huge impact on existing code.
Interestingly, I didn't know before researching this PEP that you can actually
use `return` without
Chris Angelico added the comment:
Yep, the question is whether any of the raise StopIteration lines are
actually non-local flow control. If they're local, then it's easy: mechanical
replacement with return and it becomes compatible with all versions (unless
it has a value attached to it, as
Brett Cannon added the comment:
I'm going to at least update the Makefile to have a ``make venv`` that will do
the steps necessary to create a venv and then check out the necessary tools. It
should also be set up so that running the command with a pre-existing venv will
update it. This should
Guido van Rossum added the comment:
If all examples were just using raise StopIteration instead of return
in a generator I would be very happy. Such code can be trivially fixed by
using return and the __future__ import will help the eventual transition.
It's sad that apparently this use of
Chris Angelico added the comment:
Sadly, I don't know of a way to check if that's the case, other than by
manually going through and eyeballing the code - if there's raise
StopIteration, see if there's also yield in the same function. The three
cited examples are (I checked those straight
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
___
___
Serhiy Storchaka added the comment:
I suggest to apply right now those changes which are compatible with current
behavior and don't make code more cumbersome. E.g.
-while True:
-yield next(line_pair_iterator)
+yield from line_pair_iterator
and
-raise
Roundup Robot added the comment:
New changeset 2de3c659a979 by Serhiy Storchaka in branch 'default':
Issue #19720: Suppressed context for some exceptions in importlib.
https://hg.python.org/cpython/rev/2de3c659a979
--
nosy: +python-dev
___
Python
New submission from Ian Kelly:
I expect this should result in a recursion depth exceeded error, not a
segmentation fault.
$ cat test.py
import itertools
l = []
it = itertools.chain.from_iterable(l)
l.append(it)
next(it)
$ python3 test.py
Segmentation fault (core dumped)
--
Serhiy Storchaka added the comment:
See issue22911 for another instance of this in chain.from_iterable().
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14010
___
Serhiy Storchaka added the comment:
This is a duplicate of issue14010.
--
nosy: +serhiy.storchaka
resolution: - duplicate
stage: - resolved
status: open - closed
superseder: - deeply nested filter segfaults
___
Python tracker
New submission from Taylor Marks:
The following code causes Python 2.7.8 to lockup for ten minutes, then crash,
in both Windows 7 and OS X:
from urllib import urlretrieve
urlretrieve('http://chromedriver.storage.googleapis.com/2.12/chromedriver_win32.zip',
'chromedriver_win32.zip')
Here's a
Roundup Robot added the comment:
New changeset 8f77f7bb46c7 by Serhiy Storchaka in branch 'default':
Issue #19720: Suppressed context for some exceptions in importlib.
https://hg.python.org/cpython/rev/8f77f7bb46c7
--
___
Python tracker
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - fixed
stage: commit review - resolved
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19720
___
Roundup Robot added the comment:
New changeset 301d62ef5c0b by Serhiy Storchaka in branch '2.7':
Issue #17293: socket.gethostbyname() can raise an exception of FreeBSD.
https://hg.python.org/cpython/rev/301d62ef5c0b
New changeset 97ceab0bd6f8 by Serhiy Storchaka in branch '3.4':
Issue #17293:
Changes by Brett Cannon br...@python.org:
--
resolution: - duplicate
status: open - closed
superseder: - Rewrite of Python 2/3 porting HOWTO
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22913
New submission from Brett Cannon:
This is a rewrite of the Python 2/3 porting HOWTO to describe how to make code
be compatible with both Python 2 3. To see it rendered for easier reading,
see https://gist.github.com/brettcannon/91ff264ae549315706f6
--
assignee: brett.cannon
Serhiy Storchaka added the comment:
Sorry, 8f77f7bb46c7 is related to issue17293, not this issue. I have copied
wrong commit message from clipboard.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19720
New submission from Brett Cannon:
This is a rewrite of the Python 2/3 porting HOWTO to describe how to make code
be compatible with both Python 2 3. To see it rendered for easier reading,
see https://gist.github.com/brettcannon/91ff264ae549315706f6
--
assignee: brett.cannon
Changes by Berker Peksag berker.pek...@gmail.com:
--
stage: - patch review
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22914
___
Changes by Barry A. Warsaw ba...@python.org:
--
nosy: +barry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22914
___
___
Python-bugs-list mailing
Serhiy Storchaka added the comment:
Why you have removed many sections: about subclassing from object, using io
classes, comparison of bytes with unicode objects, the use of warnings and -b
and -3 options and other subtle details?
--
nosy: +serhiy.storchaka
Ned Deily added the comment:
Sorry, I'm unable to reproduce the problem using various systems and various
version of Python 2.7. And, as I read the StackOverflow comments, it appears
that no one else was able to reproduce the problem, either. To investigate
further, we would need more
Serhiy Storchaka added the comment:
While we here may be change error messages?
The only error which contains end position is Extra data. And it doesn't look
clean to me why end position should be mentioned at all (it is always len(data)
here). I suggest to drop it, this will make error
Éric Araujo added the comment:
Thanks bitdancer for applying this.
FTR I just stumbled on code extracted from chishop that shows Django had issues
with the non-CRLF requests sent by distutils:
https://github.com/disqus/djangopypi/blob/master/djangopypi/http.py#L19
--
Éric Araujo added the comment:
Nick being the current shepherd for packaging discussions and the instigator of
the new version-independent documentation, I’d like to let him take a decision
on this.
--
assignee: eric.araujo - ncoghlan
nosy: +ncoghlan
versions: +Python 3.5 -Python 3.2,
New submission from Jocelyn:
With the attached code, and an xml file, I got the following error with python
3.4.2:
$ cat toto.xml
?xml version='1.0' encoding='UTF-8'?
test/test
$ python3.4 toto.py
Traceback (most recent call last):
File toto.py, line 10, in module
parse(proc.stdout,
R. David Murray added the comment:
My guess is that this is similar to issue 21044.
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22915
___
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22915
___
___
Mark Lawrence added the comment:
Anybody?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19980
___
___
Python-bugs-list mailing list
Zachary Ware added the comment:
Mark, did you test your latest patch?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19980
___
___
R. David Murray added the comment:
I've looked at the sax code, and this does indeed have the same root cause: in
python2 a dummy string was used for the 'name' attribute of io objects that are
based on file descriptors, whereas in python3 the name is the integer value of
the file descriptor.
Steve Dower added the comment:
That should be the last fix for Windows - a bit of code that was copied into
the new file but not removed from the old one.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22869
Roundup Robot added the comment:
New changeset e7df0a47af16 by Steve Dower in branch 'default':
Issue #22869: Remove duplicate stack check from pythonrun.c
https://hg.python.org/cpython/rev/e7df0a47af16
--
___
Python tracker rep...@bugs.python.org
Zachary Ware added the comment:
Steve, I was actually just minutes away from committing the same fix in the
opposite direction when I got the notification of your commit. Nick will
correct me if I'm wrong but I think PyOS_CheckStack was supposed to stay in
pythonrun.c, especially since it's
Steve Dower added the comment:
You may be right, I didn't think of looking in the include files. I assumed
that it was copied without being removed, rather than the copy itself being
accidental. Feel free to move it back.
--
___
Python tracker
Roundup Robot added the comment:
New changeset 406965684327 by Zachary Ware in branch 'default':
Closes #22869: Move PyOS_CheckStack back to pythonrun.c
https://hg.python.org/cpython/rev/406965684327
--
status: open - closed
___
Python tracker
54 matches
Mail list logo
