[issue13894] threading._CRLock should not be tested if _thread.RLock isn't implemented
New submission from Matt Joiner anacro...@gmail.com: _threading.RLock is optional, and threading._CRLock is set to None if it isn't available. If this happens, the test_threading unittests crash. Some implementations don't provide _thread.RLock. Patch attached. -- components: Library (Lib) files: skip-crlock-tests-if-not-implemented.patch keywords: patch messages: 152151 nosy: anacrolix priority: normal severity: normal status: open title: threading._CRLock should not be tested if _thread.RLock isn't implemented type: behavior versions: Python 3.3 Added file: http://bugs.python.org/file24345/skip-crlock-tests-if-not-implemented.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13496] bisect module: Overflow at index computation
Mark Dickinson dicki...@gmail.com added the comment: Here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file24346/issue13496.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4966] Improving Lib Doc Sequence Types Section
Nick Coghlan ncogh...@gmail.com added the comment: One other point... the branch is actually now relative to default, not 3.2. While that was due to a merging mistake on my part, it also means I can legitimately ignore the narrow/wide build distinction in the section on strings. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4966 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13874] test_faulthandler: read_null test fails with current clang
Stefan Krah stefan-use...@bytereef.org added the comment: Jes??s Cea Avi??n rep...@bugs.python.org wrote: That makes x and y volatile. Well yes, but is that a problem? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13894] threading._CRLock should not be tested if _thread.RLock isn't implemented
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 5cf181df7bea by Charles-François Natali in branch '3.2': Issue #13894: Skip test_threading.CRLockTests if _CRLock isn't available. Patch http://hg.python.org/cpython/rev/5cf181df7bea New changeset 279b6d778663 by Charles-François Natali in branch 'default': Issue #13894: Skip test_threading.CRLockTests if _CRLock isn't available. Patch http://hg.python.org/cpython/rev/279b6d778663 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
New submission from Nadeem Vawda nadeem.va...@gmail.com:
Since changeset b99c54acb22d, the ARM Ubuntu buildbot has been hanging in
test_ssl:
http://www.python.org/dev/buildbot/all/builders/ARM%20Ubuntu%203.x/builds/250/steps/test/logs/stdio
I've been able to reproduce this behaviour on my AMD64 Ubuntu 11.10 machine.
The last output before it hangs is:
test_protocol_sslv3 (test.test_ssl.ThreadedTests)
Connecting to an SSLv3 server with various client options ...
SSLv3-SSLv3 CERT_NONE
SSLv3-SSLv3 CERT_OPTIONAL
SSLv3-SSLv3 CERT_REQUIRED
{SSLv23-SSLv3} CERT_NONE
No such problem has shown up on the x86 Ubuntu Shared builder. This is probably
because it runs Ubuntu 8.04, whereas the ARM bot runs 11.10.
--
messages: 152156
nosy: barry, giampaolo.rodola, janssen, nadeem.vawda, pitrou
priority: normal
severity: normal
stage: needs patch
status: open
title: test_ssl hangs on Ubuntu
type: behavior
versions: Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13895
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13894] threading._CRLock should not be tested if _thread.RLock isn't implemented
Charles-François Natali neolo...@free.fr added the comment: Committed, thanks! -- components: +Tests -Library (Lib) nosy: +neologix resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13894 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Nadeem Vawda nadeem.va...@gmail.com added the comment: The ARM Ubuntu 3.2 buildbot is having the same problem: http://www.python.org/dev/buildbot/all/builders/ARM%20Ubuntu%203.2/builds/158/steps/test/logs/stdio The 2.7 bot is fine, though. -- versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13896] shelf doesn't work with 'with'
New submission from Filip Gruszczyński grusz...@gmail.com: It would be cool if use could use with to manage shelf object and forget about close. -- messages: 152159 nosy: gruszczy priority: normal severity: normal status: open title: shelf doesn't work with 'with' ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13896] shelf doesn't work with 'with'
Changes by Filip Gruszczyński grusz...@gmail.com: -- keywords: +patch Added file: http://bugs.python.org/file24347/13896.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4966] Improving Lib Doc Sequence Types Section
Nick Coghlan ncogh...@gmail.com added the comment: I finished off the binary data section, so the first draft of the update is now complete in the bitbucket repo. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4966 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Stefan Krah stefan-use...@bytereef.org added the comment: I've been busy fixing the memoryview.h issues first. Could you take a look at: http://hg.python.org/features/pep-3118/file/f020716704d4/Include/memoryobject.h Changes: a) Make all functions and the two buffer access macros part of the limited API again. b) Make the managed buffer API definitely private. c) Make PyBUF_MAX_NDIM=64 part of the official buffer API. I think it might be OK to defer the decision about Py_MEMORYVIEW_C etc., since the comment already says ... Don't access their fields directly.. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13817] deadlock in subprocess while running several threads using Popen
Charles-François Natali neolo...@free.fr added the comment: And here's the test. To sum up: - reinit_tls.diff makes sure to call PyThread_ReInitTLS() at the beginning of PyOS_AfterFork(), so that the TLS API is usable within PyOS_AfterFork() (e.g. in _after_fork()). It would be applied to 3.2 and default, even though they are not affected (at least on platform withs a native TLS implementation) - reinit_tls_test.diff would be applied to 2.7, 3.2 and default: it should not trigger a failure on any of the active branches (2.7, 3.2 and default), it's just to prevent potential future regressions. Notes regarding the test: - I replaced subprocess with bare fork(), since it's way cheaper than spawning an entire subprocess - I reduced the number of threads compared to Christoph's reproducer, because I feel uncomfortable forking up to 1024 processes in parallel (even though in practise they won't be that much, because child processes will terminate before the other threads call fork()) - even with 2.7.2, it won't deadlock 100%, since the race window is really short (but having a failure on one of the buildbots once would be enough to detect the problem, should it ever resurface) -- versions: +Python 2.7 Added file: http://bugs.python.org/file24348/reinit_tls_test.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13817 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Antoine Pitrou pit...@free.fr added the comment: Can you try the following patch? -- keywords: +patch Added file: http://bugs.python.org/file24349/test_ssl.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Nadeem Vawda nadeem.va...@gmail.com added the comment:
With the patch applied on 3.2 (it doesn't apply on default), the test passes,
but it also prints out this exception traceback:
test_protocol_sslv3 (test.test_ssl.ThreadedTests)
Connecting to an SSLv3 server with various client options ...
SSLv3-SSLv3 CERT_NONE
SSLv3-SSLv3 CERT_OPTIONAL
SSLv3-SSLv3 CERT_REQUIRED
{SSLv23-SSLv3} CERT_NONE
Exception in thread Thread-8:
Traceback (most recent call last):
File /home/nadeem/src/cpython/3.2/Lib/threading.py, line 741, in
_bootstrap_inner
self.run()
File /home/nadeem/src/cpython/3.2/Lib/test/test_ssl.py, line 810, in run
if not self.wrap_conn():
File /home/nadeem/src/cpython/3.2/Lib/test/test_ssl.py, line 764, in
wrap_conn
self.sock, server_side=True)
File /home/nadeem/src/cpython/3.2/Lib/ssl.py, line 189, in wrap_socket
_context=self)
File /home/nadeem/src/cpython/3.2/Lib/ssl.py, line 276, in __init__
raise x
File /home/nadeem/src/cpython/3.2/Lib/ssl.py, line 272, in __init__
self.do_handshake()
File /home/nadeem/src/cpython/3.2/Lib/ssl.py, line 451, in do_handshake
self._sslobj.do_handshake()
socket.error: [Errno 104] Connection reset by peer
{TLSv1-SSLv3} CERT_NONE
SSLv23-SSLv3 CERT_NONE
ok
I'm assuming it's unrelated, though - I get the same traceback on earlier
revisions (before the test started hanging). Should I file a separate bug?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13895
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13874] test_faulthandler: read_null test fails with current clang
Jesús Cea Avión j...@jcea.es added the comment: Nothing. I just read the sourcecode :-). I would add an y=0 in the declaration too, just for aestetics. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13874 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10910] pyport.h FreeBSD/Mac OS X fix causes errors in C++ compilation
Chen Huang chi...@gmail.com added the comment: I am experiencing the same issue. Googled for a bit but couldn't find much with the error, then changed the search context, come across to this thread. In file included from /opt/local/include/boost/date_time/gregorian/parsers.hpp:13, from /opt/local/include/boost/date_time/gregorian/gregorian.hpp:34, from /opt/local/include/boost/date_time/posix_time/time_formatters.hpp:12, from /opt/local/include/boost/date_time/posix_time/posix_time.hpp:24, from /opt/local/include/boost/date_time/local_time/local_time.hpp:11, from /opt/local/include/boost/date_time.hpp:15, from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.h:11, from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.cpp:12: /opt/local/include/boost/date_time/date_parsing.hpp:50:33: error: macro tolower passed 2 arguments, but takes just 1 In file included from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.cpp:12: /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.h:13:21: error: Devices.h: No such file or directory In file included from /opt/local/include/boost/date_time/gregorian/parsers.hpp:13, from /opt/local/include/boost/date_time/gregorian/gregorian.hpp:34, from /opt/local/include/boost/date_time/posix_time/time_formatters.hpp:12, from /opt/local/include/boost/date_time/posix_time/posix_time.hpp:24, from /opt/local/include/boost/date_time/local_time/local_time.hpp:11, from /opt/local/include/boost/date_time.hpp:15, from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.h:11, from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.cpp:12: /opt/local/include/boost/date_time/date_parsing.hpp: In function ‘std::string boost::date_time::convert_to_lower(std::string)’: /opt/local/include/boost/date_time/date_parsing.hpp:50: error: cannot resolve overloaded function ‘tolower’ based on conversion to type ‘char’ In file included from /Users/chen/GitRepo/Cpp_EmbeddingPython/Device.cpp:12: -- nosy: +Chen.Huang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13897] Move fields relevant to coroutine/generators out of frame into generator/threadstate
New submission from Mark Shannon m...@hotpy.org: The frame object has a number of fields which belong to the generator object. By creating a CoState struct, these fields can be moved to generator/threadstate where they belong. The interpreter no longer has to swap around exception state whenever generators are entered/exited. The frame object is made more compact, reducing allocation/deallocation overhead (although benchmarking showed no significant difference) The attached patch reduces the code base by about 50 LOC overall. -- components: Interpreter Core files: coro.patch keywords: patch messages: 152167 nosy: Mark.Shannon priority: normal severity: normal status: open title: Move fields relevant to coroutine/generators out of frame into generator/threadstate type: enhancement versions: Python 3.3 Added file: http://bugs.python.org/file24350/coro.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Antoine Pitrou pit...@free.fr added the comment: I'm assuming it's unrelated, though - I get the same traceback on earlier revisions (before the test started hanging). Should I file a separate bug? Yes, please. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10910] pyport.h FreeBSD/Mac OS X fix causes errors in C++ compilation
Chen Huang chi...@gmail.com added the comment: if I put #include cctype before boost/date_time, it solves my problem. And by the way, i can't seem to get to the point where boost/week_ptr.hpp causes the error. I tried to compile Nasos's upload test-boost-python. That codes works on my machine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 10c79f29e417 by Antoine Pitrou in branch '3.2': Issue #13895: fix test_ssl hanging under Ubuntu http://hg.python.org/cpython/rev/10c79f29e417 New changeset db0c717cbc01 by Antoine Pitrou in branch 'default': Issue #13895: fix test_ssl hanging under Ubuntu http://hg.python.org/cpython/rev/db0c717cbc01 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13895] test_ssl hangs on Ubuntu
Antoine Pitrou pit...@free.fr added the comment: Hopefully it's fixed now, thank you. -- resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13895 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
New submission from Nadeem Vawda nadeem.va...@gmail.com:
While running test_ssl in verbose mode, I noticed the following exception:
[...]
test_protocol_sslv3 (test.test_ssl.ThreadedTests)
Connecting to an SSLv3 server with various client options ...
SSLv3-SSLv3 CERT_NONE
SSLv3-SSLv3 CERT_OPTIONAL
SSLv3-SSLv3 CERT_REQUIRED
{SSLv23-SSLv3} CERT_NONE
Exception in thread Thread-54:
Traceback (most recent call last):
File /home/nadeem/src/cpython/def/Lib/threading.py, line 730, in
_bootstrap_inner
self.run()
File /home/nadeem/src/cpython/def/Lib/test/test_ssl.py, line 926, in run
if not self.wrap_conn():
File /home/nadeem/src/cpython/def/Lib/test/test_ssl.py, line 880, in
wrap_conn
self.sock, server_side=True)
File /home/nadeem/src/cpython/def/Lib/ssl.py, line 206, in wrap_socket
_context=self)
File /home/nadeem/src/cpython/def/Lib/ssl.py, line 293, in __init__
raise x
File /home/nadeem/src/cpython/def/Lib/ssl.py, line 289, in __init__
self.do_handshake()
File /home/nadeem/src/cpython/def/Lib/ssl.py, line 489, in do_handshake
self._sslobj.do_handshake()
ConnectionResetError: [Errno 104] Connection reset by peer
{TLSv1-SSLv3} CERT_NONE
SSLv23-SSLv3 CERT_NONE
ok
[...]
Note that the exception is ignored and the test still passes.
--
components: Tests
messages: 152172
nosy: giampaolo.rodola, janssen, nadeem.vawda, pitrou
priority: normal
severity: normal
stage: needs patch
status: open
title: Ignored exception in test_ssl
type: behavior
versions: Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13898
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Stefan Krah stefan-use...@bytereef.org added the comment: Nick Coghlan rep...@bugs.python.org wrote: Radical suggestion: make it public as collections.simple_ndarray? Heh, that's a nice one. :) While I think that the code in _testbuffer.c is sound and very well tested, the API is low-level and optimized for testing all sorts of quirks. Examples: _testbuffer.ndarray has the questionable capability of changing views while buffers are exported. This is to test the pathological case that came up in the discussion. Then, similar to NumPy's ndarray, _testbuffer.ndarray constructs arrays from a flat list. This is a bit clumsy but quite suitable for testing. NumPy's ndarray is also the low level API. I think most people use the high level array: a = array([[1,2], [3,4]], dtype=L) a array([[1, 2], [3, 4]], dtype=uint64) So it would take some effort to polish the API. Meanwhile, to eliminate the use of _testbuffer in the documentation, I think the following might work: I've just added complete support for displaying multi-dimensional lists and multi-dimensional comparisons to memoryobject.c in my private repo. The code is quite succinct and follows exactly the same pattern as copy_base/copy_rec. Then, in the documentation we can use cast() and memoryview.tolist(), but add a comment that cast() is just used for demonstration purposes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Antoine Pitrou pit...@free.fr added the comment: Nick Coghlan rep...@bugs.python.org wrote: Radical suggestion: make it public as collections.simple_ndarray? Heh, that's a nice one. :) Well, the question is: does it have a point? Is this ndarray useful outside of any third-party infrastructure such as the APIs offered by numpy? You might answer that we already have array.array but ISTM that array.array is quite useless in general :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Stefan Krah stefan-use...@bytereef.org added the comment: Antoine Pitrou rep...@bugs.python.org wrote: Nick Coghlan rep...@bugs.python.org wrote: Radical suggestion: make it public as collections.simple_ndarray? Heh, that's a nice one. :) Well, the question is: does it have a point? Is this ndarray useful outside of any third-party infrastructure such as the APIs offered by numpy? I think it would be mainly educational. It's easier to understand the whole (multi-dimensional) point of PEP-3118 when there's a concrete object that you can play with. Of course serious users would go straight to NumPy. The other issue is that's it's slightly strange to have a fully featured memoryview with no object in the stdlib that can utilize all features (at least the testing side is now complete). Anyway, right now I don't know myself if I'm for or against it. :) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1633941] for line in sys.stdin: doesn't notice EOF the first time
Ralph Corderoy ralph-pythonb...@inputplus.co.uk added the comment:
This most certainly is a bug under Unix and an annoying one. Since the
issue is with platform's stdio library is wrong; stdio is being used
incorrectly. It would be nice to see it fixed in the 2.x line.
I've two test programs.
$ head -42 stdin2.6 stdin3.1
== stdin2.6 ==
#! /usr/bin/python2.6
import sys
for l in sys.stdin:
print repr(l)
print 'end'
== stdin3.1 ==
#! /usr/bin/python3.1
import sys
for l in sys.stdin:
print(repr(l))
print('end')
$
For both of them I will type 1 Enter 2 Enter 3 Enter Ctrl-D without
the spaces, Ctrl-D being my tty's EOF, stty -a.
$ ./stdin2.6
1
2
3
'1\n'
'2\n'
'3\n'
On the EOF the first iteration of sys.stdin returns and then so do the
others with the buffered lines. The loop doesn't terminate, a second
Ctrl-D is required, giving.
end
$
Next,
$ ./stdin3.1
1
'1\n'
2
'2\n'
3
'3\n'
end
$
perfect output. Only one Ctrl-D required and better still each line is
returned as it's entered.
ltrace shows python2.6 uses fread(3). I'm assuming it treats only a
zero return as EOF whereas whenever the return value is less than the
number of requested elements, EOF could have been reached; feof(3) must
be called afterwards to decide. Really, ferror(3) should also be called
to see if, as well as returning some elements, an error was detected.
It's this lack of feof() that means the second fread() is required to
trigger the flawed `only 0 return is EOF' logic.
Here's some C that shows stdio works fine if feof() and ferror() are
combined with fread().
#include stdio.h
int main(void)
{
unsigned char s[8192], *p;
size_t n;
while ((n = fread(s, 1, 8192, stdin))) {
printf(%zd, n);
p = s;
while (n--)
printf( %02hhx, *p++);
putchar('\n');
if (feof(stdin)) {
puts(end);
break;
}
if (ferror(stdin)) {
fputs(error, stderr);
return 1;
}
}
return 0;
}
--
nosy: +ralph.corderoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1633941
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Antoine Pitrou pit...@free.fr added the comment: What is the OpenSSL version? (printed at the beginning of test_ssl) Having an exception here is quite normal: the test checks that a certain (client protocol, server protocol) combination fails. However, a SSLError is expected rather than an OSError. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Nadeem Vawda nadeem.va...@gmail.com added the comment:
What is the OpenSSL version?
test_ssl: testing with 'OpenSSL 1.0.0e 6 Sep 2011' (1, 0, 0, 5, 15)
under Linux ('debian', 'wheezy/sid', '')
HAS_SNI = True
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13898
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Antoine Pitrou pit...@free.fr added the comment:
What is the OpenSSL version?
test_ssl: testing with 'OpenSSL 1.0.0e 6 Sep 2011' (1, 0, 0, 5, 15)
under Linux ('debian', 'wheezy/sid', '')
HAS_SNI = True
For the record, it works here under 'OpenSSL 1.0.0d 8 Feb 2011'.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13898
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Antoine Pitrou pit...@free.fr added the comment: The changelog between 1.0.0d and 1.0.0e doesn't seem to list anything which could affect this test: *) Fix bug where CRLs with nextUpdate in the past are sometimes accepted by initialising X509_STORE_CTX properly. (CVE-2011-3207) [Kaspar Brand o...@velox.ch] *) Fix SSL memory handling for (EC)DH ciphersuites, in particular for multi-threaded use of ECDH. (CVE-2011-3210) [Adam Langley (Google)] *) Fix x509_name_ex_d2i memory leak on bad inputs. [Bodo Moeller] *) Remove hard coded ecdsaWithSHA1 signature tests in ssl code and check signature public key algorithm by using OID xref utilities instead. Before this you could only use some ECC ciphersuites with SHA1 only. [Steve Henson] *) Add protection against ECDSA timing attacks as mentioned in the paper by Billy Bob Brumley and Nicola Tuveri, see: http://eprint.iacr.org/2011/232.pdf (from http://www.openssl.org/news/changelog.html) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Nadeem Vawda nadeem.va...@gmail.com added the comment: Might it be a distribution-specific issue, then? I'm running Ubuntu and IIRC you're using Mageia? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Antoine Pitrou pit...@free.fr added the comment: Might it be a distribution-specific issue, then? I'm running Ubuntu and IIRC you're using Mageia? Yes, I'm using Mageia. It would be nice if you could take a look at Ubuntu's or Debian's OpenSSL patches (if any). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13703] Hash collision security issue
Dave Malcolm dmalc...@redhat.com added the comment: This turns out to pass without PYTHONHASHRANDOMIZATION in the environment, and fail intermittently with it. Note that make test invokes the built python with -E, so that it ignores the setting of PYTHONHASHRANDOMIZATION in the environment. Barry, Benjamin: does fixing this bug require getting the full test suite to pass with randomization enabled (and fixing the intermittent failures due to ordering issues), or is it acceptable to merely have full passes without randomizing the hashes? What do the buildbots do? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13898] Ignored exception in test_ssl
Nadeem Vawda nadeem.va...@gmail.com added the comment: I can't see anything in the Ubuntu patches (available from https://launchpad.net/ubuntu/+source/openssl/1.0.0e-2ubuntu4) that relate to networking or handshakes, so maybe it's not that. I could be wrong, though - I've never used OpenSSL myself. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13703] Hash collision security issue
Benjamin Peterson benja...@python.org added the comment: I think we don't need to mess with tests in 2.6/3.1, but everything should pass under 2.7 and 3.2. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13896] shelf doesn't work with 'with'
Zachary Richey mach1...@gmail.com added the comment: The docs for shelve(see: http://docs.python.org/dev/library/shelve.html#shelve.open) recommend using contextlib.closing for this purpose. -- nosy: +zachary r. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13896 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13496] bisect module: Overflow at index computation
Changes by Mark Dickinson dicki...@gmail.com: -- stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13496 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11437] IDLE crash on startup with typo in config-keys.cfg
Roger Serwy roger.se...@gmail.com added the comment: Attached is a patch against 3.3a0 to validate the active key set in the configuration handler. It validates each key binding and then presents a dialog with a list of incorrect keys if there are any. In developing this patch I found that IDLE calls GetCurrentKeySet multiple times during initialization of an EditorWindow or a PyShell, once for each extension loaded. This inefficiency leads to long start times for IDLE. -- keywords: +patch Added file: http://bugs.python.org/file24351/issue11437.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11437 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Antoine Pitrou pit...@free.fr added the comment: a) Make all functions and the two buffer access macros part of the limited API again. Hmm, I don't think buffer access macros should be part of the limited API. If they are truely important (which I doubt), we should have equivalent functions for them. I think it might be OK to defer the decision about Py_MEMORYVIEW_C etc., since the comment already says ... Don't access their fields directly.. My question is whether there is any point in making these flags. Does 3rd-party code want to manipulate memoryview internals, instead of querying the Py_buffer? (and of course the memoryview object is becoming more and more like another Py_buffer :-)) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5707] IDLE will not load
Roger Serwy roger.se...@gmail.com added the comment: Amaury's patch has already been applied in (d31be8c9c8a2). GUO's description does cause an error. TclTk does not allow Control by itself to be bounded. This underlying cause for that error is addressed in #6739 I think this issue should be closed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5707 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13806] Audioop decompression frames size check fix
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 77188bc37c74 by Antoine Pitrou in branch '3.2': Issue #13806: The size check in audioop decompression functions was too strict and could reject valid compressed data. http://hg.python.org/cpython/rev/77188bc37c74 New changeset ce89dcba008f by Antoine Pitrou in branch 'default': Issue #13806: The size check in audioop decompression functions was too strict and could reject valid compressed data. http://hg.python.org/cpython/rev/ce89dcba008f New changeset f1ee3bb6ba64 by Antoine Pitrou in branch '2.7': Issue #13806: The size check in audioop decompression functions was too strict and could reject valid compressed data. http://hg.python.org/cpython/rev/f1ee3bb6ba64 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13806 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13806] Audioop decompression frames size check fix
Antoine Pitrou pit...@free.fr added the comment: Thank you for your work Oleg! The patch is now committed. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13806 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13884] IDLE 2.6.5 Recent Files undocks
Roger Serwy roger.se...@gmail.com added the comment: Should tear-off menus still be a feature? This relates to the #13504 meta-issue, in particular entry 4) ANNOYANCE: Get rid of the detachable menus feature.. Attached is patch against 3.3a0 to disable tear-off menus. (It also makes modifications to Mac-specific code, but I can't test it since I don't have a Mac.) -- keywords: +patch nosy: +serwy Added file: http://bugs.python.org/file24352/issue13884.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13884 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13504] Meta-issue for Invent with Python IDLE feedback
Roger Serwy roger.se...@gmail.com added the comment: #13884 has a patch to address point 4) ANNOYANCE: Get rid of the detachable menus feature. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13504 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13899] re pattern r[\A] should work like A but matches nothing. Ditto B and Z.
New submission from John Machin sjmac...@lexicon.net: Expected behaviour illustrated using C: import re re.findall(r'[\C]', 'CCC') ['C', 'C', 'C'] re.compile(r'[\C]', 128) literal 67 _sre.SRE_Pattern object at 0x01FC6E78 re.compile(r'C', 128) literal 67 _sre.SRE_Pattern object at 0x01FC6F08 Incorrect behaviour exhibited by A (and by B and Z): re.findall(r'[\A]', 'AAA') [] re.compile(r'A', 128) literal 65 _sre.SRE_Pattern object at 0x01FC6F98 re.compile(r'[\A]', 128) in at at_beginning_string FAIL _sre.SRE_Pattern object at 0x01FDF0B0 Also there is no self-checking at runtime; the switch default has a comment to the effect that nothing can be done, so pretend that the unknown opcode matched nothing. Zen? -- messages: 152194 nosy: sjmachin priority: normal severity: normal status: open title: re pattern r[\A] should work like A but matches nothing. Ditto B and Z. type: behavior versions: Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13899] re pattern r[\A] should work like A but matches nothing. Ditto B and Z.
Ezio Melotti ezio.melo...@gmail.com added the comment: This happens because \A, \B and \Z are valid escape sequences[0]. If what you mean is that they shouldn't be recognized as such inside a character class, then I can agree with that. ^ and $ are similar to \A and \Z but they are considered as literals inside []. I think the same could also be applied to \b and \B, unless you expect r'[\b]' to match the same as r'\b'. (On an unrelated note, it's preferable to avoid using ints as flag -- using re.DEBUG is better) [0]: http://docs.python.org/library/re.html#regular-expression-syntax -- nosy: +ezio.melotti, mrabarnett ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Stefan Krah stefan-use...@bytereef.org added the comment: Antoine Pitrou rep...@bugs.python.org wrote: a) Make all functions and the two buffer access macros part of the limited API again. Hmm, I don't think buffer access macros should be part of the limited API. If they are truely important (which I doubt), we should have equivalent functions for them. I thought the whole Py_buffer API was only temporarily removed from the limited API until the issues were sorted out: http://bugs.python.org/issue10181#msg125462 For instance, here the macros are not excluded: http://hg.python.org/cpython/file/3292cc222d5c/Include/memoryobject.h Since the issues seem resolved in general, I thought it was time to restore the previous state. [I just noticed that I didn't revert all of Martin's changes, so xxlimited currently does not build in the pep-3118 repo.] As for the two macros specifically, I know Pauli was using them: http://bugs.python.org/issue10181#msg139775 I think it might be OK to defer the decision about Py_MEMORYVIEW_C etc., since the comment already says ... Don't access their fields directly.. My question is whether there is any point in making these flags. Does 3rd-party code want to manipulate memoryview internals, instead of querying the Py_buffer? The flags are primarily for the memoryview itself to avoid repeated calls to PyBuffer_IsContiguous(). So when 3rd-party uses PyMemoryView_GET_BUFFER to get the view and also needs to determine the contiguity type, that code could also use the flags. Pauli: If you are still following the issue, do you think having access to contiguity flags is useful for 3rd-party code or not? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Antoine Pitrou pit...@free.fr added the comment: Antoine Pitrou rep...@bugs.python.org wrote: a) Make all functions and the two buffer access macros part of the limited API again. Hmm, I don't think buffer access macros should be part of the limited API. If they are truely important (which I doubt), we should have equivalent functions for them. I thought the whole Py_buffer API was only temporarily removed from the limited API until the issues were sorted out: http://bugs.python.org/issue10181#msg125462 I'm talking about the memoryview access macros. It's like PyList_GET_SIZE, it isn't part of the limited API and you have to use PyList_GetSize instead. The limited API promises binary (ABI) compatibility accross releases. It's a very strong promise to make and we must be careful not to put too much stuff in the limited API. I don't think the rule for inclusion is we should put everything useful in the limited API. For instance, here the macros are not excluded: http://hg.python.org/cpython/file/3292cc222d5c/Include/memoryobject.h It might be a mistake, then. As for the two macros specifically, I know Pauli was using them: http://bugs.python.org/issue10181#msg139775 Well, Pauli might use them, but it just means his code isn't compatible with the limited API, then. The flags are primarily for the memoryview itself to avoid repeated calls to PyBuffer_IsContiguous(). So when 3rd-party uses PyMemoryView_GET_BUFFER to get the view and also needs to determine the contiguity type, that code could also use the flags. But why would 3rd-party code use PyMemoryView_GET_BUFFER instead of, for example, PyObject_GetBuffer? You seldom have APIs which *expect* a memoryview, I think. Instead, they would expect a buffer-compatible object. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13899] re pattern r[\A] should work like A but matches nothing. Ditto B and Z.
John Machin sjmac...@lexicon.net added the comment: @ezio: Of course the context is inside a character class. I expect r'[\b]' to act like r'\b' aka r'\x08' aka backspace because (1) that is the treatment applied to all other C-like control char escapes (2) the docs say so explicitly: Inside a character range, \b represents the backspace character, for compatibility with Python’s string literals. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13899 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13703] Hash collision security issue
Dave Malcolm dmalc...@redhat.com added the comment: On Sat, 2012-01-28 at 20:05 +, Benjamin Peterson wrote: Benjamin Peterson benja...@python.org added the comment: I think we don't need to mess with tests in 2.6/3.1, but everything should pass under 2.7 and 3.2. New version of the patch for 3.1 optin-hash-randomization-for-3.1-dmalcolm-2012-01-28-001.patch This version adds a command-line flag to enable hash-randomization: -R (given that the -E flag disables env vars and thus disabled PYTHONHASHRANDOMIZATION). See [1] below [Is there a convenient way to check the length of the usage messages in Modules/main.c? I see this comment: /* Long usage message, split into parts 512 bytes */ ] I reworded the documentation somewhat based on input from Barry and Antoine. Also adds a NEWS item. Passes make test on this x86_64 Fedora 15 box, --with-pydebug, though that's without randomization enabled (it just does it within individual test cases that explicitly enable it). No performance testing done yet (though hopefully similar to that of Victor's patch; see msg151078) No idea of the impact on Windows users (I don't have a windows dev box). It still has the stuff from Victor's patch described in msg151158. How is this looking? Dave [1] IRC transcript concerning -R follows: __ap__ dmalcolm: IMO it would be simpler if there was only one env var (preferably not too clumsy to type) __ap__ also, despite being neither barry nor gutworth, I think the test suite *should* pass with randomized hashes __ap__ :) dmalcolm :) __ap__ also the failure you're having is a bit worrying, since apparently it's not about dict ordering dmalcolm PYTHONHASHSEED exists mostly for selftesting (also for compat, if you absolutely need to reproduce a specific random dict ordering) __ap__ ok __ap__ if -E suppresses hash randomization, I think we should also add a command-line flag __ap__ -R seems untaken __ap__ also it'll make things easier for Windows users, I think -- Added file: http://bugs.python.org/file24353/optin-hash-randomization-for-3.1-dmalcolm-2012-01-28-001.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___diff -r 73dad4940b88 Doc/reference/datamodel.rst --- a/Doc/reference/datamodel.rst Fri Jan 20 11:23:02 2012 + +++ b/Doc/reference/datamodel.rst Sat Jan 28 18:05:49 2012 -0500 @@ -1265,6 +1265,8 @@ inheritance of :meth:`__hash__` will be blocked, just as if :attr:`__hash__` had been explicitly set to :const:`None`. + See also the :option:`-R` command-line option. + .. method:: object.__bool__(self) diff -r 73dad4940b88 Doc/using/cmdline.rst --- a/Doc/using/cmdline.rst Fri Jan 20 11:23:02 2012 + +++ b/Doc/using/cmdline.rst Sat Jan 28 18:05:49 2012 -0500 @@ -21,7 +21,7 @@ When invoking Python, you may specify any of these options:: -python [-bBdEhiOsSuvVWx?] [-c command | -m module-name | script | - ] [args] +python [-bBdEhiORsSuvVWx?] [-c command | -m module-name | script | - ] [args] The most common use case is, of course, a simple invocation of a script:: @@ -215,6 +215,30 @@ Discard docstrings in addition to the :option:`-O` optimizations. +.. cmdoption:: -R + + Turn on hash randomization, so that the :meth:`__hash__` values of str, + bytes and datetime objects are salted with an unpredictable random value. + Although they remain constant within an individual Python process, they + are not predictable between repeated invocations of Python. + + This is intended to provide protection against a denial-of-service + caused by carefully-chosen inputs that exploit the worst case performance + of a dict lookup, O(n^2) complexity. See: + + http://www.ocert.org/advisories/ocert-2011-003.html + + for details. + + Changing hash values affects the order in which keys are retrieved from + a dict. Although Python has never made guarantees about this ordering + (and it typically varies between 32-bit and 64-bit builds), enough + real-world code implicitly relies on this non-guaranteed behavior that + the randomization is disabled by default. + + See also :envvar:`PYTHONHASHRANDOMIZATION`. + + .. cmdoption:: -s Don't add user site directory to sys.path @@ -435,6 +459,25 @@ import of source modules. +.. envvar:: PYTHONHASHRANDOMIZATION + + If this is set to a non-empty string it is equivalent to specifying the + :option:`-R` option. + + +.. envvar:: PYTHONHASHSEED + + If this is set, it is used as a fixed seed for generating the hash() of + the types covered by the :option:`-R` option (or its equivalent, + :envvar:`PYTHONHASHRANDOMIZATION`. + + It is primarily intended for use in selftests for the interpreter, but + may perhaps be of use for reproducing a specific dict ordering. + + It should be a decimal number in the range [0; 4294967295]. Specifying + the
[issue13703] Hash collision security issue
Antoine Pitrou pit...@free.fr added the comment: Passes make test on this x86_64 Fedora 15 box, --with-pydebug, though that's without randomization enabled (it just does it within individual test cases that explicitly enable it). I think you should check with randomization enabled, if only to see the nature of the failures and if they are expected. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10910] pyport.h FreeBSD/Mac OS X fix causes errors in C++ compilation
Chen Huang chi...@gmail.com added the comment: Nevermind, putting #include cctype doesn't help. I have to put python.h on top to get away this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10910 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13897] Move fields relevant to coroutine/generators out of frame into generator/threadstate
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: - Why is it called CoState? is it related to coroutines? - I'm a bit worried about the removal of tstate-exc_value, and the changes in sys.exc_info(). tstate-exc_value is used by many extension modules, do you really want to replace this? -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13703] Hash collision security issue
Terry J. Reedy tjre...@udel.edu added the comment: I think you should check with randomization enabled, if only to see the nature of the failures and if they are expected. Including the list of when-enabled expected failures in the release notes would help those who compile and test. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13897] Move fields relevant to coroutine/generators out of frame into generator/threadstate
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +benjamin.peterson, ncoghlan stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13703] Hash collision security issue
Dave Malcolm dmalc...@redhat.com added the comment: On Sat, 2012-01-28 at 23:56 +, Terry J. Reedy wrote: Terry J. Reedy tjre...@udel.edu added the comment: I think you should check with randomization enabled, if only to see the nature of the failures and if they are expected. Including the list of when-enabled expected failures in the release notes would help those who compile and test. OK, though note that because it's random, I'll have to run it a few times, and we'll see what shakes out. Am running with: $ make test TESTPYTHONOPTS=-R leading to: ./python -E -bb -R ./Lib/test/regrtest.py -l BTW, I see: Testing with flags: sys.flags(debug=0, division_warning=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=1, verbose=0, bytes_warning=2) which doesn't list the new flag. Should I add it to sys.flags? (or does anyone ever do tuple-unpacking of that PyStructSequence and thus rely on the number of elements?) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13703 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13897] Move fields relevant to coroutine/generators out of frame into generator/threadstate
Benjamin Peterson benja...@python.org added the comment: Extensions modules should really be using PyErr_Occurred/Fetch etc. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Nick Coghlan ncogh...@gmail.com added the comment: I'm with Antoine here - we want to be *very* conservative with what we expose through the limited API. Due to the ABI compatibility promise, anything exposed that way is very hard to change. Keeping things out of the limited API isn't really an issue - it just means that anyone that wants to use them needs to rebuild their extensions for each new version of the C API (just as they do now). Addings things to the stable ABI later is easy though - that's why we had Martin take all the Py_buffer related stuff out of the initial version of the limited API. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13897] Move fields relevant to coroutine/generators out of frame into generator/threadstate
Nick Coghlan ncogh...@gmail.com added the comment: The division of responsibilities between generator objects and the eval loop is currently a little messy. The eval loop deals almost entirely with frame objects and also handles swapping exception states around on behalf of generators, which is why the generator specific exception state currently lives on frame objects (i.e. to avoid the eval loop needing to know too much about the internal structure of generator objects). Before generator related state can reasonably be moved out of the frame objects, those responsibilities should be divided more cleanly. Ron Adam has made an initially attempt at tackling that problem in issue 13607. Once the responsibilities are divided appropriately, *then* we can look at the fields that ceval no longer touches and see if they should be moved somewhere else (whether that's directly into the generator struct or into a new struct referenced from the generator struct). -- nosy: +ron_adam ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13897 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)
Nick Coghlan ncogh...@gmail.com added the comment: Also, +1 to replacing _testbuffer with .cast() to demonstrate the multi-dimensional support. Without an actual multi-dimensional array object in the standard library, demonstrating those aspects is always going to be a little tricky. However, it's worth doing so that the likes of NumPy and PIL don't need to explain those interactions. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10181 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13900] http://docs.python.org/library/email.parser.html#email.parser.Parser.parse
Changes by Parker Phinney gamegu...@gmail.com: -- assignee: docs@python components: Documentation nosy: Parker.Phinney, docs@python priority: normal severity: normal status: open title: http://docs.python.org/library/email.parser.html#email.parser.Parser.parse type: behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13900 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13900] documentation page on email.parser contains self-referential non-definition of headersonly parameter
New submission from Parker Phinney gamegu...@gmail.com: to recreate: go here: http://docs.python.org/library/email.parser.html#email.parser.Parser.parse notice this line: Optional headersonly is as with the parse() method. But that doesn't make sense, because this /is/ the parse() method! -- title: http://docs.python.org/library/email.parser.html#email.parser.Parser.parse - documentation page on email.parser contains self-referential non-definition of headersonly parameter type: behavior - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13900 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Nick Coghlan ncogh...@gmail.com added the comment: As part of the PEP 408 discussions, Guido approved the addition of 'regex' in 3.3 (using that name, rather than as a drop-in replacement for re) [1,2] That should greatly ease the backwards compatibility concerns, even if it isn't as transparent an upgrade path. [1] http://mail.python.org/pipermail/python-dev/2012-January/115961.html [2] http://mail.python.org/pipermail/python-dev/2012-January/115962.html -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Alex Gaynor alex.gay...@gmail.com added the comment: So, to my reading of teh compatibility PEP this cannot be added wholesale, unless there is a pure Python version as well. However, if it replaced re (read: patched) it would be valid. On Sun, Jan 29, 2012 at 1:26 AM, Nick Coghlan rep...@bugs.python.orgwrote: Nick Coghlan ncogh...@gmail.com added the comment: As part of the PEP 408 discussions, Guido approved the addition of 'regex' in 3.3 (using that name, rather than as a drop-in replacement for re) [1,2] That should greatly ease the backwards compatibility concerns, even if it isn't as transparent an upgrade path. [1] http://mail.python.org/pipermail/python-dev/2012-January/115961.html [2] http://mail.python.org/pipermail/python-dev/2012-January/115962.html -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Georg Brandl ge...@python.org added the comment: I created a new sandbox branch to integrate regex into CPython, see remote repo field. I mainly had to adapt the test suite to use unittest. -- hgrepos: +108 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file10645/issue2636-patches.tar.bz2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file10647/issue2636-02.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file11657/issue2636-01+09-02+17_backport.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file11669/issue2636+01+09-02+17+18+19+20+21+24+26_speedup.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file12932/issue2636-features.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file12974/issue2636-features-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13165/issue2636-features-3.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13185/issue2636-features-4.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13216/issue2636-features-5.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13257/issue2636-features-6.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13449/issue2636-patch-1.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file13707/issue2636-patch-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14570/issue2636-20090726.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14576/issue2636-20090727.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14594/issue2636-20090729.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14642/issue2636-20090804.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14682/issue2636-20090810.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14683/issue2636-20090810#2.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14687/issue2636-20090810#3.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file14733/issue2636-20090815.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file15901/issue2636-20100116.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16122/issue2636-20100204.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16195/issue2636-20100210.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16243/issue2636-20100217.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16247/issue2636-20100218.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16255/issue2636-20100219.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16278/Features-backslashes.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: -- nosy: -akitada, akoumjian, alex, amaury.forgeotdarc, belopolsky, davide.rizzo, eric.snow, ezio.melotti, georg.brandl, giampaolo.rodola, gregory.p.smith, jacques, jaylogan, jhalcrow, jimjjewett, loewis, mark, mattchaput, moreati, mrabarnett, ncoghlan, nneonneo, pitrou, r.david.murray, ronnix, rsc, sjmachin, stevenjd, stiv, timehorse, vbr, zdwiel ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16362/issue2636-20100224.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16365/issue2636-20100225.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16375/issue2636-20100226.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16424/issue2636-20100304.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16444/issue2636-20100305.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2636] Adding a new regex module (compatible with re)
Changes by Georg Brandl ge...@python.org: Removed file: http://bugs.python.org/file16626/issue2636-20100323.zip ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2636 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
