[issue3872] Python 2.6rc2: Tix ComboBox error
Dominique Wahli [EMAIL PROTECTED] added the comment: Sorry Martin but I couldn't help to fix this issue. A quick check of Tix widgets show the same issue with: CheckList HList ListNoteBook DirList DirTree DirSelectDialog DirSelectBox ExFileSelectBox FileSelectBox That's a lot of things so maybe it's time to remove Tix package from core Python. If not, Tix documentation in Python help need a big red comment in the beginning of the page. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3872 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3934] sphinx - building muppy docs fails on Linux
Robert Schuppenies [EMAIL PROTECTED] added the comment: This was fixed in r65489 (see issue3498). Using the current Sphinx trunk (http://svn.python.org/projects/doctools/trunk/sphinx) works for me. -- resolution: - duplicate status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3934 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3554] ctypes.wstring_at and string_at call Python API without the GIL
STINNER Victor [EMAIL PROTECTED] added the comment: Reference to the SVN: - trunk: rev65681 - release25-maint branch: rev65858 -- nosy: +haypo ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3554 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3943] IDLE won't start in 3.0rc1 Subprocess didn't make connection....
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: It is probably already corrected in svn. Can you please try from a command prompt: cd path_to_python3.0rc1 python Lib/idlelib/idle.py Does this display some error message? -- nosy: +amaury.forgeotdarc ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3943 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3943] IDLE won't start in 3.0rc1 Subprocess didn't make connection....
Jean-Michel Fauth [EMAIL PROTECTED] added the comment: I think the problem is fixed. See issue 3905. -- nosy: +jmfauth ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3943 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3943] IDLE won't start in 3.0rc1 Subprocess didn't make connection....
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: But #3905 is not yet fixed, furthermore the OP already tried the correction suggested there. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3943 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment:
I've had a chance to do some testing and it _is_ related to the itimer
tests (in test_wait4).
This is with r66550:
$ ./python -E -tt ./Lib/test/regrtest.py -l -v test_wait4 test_signal
test_wait4
test_wait (test.test_wait4.Wait4Test) ... ok
--
Ran 1 test in 5.007s
OK
test_signal
test_getsignal (test.test_signal.BasicSignalTests) ... ok
test_out_of_range_signal_number_raises_error
(test.test_signal.BasicSignalTests) ... ok
test_setting_signal_handler_to_none_raises_error
(test.test_signal.BasicSignalTests) ... ok
test_main (test.test_signal.InterProcessSignalTests) ... FAIL
test_wakeup_fd_during (test.test_signal.WakeupSignalTests) ... ok
test_wakeup_fd_early (test.test_signal.WakeupSignalTests) ... ok
test_siginterrupt_off (test.test_signal.SiginterruptTest) ... ok
test_siginterrupt_on (test.test_signal.SiginterruptTest) ... ok
test_without_siginterrupt (test.test_signal.SiginterruptTest) ... ok
test_itimer_exc (test.test_signal.ItimerTest) ... ok
test_itimer_prof (test.test_signal.ItimerTest) ...
Running only test_signal:
$ ./python -E -tt ./Lib/test/regrtest.py -l -v test_signal
test_signal
test_getsignal (test.test_signal.BasicSignalTests) ... ok
test_out_of_range_signal_number_raises_error
(test.test_signal.BasicSignalTests)
... ok
test_setting_signal_handler_to_none_raises_error
(test.test_signal.BasicSignalTe
sts) ... ok
test_main (test.test_signal.InterProcessSignalTests) ... ok
test_wakeup_fd_during (test.test_signal.WakeupSignalTests) ... ok
test_wakeup_fd_early (test.test_signal.WakeupSignalTests) ... ok
test_siginterrupt_off (test.test_signal.SiginterruptTest) ... ok
test_siginterrupt_on (test.test_signal.SiginterruptTest) ... ok
test_without_siginterrupt (test.test_signal.SiginterruptTest) ... ok
test_itimer_exc (test.test_signal.ItimerTest) ... ok
test_itimer_prof (test.test_signal.ItimerTest) ... ('SIGPROF handler
invoked', (
27, frame object at 0x83c860c))
ok
test_itimer_real (test.test_signal.ItimerTest) ...
call pause()...
('SIGALRM handler invoked', (14, frame object at 0x83c8c0c))
ok
test_itimer_virtual (test.test_signal.ItimerTest) ... ('SIGVTALRM
handler invoke
d', (26, frame object at 0x83c920c))
('SIGVTALRM handler invoked', (26, frame object at 0x83c920c))
('SIGVTALRM handler invoked', (26, frame object at 0x83c920c))
last SIGVTALRM handler call
('SIGVTALRM handler invoked', (26, frame object at 0x83c920c))
ok
--
Ran 13 tests in 6.534s
OK
1 test OK.
Noting the interprocess signal test failure, I tried deactivating it and
the itimer tests still go off into the never never (using all available
CPU cycles too).
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3864
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment: Oops - the itimer tests are in test_signal, not test_wait4. test_wait4 just triggers the problems in test_signal (both the itimer problems and the interprocess signal test failure). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment: After perusing test_wait4, I tried substituting test_fork1 for test_wait4 and got the same behaviour from test_signal. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3885] errors on _bsddb creation and dealloc
Nick Coghlan [EMAIL PROTECTED] added the comment: All of those explanations sound fair to me - with those questions answered, the patch looks good to me. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment:
I compiled the C test case from issue 2240:
$ gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -o test_2240
test_2240.c
{lifted as many gcc options off the standard Python compile as possible}
$ ldd test_2240
test_2240:
libpthread.so.2 = /lib/libpthread.so.2 (0x2807a000)
libc.so.6 = /lib/libc.so.6 (0x2809f000)
$ ./test_2240
0
1 0
deactive ITIMER_PROF
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3864
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3547] Ctypes is confused by bitfields of varying integer types
Thomas Heller [EMAIL PROTECTED] added the comment: Make this a release blocker so hopefully someone will review it. -- priority: - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3935] bisect insort C implementation ignores methods on list subclasses
Changes by Raymond Hettinger [EMAIL PROTECTED]: -- assignee: - rhettinger nosy: +rhettinger priority: - low ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3935 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment: Spelunking with test_fork1, it seems that the interprocess signal test failure is due to the HUP signal not being delivered from the subprocess to the parent (line 99 of test_signal.py: self.assertTrue(self.a_called). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3926] Idle doesn't obey the new improved warnings arguements
Scott David Daniels [EMAIL PROTECTED] added the comment: I found that patch, but it confuses showwarning and formatwarning parameter changes. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3926 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3942] Usability issue from not being able to use defined start and end code block markers
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- resolution: - rejected status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3942 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Guilherme Polo [EMAIL PROTECTED] added the comment: When you say interprocess signal test do you actually mean ItimerTest ? Because I don't see the former failing, and the later hangs because signals are not being delivered to it (SIGVTALRM neither SIGPROF). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3690] sys.getsizeof wrong for Py3k bool objects
Robert Schuppenies [EMAIL PROTECTED] added the comment: Attached is a patch which takes the preallocation of small_ints into account. What do you think? Added file: http://bugs.python.org/file11568/smallints_sizeof.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3690 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3939] Patch to implement a real ftplib test suite
Benjamin Peterson [EMAIL PROTECTED] added the comment: Giampaolo, my review comments are on Rietveld: http://codereview.appspot.com/5698 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3939 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment: From the problematic test run log: ... test_main (test.test_signal.InterProcessSignalTests) ... FAIL ... I should be using the full name, sorry. This failure seems unrelated to the itimer problem though (which is in itimer_test_prof). If I deactivate it, the itimer tests still goes into the never never. Both however are reliably triggered by running test_fork1 or test_wait4 (which uses the same machinery as test_fork1) before test_signal. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Andrew I MacIntyre [EMAIL PROTECTED] added the comment: I should be more specific: itimer_test_prof (test.test_signal.ItimerTest) appears to go into an infinite loop when run after test_fork1 or test_wait4 have been run. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3
Guilherme Polo [EMAIL PROTECTED] added the comment: Last time I checked many more would cause ItimerTest to not run properly, these were: test_asynchat, test_asyncore, test_decimal, text_docxmlrpc, test_ftplib, test_logging, test_poplib, test_queue, test_smtplib, test_socket and all these tests had in common the threading.Event usage. It is possible that I missed other tests, but what I concluded is that freebsd, threads, and itimer doesn't work together :/ ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3864 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3945] compile error in _fileio.c (cygwin)
New submission from Hirokazu Yamamoto [EMAIL PROTECTED]:
Currently, fails to build trunk on cygwin.
gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes -I. -
I/home/WhiteRabbit/python-dev/trunk/./Include -I. -IInclude -I./Include
-I/home/
WhiteRabbit/python-dev/trunk/Include
-I/home/WhiteRabbit/python-dev/trunk -c /ho
me/WhiteRabbit/python-dev/trunk/Modules/_fileio.c -o
build/temp.cygwin-1.5.25-i6
86-2.6/home/WhiteRabbit/python-dev/trunk/Modules/_fileio.o
/home/WhiteRabbit/python-dev/trunk/Modules/_fileio.c:834: error:
initializer ele
ment is not constant
/home/WhiteRabbit/python-dev/trunk/Modules/_fileio.c:834: error: (near
initializ
ation for `PyFileIO_Type.ob_type')
To fix this, attached patch is needed. Or, like py3k, using following
Py_???_HEAD_INIT (surrounded with bracket) might fix this issue in trunk.
#define PyObject_HEAD_INIT(type)\
{ _PyObject_EXTRA_INIT \
1, type },
#define PyVarObject_HEAD_INIT(type, size) \
{ PyObject_HEAD_INIT(type) size },
--
components: Build
files: _fileio.patch
keywords: easy, needs review, patch
messages: 73639
nosy: ocean-city
severity: normal
status: open
title: compile error in _fileio.c (cygwin)
versions: Python 2.6
Added file: http://bugs.python.org/file11569/_fileio.patch
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3945
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3946] PyObject_CheckReadBuffer crashes on memoryview object
New submission from Roger Upole [EMAIL PROTECTED]: Sample code: PyObject *b=PyBytes_FromString(eh ?); PyObject *mv=PyMemoryView_FromObject(b); PyObject_CheckReadBuffer(mv); From following the chain of calls in PyObject_CheckReadBuffer, a few things are unclear. It calls bf_getbuffer with a NULL Py_Buffer pointer, although the PEP explicitely states that is should never be NULL. PyBuffer_FillInfo immediately returns success if the view pointer is NULL. I'm guessing this is to just determine if the operation could be completed, but it returns before any checks are done. It then attempts to release a hardcoded NULL Py_buffer pointer which of course crashes. -- messages: 73640 nosy: rupole severity: normal status: open title: PyObject_CheckReadBuffer crashes on memoryview object ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3937] platform.dist(): detect Linux distribution version in a robust, standard way
Raghuram Devarakonda [EMAIL PROTECTED] added the comment: Please take a look at #1322 for some discussion on this topic. -- nosy: +draghuram ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3937 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3946] PyObject_CheckReadBuffer crashes on memoryview object
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: And the following statement crashes the interpreter: compile(memoryview(btext), name, exec) -- nosy: +amaury.forgeotdarc priority: - critical ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3945] compile error in _fileio.c (cygwin)
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: The patch is OK, even if the second half is not necessary: PyType_Ready() takes care of the ob_type field. Adding brackets in the macro would be wrong: the object layout is different between 2.6 and 3.0. 3.0 does not have this problem because _fileio.c is built-in and linked with the core interpreter (2.6 leaves it in an extension module). -- nosy: +amaury.forgeotdarc ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3945 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2486] Decimal slowdown in 3.0 due to str/unicode changes
Mark Dickinson [EMAIL PROTECTED] added the comment: So I would suggest either a new directory in the sandbox, or re-using Facundo's original directory (which includes the telco benchmark) Makes sense---thanks for the suggestion! But since it seems I don't have any open ssh ports it looks like I'll just have to post a tarball for now. The module is written to work with Python 3.x, on the basis that it's probably easier to backport to 2.x later than to try to maintain two separate versions. On Unix, untar, edit the top line of the Makefile to point to a Python 3.0 executable, and do ./configure make make test runs the decimal test-suite. Added file: http://bugs.python.org/file11570/deccoeff.tar.gz ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2486 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3945] compile error in _fileio.c (cygwin)
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: The patch is OK, even if the second half is not necessary: PyType_Ready() takes care of the ob_type field. Oh, OK. Adding brackets in the macro would be wrong: the object layout is different between 2.6 and 3.0. I Undarstand. How about the attached patch? Added file: http://bugs.python.org/file11571/_fileio.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3945 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3945] compile error in _fileio.c (cygwin)
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: OK, please apply! -- keywords: -needs review resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3945 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3945] compile error in _fileio.c (cygwin)
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: Thanks, fixed in r66566(trunk). -- resolution: accepted - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3945 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1168055] Add current dir when running try_run test program
Steve Lianoglou [EMAIL PROTECTED] added the comment: Sorry to bring up an old issue, but I just got bit by this when trying to install a python package. The `config` command was used to ensure that a certain function was included in the math.h on my cpu before compiling the resulting c binary and python wrapper for it. I had to chase down the problem and basically re-figure out what Michiel did in his patch on my system[1] and override the `try_run` method in the setup.py file. I didn't bother checking the issue tracker assuming distutils is used so widely (and is old enough) that the bug couldn't be in distutiles itself, but must be something I'm doing wrong in my end ... oh well. Anyway, could we somehow try to fix this bug to mitigate some lost time and frustration? Michiel's patch seems reasonable enough to me since it looks to be the least surgery-intensive way (I'm not sure where Phillip would like to put the os.path.abspath() call) to fix the bug for the majority of the time when someone would be bitten by it. Regardless of whether or not the code is well documented, it's still there and usable in distutils (w/o any warnings against its use), so it would make sense to me that we at least have it work as its intended to. [1] My path was slightly different than the submitted patch. Where Michiel has: command = os.path.join(os.curdir, exe) I have: command = os.path.join(os.getcwd(), exe) all in all, you get the same effect -- nosy: +lianos ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1168055 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3947] configure --with-threads on cygwin = crash on thread related tests
New submission from Hirokazu Yamamoto [EMAIL PROTECTED]:
I'm not sure this is python's bug or cygwin's bug, thread enabled python
crashes thread related tests on cygwin. (ex: test_exit on test_sys.py,
test_threading.py etc)
After some investigation, I found following workaround solves this crash.
Index: Modules/_ssl.c
===
--- Modules/_ssl.c (revision 66562)
+++ Modules/_ssl.c (working copy)
@@ -1580,7 +1580,7 @@
/* Init OpenSSL */
SSL_load_error_strings();
-#ifdef WITH_THREAD
+#if defined(WITH_THREAD) !defined(__CYGWIN__)
/* note that this will start threading if not already started */
if (!_setup_ssl_threads()) {
return;
So I applied following patch. (after reverted above workaround)
Index: Modules/_ssl.c
===
--- Modules/_ssl.c (revision 66562)
+++ Modules/_ssl.c (working copy)
@@ -1517,6 +1517,8 @@
lock. They can be useful for debugging.
*/
+printf(--- %d (%u) %s %d: %ul\n, n, mode CRYPTO_LOCK,
file, line, PyThread_get_thread_ident());
+
if ((_ssl_locks == NULL) ||
(n 0) || ((unsigned)n = _ssl_locks_count))
return;
And this is result.
--- 20 (1) mem_dbg.c 161: 6684680l
--- 20 (0) mem_dbg.c 221: 6684680l
--- 20 (1) mem_dbg.c 161: 6684680l
--- 20 (0) mem_dbg.c 221: 6684680l
--- 16 (1) ssl_ciph.c 273: 6684680l
--- 16 (0) ssl_ciph.c 276: 6684680l
--- 16 (1) ssl_ciph.c 277: 6684680l
--- 20 (1) mem_dbg.c 161: 6684680l
--- 20 (0) mem_dbg.c 221: 6684680l
--- 20 (1) mem_dbg.c 161: 6684680l
--- 20 (0) mem_dbg.c 221: 6684680l
--- 16 (0) ssl_ciph.c 308: 6684680l
started worker thread
trying nonsensical thread id
waiting for worker thread to get started
verifying worker hasn't exited
attempting to raise asynch exception in worker
waiting for worker to say it caught the exception
--- 1 (1) err.c 418: 7282896l
all OK -- joining worker
--- 1 (1) err.c 418: 7282896l
6020 [unknown (0x650)] python 1156 _cygtls::handle_exceptions: Error
while du
mping state (probably corrupted stack)
Illegal instruction (core dumped)
Thread 7282896l tries to lock same object twice. I'm not familiar with
OpenSSL nor Python Thread, so I cannot fix this.
# Can callback function for CRYPTO_set_locking_callback() be called like
this? How does PyThread_allocate_lock behave in this situation? I don't
know.
I used OpenSSL0.9.8h installed via cygwin setup.
--
files: a.py
messages: 73649
nosy: ocean-city
severity: normal
status: open
title: configure --with-threads on cygwin = crash on thread related tests
type: crash
versions: Python 2.6
Added file: http://bugs.python.org/file11572/a.py
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3947
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3947] configure --with-threads on cygwin = crash on thread related tests
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: releast25-maint is fine probably because CRYPTO_set_locking_callback() is not used in Modules/_ssl.c. I don't try configure --with-threads on py3k, but probably same on trunk. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3947 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3937] platform.dist(): detect Linux distribution version in a robust, standard way
Zooko O'Whielacronx [EMAIL PROTECTED] added the comment: Here is an updated version of my patch which tries parsing /etc/lsb-release first and only if that fails tries executing lsb_release. The reason is that executing lsb_release in a subprocess takes half-a-second on my high-performance Athlon64 Ubuntu workstation, and also that some installations have /etc/lsb-release but not lsb_release. See the docstring for more details about why to do it this way and exactly what it does. Added file: http://bugs.python.org/file11573/dist.patch.txt ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3937 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3937] platform.dist(): detect Linux distribution version in a robust, standard way
Changes by Gregory P. Smith [EMAIL PROTECTED]: -- dependencies: +platform.dist() has unpredictable result under Linux keywords: +patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3937 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Changes by Gregory P. Smith [EMAIL PROTECTED]: -- dependencies: +platform.dist(): detect Linux distribution version in a robust, standard way ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Zooko O'Whielacronx [EMAIL PROTECTED] added the comment: Please see also #3937 for a patch which first tries to parse /etc/lsb-release, then tries to execute lsb_release, then falls back to the old behavior of platform.dist(). (Note that parsing the file named /etc/lsb-release is not guaranteed to work by the Linux Standard Base spec, but that executing lsb_release is. On the other hand, the former currently seems to work on more Debian/Ubuntu installations than the latter does, and invoking lsb_release in a subprocess takes significantly more time.) Please see the links to the Linux Standard Base specifications which I posted in #3937. (The specification was originally published in 2001, so most of the Linux systems that future versions of Python will be deployed on were developed long after that specification was written.) My patch, in #3937, is against the python-release25-maint branch. I tested the patch locally and it worked, and then I wrote a patch for my project -- allmydata.org Tahoe -- which does something similar: http://allmydata.org/trac/tahoe/browser/src/allmydata/__init__.py?rev=2976 I committed that change to Tahoe, and it was automatically tested on eleven different systems by our buildbot: http://allmydata.org/buildbot/waterfall The resulting distribution-identification can be seen in the logs of those tests. For any machine on the waterfall, click on the test.log hyperlink and search in text for tahoe versions:. For example, here is the one for our Debian etch machine -- debian, 4.0: http://allmydata.org/buildbot/builders/etch/builds/1205/steps/test/logs/test.log here is the one for the Ubuntu dapper machine -- Ubuntu, 6.06: http://allmydata.org/buildbot/builders/dapper/builds/1773/steps/test/logs/test.log and here is the result for my Ubuntu hardy workstation -- Ubuntu, 8.04: http://allmydata.org/buildbot/builders/zooko%20yukyuk%20hardy/builds/216/steps/test/logs/test.log -- nosy: +zooko ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3937] platform.dist(): detect Linux distribution version in a robust, standard way
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment: As explained in #1322. platform.dist() has been superseded by platform.linux_distribution(). Please check what platform.linux_distribution() returns on your platform using Python 2.6rc2. I'm closing this ticket since it's basically a duplicate of #1322. -- resolution: - duplicate status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3937 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1706863] Failed to build Python 2.5.1 with sqlite3
Roumen Petrov [EMAIL PROTECTED] added the comment: The search for *dll.a is described in paragraph direct linking to a dll here: http://sourceware.org/binutils/docs/ld/WIN32.html -- nosy: +rpetrov ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3936] Faulty suppression of 'as' keyword warning
Koen van de Sande [EMAIL PROTECTED] added the comment: I was wondering why I didn't have any warnings in my code in 2.5, when it started failing with errors on import in 2.6. Now I know. -- nosy: +koen ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Marc-Andre Lemburg [EMAIL PROTECTED] added the comment: Zooko, I think the main reason for the parser in platform.py to fail on Ubuntu is that Ubuntu doesn't ship with a /etc/ubuntu-release file and instead uses the optional override parameters in /etc/lsb-release to setup the distribution values. E.g. on my Ubuntu box it has these lines: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION=Ubuntu 7.10 I guess we'll need to add a special parser for lsb-release files which then gets tried *after* having tried the /etc/distro-release files (this is how the lsb_release command works as well) and overrides any settings found in the distro-release file. If that doesn't work either, the function will need to fallback to _dist_try_harder(). There's no need to start a subprocess for running lsb_release. Please also note that the subprocess module is not available in Python 2.1, so it's not an option anyway (platform.py defines it's own popen() helper which should be used instead). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3885] errors on _bsddb creation and dealloc
Jesús Cea Avión [EMAIL PROTECTED] added the comment: Thanks. Committed as r66568. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3824] test_tarfile fails on cygwin (unicode decode error)
Roumen Petrov [EMAIL PROTECTED] added the comment: What is test result if the environment variable LANG is set to C ? -- nosy: +rpetrov ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3824 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Zooko O'Whielacronx [EMAIL PROTECTED] added the comment:
Okay, per MAL's request over on #3937, I tried
platform.get_linux_distribution() on the current svn trunk (which I
assume is the version that is about to become python 2.6). It gave the
same not-so-great answer as platform.dist() used to: ('debian',
'lenny/sid', ''). I then ported my patch to trunk (attached), and it
gave the answer I wanted: ('Ubuntu', '8.04', 'hardy').
Note that technique of parsing /etc/lsb-release or invoking lsb_release
is more standard and generic and easier to maintain than the current
technique of trying a series of specific file parses for specific
supported distributions. For example, if some new Linux distribution
is invented, or if this is tried on a distribution that isn't in the
supported list (has anyone tried this on Foresight Linux yet?), then my
technique has a good chance of working on that distribution, where the
current technique has a higher chance of accidentally mis-identifying it
as some other distribution, for example the way that the current trunk
mis-identifies Ubuntu 8.04 as Debian lenny/sid.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1322
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Changes by Zooko O'Whielacronx [EMAIL PROTECTED]: Added file: http://bugs.python.org/file11574/dist.patch.txt ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Zooko O'Whielacronx [EMAIL PROTECTED] added the comment: MAL: why do you say it is better to look for /etc/$supportedplatform-release files first instead of looking for /etc/lsb-release first? I do not know if /etc/lsb-release is suitably generic -- I've tried it only on a few platforms. I do know that executing lsb_release is suitably generic since it is standard, but I prefer not to try it first since it imposes about half-a-second delay. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1322] platform.dist() has unpredictable result under Linux
Zooko O'Whielacronx [EMAIL PROTECTED] added the comment: Because that's exactly what lsb_release does as well. You must know something about common lsb_release implementations that I don't. As far as I saw in the LSB documentation, it is required to print out information in a certain format, but how it is implemented is totally up to the distribution in question. You give examples of SuSE and Fedora as not having /etc/lsb-release files, and I'm sure you are right, but I happen to know that both of them have compliant lsb_release executables (and that they have had for many releases). So, the patch that I've submitted will definitely work correctly for those two distributions, although it will pay the price of having to spawn a subprocess and then wait for the lsb_release executable to do its work (however it does it). However, presumably your SuSE- and Fedora- specific techniques will give correct answers on those platforms faster than the generic lsb_release would. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1322 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1706863] Failed to build Python 2.5.1 with sqlite3
Roumen Petrov [EMAIL PROTECTED] added the comment: I think that modification has to be in cygwinccompiler. It is specific for win32 binutils and impact both - cygwin and mingw. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3948] readline steals sigwinch
New submission from Shish [EMAIL PROTECTED]: I have an app which wants to use a mostly curses interface with some parts readline, however, doing so much as import readline causes readline to claim ownership of sigwinch, thus breaking the ability of the app to resize. Worse, it seems to claim it at the C level -- doing signal.getsignal (signal.SIGWINCH) returns SIG_DFL, so I can't see anything I can do at the python level to manually set the signals to be handled in the way I want :-/ I would think it best to set the handler at the start (for compatability, and because the vast majority of apps will expect it that way), but set it via python's signal module, so that app writers can take the signal handler and call it in their own way (In my case, I want the app to listen for the signal, and the app's handler will call readline's and curses's handlers in turn) -- components: Extension Modules messages: 73667 nosy: shish severity: normal status: open title: readline steals sigwinch type: behavior versions: Python 2.4 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3948 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3949] curses' sigwinch handler isn't visible from python
New submission from Shish [EMAIL PROTECTED]: after the first initscr() sigwinch is handled as expected, but then my app needs to ignore sigwinch, leave curses to view the output from something, come back into curses, and start listening for sigwinch again. The signal(SIGWINCH, SIG_IGN) call doesn't return the old, working signal handler; it returns 0 -- thus trying to re-set the signal handler doesn't work. (The reason for ignoring the signal is that if the window is resized while the external app is running, python's wait() is interrupted) Having the handler visible from python would also make curses play nicer with readline, as the app could mediate signal handling (see issue #3948) -- components: Extension Modules messages: 73668 nosy: shish severity: normal status: open title: curses' sigwinch handler isn't visible from python versions: Python 2.4 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3949 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3885] errors on _bsddb creation and dealloc
Changes by Jesús Cea Avión [EMAIL PROTECTED]: -- resolution: - fixed status: open - closed type: - crash ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3946] PyObject_CheckReadBuffer crashes on memoryview object
Benjamin Peterson [EMAIL PROTECTED] added the comment: Attaching patch and test. -- keywords: +needs review, patch nosy: +benjamin.peterson Added file: http://bugs.python.org/file11576/no_null_view.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3946 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3936] Faulty suppression of 'as' keyword warning
Benjamin Peterson [EMAIL PROTECTED] added the comment: Attaching patch and test. -- keywords: +needs review, patch nosy: +benjamin.peterson priority: - high Added file: http://bugs.python.org/file11577/fix_warning_after_import.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3885] errors on _bsddb creation and dealloc
Jesús Cea Avión [EMAIL PROTECTED] added the comment: Would be nice to use that fuzzer myself. Details, please :). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3950] turtle.py: bug in TurtleScreenBase._drawimage
New submission from Gregor Lingl [EMAIL PROTECTED]: In the first line of TurtleScreenBase._drawimage() there are to scalefactors missing. This leads to the annoying fact, that the drawings and the movement of a turtle which has an image shape differ. This is shown in the short script _drawimage_bug_fix-test.py which I'll submit immediately. (You have to have huhn.gif in the same directory as the script.) After applying the bugfix submitted in _drawimage_patch.diff this annoying behaviour goes away. It is really an ambarassing and easy to fix bug. Regards, Gregor -- files: _drawimage-patch.diff keywords: patch messages: 73673 nosy: gregorlingl, loewis severity: normal status: open title: turtle.py: bug in TurtleScreenBase._drawimage Added file: http://bugs.python.org/file11578/_drawimage-patch.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3950 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3950] turtle.py: bug in TurtleScreenBase._drawimage
Changes by Gregor Lingl [EMAIL PROTECTED]: -- type: - behavior versions: +Python 2.6 Added file: http://bugs.python.org/file11579/_drawimage_bug_fix_test.py ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3950 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3950] turtle.py: bug in TurtleScreenBase._drawimage
Changes by Gregor Lingl [EMAIL PROTECTED]: Added file: http://bugs.python.org/file11580/huhn.gif ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3950 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2445] Use The CygwinCCompiler Under Cygwin
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: # I found this infomation via svn blame According to issue403947, cygwin once used CygwinCCompiler, and problem was there, swiched to UnixCCompier. (r19674) If this issue is not solved yet, maybe it's not good to go back to CygwinCCompiler. (maybe) -- nosy: +ocean-city ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2445 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1706863] Failed to build Python 2.5.1 with sqlite3
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: Python is not using CCygwinCCompiler to build itself on cygwin. See issue2445. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706863 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3885] errors on _bsddb creation and dealloc
STINNER Victor [EMAIL PROTECTED] added the comment: Would be nice to use that fuzzer myself. Details, please :). It's not the best place to explain it, so I will try explain shortly: * install fusil 1.0: use mandriva/debian packages, or use sources * (create fusil user group) * run sudo fusil-python --module=_bsddb The best way is to use the trunk version (without installation)! cd your fusil home svn co http://python-ptrace.hachoir.org/svn/trunk python-ptrace svn co http://fusil.hachoir.org/svn/trunk fusil export PYTHONPATH=$PWD/python-ptrace/ptrace:$PWD/fusil:$PYTHONPATH sudo your python interpreter ./fusil/fuzzer/fusil-python --module=_bsddb (refer to python-ptrace/INSTALL and fusil/INSTALL) You have to run the fuzzer as root to be able to run child processes as the fusil user. Never run fusil as root or it will kill you(r computer)! See also http://fusil.hachoir.org/trac/wiki/Contact ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3885 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3187] os.listdir can return byte strings
Benjamin Peterson [EMAIL PROTECTED] added the comment: Here's another patch. It simply propagates the UnicodeDecodeErrors. I like this because it avoids silent ignoring problem, and people can get bytes if they want by passing in a bytes path. Added file: http://bugs.python.org/file11581/raise_decoding_errors.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3936] Faulty suppression of 'as' keyword warning
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: I would be more comfortable if started = 1 was also executed in the NEWLINE case. I'm not sure to understand the exact use of its value. And do you think if it's possible to add the type==SEMICOLON case? This would properly show the warning for: import sys; as = 3# on the same line There are still some far-fetched constructs that do not warn, like: import sys as as but they are probably not worth the trouble. -- nosy: +amaury.forgeotdarc ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3187] os.listdir can return byte strings
Guido van Rossum [EMAIL PROTECTED] added the comment: Hmm... much of the os.path machinery (and os.walk) probably doesn't work with bytes, and neither do fnmatch.py and glob.py, I expect. Plus io.open() refuses bytes for the filename, even though _fileio accepts them. The latter should be fixed regardless, and one of the attachments here has a fix IIRC. Gotta run, sorry. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3824] test_tarfile fails on cygwin (unicode decode error)
Hirokazu Yamamoto [EMAIL PROTECTED] added the comment: What is test result if the environment variable LANG is set to C ? There is no change. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3824 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3939] Patch to implement a real ftplib test suite
Giampaolo Rodola' [EMAIL PROTECTED] added the comment: Patch modified after the remarks discussed with Benjamin is in attachment. Added file: http://bugs.python.org/file11582/test_ftplib.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3939 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3951] Disable Py_USING_MEMORY_DEBUGGER!
New submission from STINNER Victor [EMAIL PROTECTED]: In rev 56476, martin.v.loewis enabled Py_USING_MEMORY_DEBUGGER by default in an huge commit: PEP 3123: Provide forward compatibility with Python 3.0, while keeping backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT. I guess that's an error, and that Py_USING_MEMORY_DEBUGGER should be disabled by default. Proposition to avoid such bug in future: create a configure option, like --with-memory-debugger. See for example my patch to configure.in (you will need to run autoconf autoheader). -- files: configure-memory-debugger.patch keywords: patch messages: 73683 nosy: haypo severity: normal status: open title: Disable Py_USING_MEMORY_DEBUGGER! versions: Python 2.6, Python 3.0 Added file: http://bugs.python.org/file11583/configure-memory-debugger.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3951] Disable Py_USING_MEMORY_DEBUGGER!
Changes by STINNER Victor [EMAIL PROTECTED]: Added file: http://bugs.python.org/file11584/obmalloc-no-debug.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3825] Major reworking of Python 2.5.2 re module
Matthew Barnett [EMAIL PROTECTED] added the comment: Patch regex_2.6rc2+5.diff adds scoped and 'negative' flags for (?i), (?m) and (?s). The other flags remain unchanged in behaviour. See #433024, #433027 and #433028. Added file: http://bugs.python.org/file11585/regex_2.6rc2+5.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3825 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue433024] SRE: (?flag) isn't properly scoped
Matthew Barnett [EMAIL PROTECTED] added the comment: Implemenetd in #3825. -- nosy: +mrabarnett ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue433024 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue433027] SRE: (?-flag) is not supported.
Matthew Barnett [EMAIL PROTECTED] added the comment: Implemented in #3825. -- nosy: +mrabarnett ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue433027 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue433028] SRE: (?flag:...) is not supported
Matthew Barnett [EMAIL PROTECTED] added the comment: Implemented in #3825. -- nosy: +mrabarnett ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue433028 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3187] os.listdir can return byte strings
STINNER Victor [EMAIL PROTECTED] added the comment: Guido compiled my patches here: http://codereview.appspot.com/3055 My patches allows bytes for fnmatch.filter(), glob.glob1(), os.path.join() and open(). ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3952] _lsprof: clear() should call flush_unmatched()
New submission from STINNER Victor [EMAIL PROTECTED]: Example to reproduce the bug (using Python trunk): --- from gc import collect import _lsprof def callMethod(obj): obj.clear() collect() obj = _lsprof.Profiler() obj.enable() callMethod(obj) obj.enable() del obj collect() --- The problem is that the profiler is still running when exiting callMethod() and so it tries to use callMethod context which was free'd just before by profiler_clear(). -- files: _lsprof_clear.patch keywords: patch messages: 73689 nosy: haypo severity: normal status: open title: _lsprof: clear() should call flush_unmatched() versions: Python 2.6, Python 3.0 Added file: http://bugs.python.org/file11586/_lsprof_clear.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3952 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3825] Major reworking of Python 2.5.2 re module
Matthew Barnett [EMAIL PROTECTED] added the comment: Patch regex_2.6rc2+6.diff is a bugfix. Added file: http://bugs.python.org/file11587/regex_2.6rc2+6.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3825 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3951] Disable Py_USING_MEMORY_DEBUGGER!
Changes by Benjamin Peterson [EMAIL PROTECTED]: -- assignee: - loewis nosy: +loewis ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3951] Disable Py_USING_MEMORY_DEBUGGER!
Martin v. Löwis [EMAIL PROTECTED] added the comment: You are right that this was by mistake; here is a patch to revert that mistake (revert.diff). I'm marking the issue release-critical because of thsi patch; the other patches (for adding a new configure option) clearly can't go into 2.6, and might need to be deferred to 2.7. -- keywords: +needs review priority: - release blocker Added file: http://bugs.python.org/file11588/revert.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3951 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
