[issue12455] urllib2 forces title() on header names, breaking some requests
Senthil Kumaran sent...@uthcode.com added the comment: AFAIR, that capitalize part is somewhere a requirement in RFC, if the server did not behave in proper manner, it may not be a good idea for the client to change (or be permissive the flag). -- nosy: +orsenthil ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12455 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12455] urllib2 forces title() on header names, breaking some requests
Senthil Kumaran sent...@uthcode.com added the comment: Sorry, not Capitalize, but the Title part. One can some bugs which lead to this change in the urllib2. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12455 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
New submission from Ulrich Eckhardt eckha...@satorlaser.com: For reference, see the thread on the users' mailinglist/newsgroup from 2011-06-29 how to call a function for evry 10 seconds and the thread on the developers' mailinglist from 2011-06-30 time.sleep(-1) behaviour. The problem is how negative arguments to time.sleep() are handled. Python 2.x (tested 2.5 and 2.7) implementations on MS Windows seems to have a 32-bit underflow while converting the given argument to the DWORD that is passed to win32's Sleep() function. This causes a small negative value to sleep for a long time. On Linux, using Python 2.6, you get an IOError instead. While an error is better than blocking effectively forever, the use of an IOError to signal the wrong argument is at least confusing. I guess it is an artifact of the implementation, but that shouldn't be visible prominently. IMHH, both versions should raise a ValueError to signal invalid arguments. However, there was also the suggestion to simply treat negative values as zero, after all time.sleep() is already documented to possibly sleep longer than specified. -- messages: 139548 nosy: eckhardt priority: normal severity: normal status: open title: time.sleep(-1.0) behaviour type: behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12450] Use the Grisu algorithms to convert floats to strings
Mark Dickinson dicki...@gmail.com added the comment: [Amaury] It would be interesting to see if it is better/faster than the current dtoa. I agree that it would be interesting to compare. [Eric] maybe we can say we we can live with 99.5% shortest repr coverage Please no! As you say, we'd still need the fallback code. For me, a precondition for actually switching (rather than just investigating speed differences) would be that the Grisu3 code has excellent tests. The dtoa.c code is still pretty hairy in places but is now fairly well tested and inspected; I'd hesitate to replace that with something less well exercised. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12457] type() returns incorrect type for nested classes
R. David Murray rdmur...@bitdance.com added the comment: Inner classes can't be pickled (see the pickle docs for what can be pickled). Whether or not there is a bug in the repr of the inner class is an interesting question. -- nosy: +r.david.murray type: crash - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12457 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12455] urllib2 forces title() on header names, breaking some requests
R. David Murray rdmur...@bitdance.com added the comment: Quoting http://tools.ietf.org/html/rfc2068#section-4.2: Field names are case-insensitive. Which is only logical, since they are modeled on email headers, and email header names are case insensitive. So, the server in question is broken, yes, but that doesn't mean we can't provide a facility to allow Python to inter-operate with it. Email, for example, preserves the case of the field names it parses or receives from the application program, but otherwise treats them case-insensitively. However, since the current code coerces to title case, we have to provide this feature as a switchable facility defaulting to the current behavior, for backward compatibility reasons. And someone needs to write a patch -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12455 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
Changes by Raymond Hettinger raymond.hettin...@gmail.com: -- assignee: - rhettinger nosy: +rhettinger priority: normal - low ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12450] Use the Grisu algorithms to convert floats to strings
Raymond Hettinger raymond.hettin...@gmail.com added the comment: I concur with Mark. This is a very challenging area and no change would be warranted without keeping the current accuracy guarantees, definitive speed improvement, extensive tests, and consideration of the impact on users of having float reprs change yet again. This was a nice tracker item for improving our awareness of alternate algorithms, but it isn't a credible feature request without the qualities listed above. I'll mark this as closed/rejected. Feel free to reopen if we get some solid evidence that python would be significantly improved enough to warrant the disruption for users and the investment of developer time. -- resolution: - rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12442] shutil.disk_usage()
Giampaolo Rodola' g.rod...@gmail.com added the comment: Agreed. New patch removes the percentage and fixes computations on posix as recommended by Charles-François: free = st.f_bavail * st.f_bsize total = st.f_blocks * st.f_frsize used = (total - st.f_bfree * st.f_bsize) -- Added file: http://bugs.python.org/file22532/diskusage3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12442 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Huzaifa Sidhpurwala sidhpurwala.huza...@gmail.com added the comment: It seems python was being blamed for what is essentially the fault of lynx. The following would translate into browsing files locally from the system and not from the web: lynx http://localhost:8000/../../../../../../../../etc/passwd The correct syntax for testing should have been: lynx http://localhost:8000/../../../../../../../../etc/passwd -- nosy: +Huzaifa.Sidhpurwala ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12450] Use the Grisu algorithms to convert floats to strings
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: Agreed. If some volunteer wants to work on it, I suggest to make an extension module first, so that everybody can try and compare with the current routines. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11197] information leakage with SimpleHTTPServer
Huzaifa Sidhpurwala sidhpurwala.huza...@gmail.com added the comment: This should have been lynx localhost:8000/../../../../../../../../etc/passwd v/s lynx http://localhost:8000/../../../../../../../../etc/passwd -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11197 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12460] SocketServer.shutdown() does not have timeout=None parameter
New submission from Марк Коренберг socketp...@gmail.com: Suppose i'm trying to correctly terminate thread with socketserver during application termination. I do not want to wait too long (also do not want to hang), I want to protect against long-lived operations in SimpleServer so something like myserver.shutdown(2) will be nice. Also it should return True or False depending on successfull shutting down. It's easy to implement - thanks to Threading.event.wait(timeout=...) Don't know if it is applicable to python 3.x -- components: Library (Lib) messages: 139557 nosy: mmarkk priority: normal severity: normal status: open title: SocketServer.shutdown() does not have timeout=None parameter type: feature request versions: Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12460 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
STINNER Victor victor.stin...@haypocalc.com added the comment: I think that time.sleep() should behave as select.select() (issue #11757, commit 3982be773b54) and signal.sigtimedwait(): raise a ValueError if the timeout is negative. A good reason to always raise an error is that floatsleep() has different implementations. Especially, the select() implementation behaves differently depending on the platform: negative timeout raises an error (select.error(22, 'Invalid argument')) or returns immediatly. Attached patch raises an error if the time length is negative. It avoids the integer overflow in the Windows implementation. -- keywords: +patch nosy: +haypo Added file: http://bugs.python.org/file22533/sleep_negative.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
Antoine Pitrou pit...@free.fr added the comment: I agree with the ValueError suggestion. Since it would slightly change existing behaviour, it can only be done in a feature release (3.3). According to Google Code Search, deliberate uses of sleep(-1) are almost non-existent: http://www.google.com/codesearch#search/q=%22sleep%28-1%29%22%20lang:pythontype=cs -- components: +Extension Modules nosy: +pitrou stage: - patch review versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
STINNER Victor victor.stin...@haypocalc.com added the comment: According to Google Code Search, deliberate uses of sleep(-1) are almost non-existent: The search gives two results, in pycaf and a plone installer (in compilezpy.py). I don't know what is the expected behaviour: infinite sleep? wait for a SIGINT signal? I'm ok to only change this in Python 3.3, it's not a good idea to introduce subtle differences in minor Python releases. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12461] it's not clear how the shutil.copystat() should work on symlinks
New submission from Марк Коренберг socketp...@gmail.com: According to http://hg.python.org/cpython/file/588fe0fc7160/Lib/shutil.py it uses utimes(), stat() ans so on, For some people, it's preferable to use lutimes() and lstat(),but for some people it's not. For example, in old implementation, exception will raise on broken symlink during os.utime(). Also, copystat() does not check that chown can not be applied to a symlink. I do not think that it's good to add two parameters like shutil.copystat(src, dst, followsrc, followdst) Adding just one parameter (followsymlinks) is not sufficient. -- components: Library (Lib) messages: 139561 nosy: mmarkk priority: normal severity: normal status: open title: it's not clear how the shutil.copystat() should work on symlinks type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12461 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
New submission from STINNER Victor victor.stin...@haypocalc.com: While reading floatsleep() (time.sleep) code for issue #12459, I noticed that the Python signal handler is not called in floatsleep() if a signal interrupted the sleep. Well, it just works because the bytecode evaluation loop will call PyErr_CheckSignals() before executing the next instruction (the C signal handler signals calls Py_AddPendingCall whichs signals that the pending call to the eval loop using eval_breaker), but it would be better to call it directly. Attached calls explicitly and immediatly PyErr_CheckSignals() in the sleep and Windows implementations of floatsleep(). It's not really a bug, so I prefer to not touch Python 2.7 and 3.2, only Python 3.3. -- components: Library (Lib) files: sleep_signal.patch keywords: patch messages: 139562 nosy: haypo, pitrou priority: normal severity: normal status: open title: time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted versions: Python 3.3 Added file: http://bugs.python.org/file22534/sleep_signal.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
STINNER Victor victor.stin...@haypocalc.com added the comment: See also #12462, I found something weird in the signal handling of floatsleep(). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
Antoine Pitrou pit...@free.fr added the comment: You don't *need* to call PyErr_CheckSignals() explicitly, PyErr_SetFromErrno() does it for you. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12463] Calling SocketServer.shutdown() when server_forever() was not called will hang
New submission from Марк Коренберг socketp...@gmail.com: Why not to call self.__is_shut_down.set() in constructor ? In reality, if event loop was not started, it mean that server is shut down. -- components: Library (Lib) messages: 139565 nosy: mmarkk priority: normal severity: normal status: open title: Calling SocketServer.shutdown() when server_forever() was not called will hang type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12463 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10647] scrollbar crash in non-US locale format settings
Hans Bering hans.ber...@arcor.de added the comment:
I have been able to reproduce this problem with a current Python 3.2 + tcl/tk
on Ubuntu. I have attached a script which should crash with the following
output stacktrace (you might have to find set a suitable locale depending
on your OS):
locale = ('de_DE', 'UTF8')
Traceback (most recent call last):
File tkinterCrash.py, line 20, in module
tkcanvas = Canvas(master=master, width=w, height=2, borderwidth=4)
File /usr/lib/python3.2/tkinter/__init__.py, line 2101, in __init__
Widget.__init__(self, master, 'canvas', cnf, kw)
File /usr/lib/python3.2/tkinter/__init__.py, line 1961, in __init__
(widgetName, self._w) + extra + self._options(cnf))
_tkinter.TclError: bad screen distance 10.0
The problem seems to stem from the fact that tkinter passes the width option
through regardless of what it is (you can set w to the string hello to get
the same error), and somewhere below (in tk, I guess?), the option argument is
tentatively parsed as a number using the system's numeric locale.
Originally, we stumbled over this problem when using matplotlib, which
passes/passed down float types as width arguments on occasions. It has been
fixed there since (see https://github.com/matplotlib/matplotlib/pull/387).
It's the locale dependency which can make this difficult to debug when it
occurs. In our setup, we had a program running on one machine, and then it
crashed on the next, which we believed to have an identical setup; it took us a
day to figure out what the difference was.
--
nosy: +hans.bering
Added file: http://bugs.python.org/file22535/tkinterCrash.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10647
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
STINNER Victor victor.stin...@haypocalc.com added the comment: The sleep implementation of floatsleep() doesn't call PyErr_SetFromErrno() if errno is EINTR, whereas EINTR indicates that select() was interrupted. I agree that PyErr_CheckSignals() is overkill in the Windows implementation. My new patch is more explicit: only add a special case for the select implementation, if errno is EINTR. -- Added file: http://bugs.python.org/file22536/sleep_signal-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
Antoine Pitrou pit...@free.fr added the comment: My new patch is more explicit: only add a special case for the select implementation, if errno is EINTR. Looks good to me! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12442] shutil.disk_usage()
Roundup Robot devnull@devnull added the comment: New changeset 2fc102ebaf73 by Giampaolo Rodola' in branch 'default': Issue #12442: add shutil.disk_usage() http://hg.python.org/cpython/rev/2fc102ebaf73 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12442 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12442] shutil.disk_usage()
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- resolution: - fixed stage: patch review - commit review status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12442 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
Roundup Robot devnull@devnull added the comment: New changeset 583be15e22ca by Victor Stinner in branch 'default': Issue #12462: time.sleep() now calls immediatly the (Python) signal handler if http://hg.python.org/cpython/rev/583be15e22ca -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12462] time.sleep(1): call PyErr_CheckSignals() if the sleep was interrupted
Changes by STINNER Victor victor.stin...@haypocalc.com: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12460] SocketServer.shutdown() does not have timeout=None parameter
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12460 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12464] tempfile.TemporaryDirectory.cleanup follows symbolic links
New submission from Evgeny Kapun abacabadabac...@gmail.com: TemporaryDirectory.cleanup follows symbolic links to directories and tries to clean them as well. Try this (on Linux): import os, tempfile with tempfile.TemporaryDirectory() as d: os.symlink(/proc, d + /test) -- components: Library (Lib) messages: 139571 nosy: abacabadabacaba priority: normal severity: normal status: open title: tempfile.TemporaryDirectory.cleanup follows symbolic links type: behavior versions: Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12464 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12465] gc.get_referents can be used to crash Python
New submission from Evgeny Kapun abacabadabac...@gmail.com:
This code crashes Python:
import gc
gc.get_referents(object.__dict__)[0].clear()
gc.get_referents(type.__dict__)[0].clear()
type(A, (), {})()
--
components: Interpreter Core
messages: 139572
nosy: abacabadabacaba
priority: normal
severity: normal
status: open
title: gc.get_referents can be used to crash Python
type: crash
versions: Python 2.7, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12465
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
STINNER Victor victor.stin...@haypocalc.com added the comment: Tim Lesher on python-dev: On the Windows side, Sleep(-1) as infinite is correct and documented: http://msdn.microsoft.com/en-us/library/ms686298(v=vs.85).aspx Wine defines INFINITE using #define INFINITE 0x: http://source.winehq.org/source/include/winbase.h -1 becomes INFINITE because of an integer overflow (because of a cast from double to *unsigned* long). time.sleep(-2) doesn't sleep for an infinite time, but for more than 136 years (maybe more in 64 bits?): print(datetime.timedelta(seconds=-2 0x)) 49710 days, 6:28:14 What is the usecase of Sleep(INFINITE)? Wait a signal or wait another event? Because other platforms don't support the INFINITE timeout, I suggest to always raise an error to have the same behaviour on all platforms. On POSIX, you can use pause(), sigwait(), select() or other functions to wait a signal for example. If we something something like that on Windows, we need a new function, but not a magic time.sleep(-1) please. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Roundup Robot devnull@devnull added the comment: New changeset 0ed5e6ff10f8 by Victor Stinner in branch '3.2': Issue #11870: Skip test_threading.test_2_join_in_forked_process() on platforms http://hg.python.org/cpython/rev/0ed5e6ff10f8 New changeset f43dee86fffd by Victor Stinner in branch 'default': (merge 3.2) Issue #11870: Skip test_threading.test_2_join_in_forked_process() http://hg.python.org/cpython/rev/f43dee86fffd -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12466] test_subprocess.test_close_fds() sporadic failures on Mac OS X Tiger
New submission from STINNER Victor victor.stin...@haypocalc.com:
==
FAIL: test_close_fds (test.test_subprocess.POSIXProcessTestCase)
--
Traceback (most recent call last):
File
/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_subprocess.py, line
1302, in test_close_fds
Some fds were left open)
AssertionError: {9} is not false : Some fds were left open
http://www.python.org/dev/buildbot/all/builders/x86%20Tiger%203.x/builds/2825/steps/test/logs/stdio
test_pass_fds() is already skipped on Mac OS X Tiger because of an OS bug: see
issue #12230.
--
messages: 139575
nosy: haypo, pitrou
priority: normal
severity: normal
status: open
title: test_subprocess.test_close_fds() sporadic failures on Mac OS X Tiger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12466
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Roundup Robot devnull@devnull added the comment: New changeset ff36b8cadfd6 by Victor Stinner in branch '2.7': Issue #11870: Skip test_threading.test_2_join_in_forked_process() on platforms http://hg.python.org/cpython/rev/ff36b8cadfd6 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12467] test_threading.test_6_daemon_threads(): Assertion failed: PyUnicode_Check(*filename), file ..\Python\_warnings.c, line 501
New submission from STINNER Victor victor.stin...@haypocalc.com:
==
FAIL: test_6_daemon_threads (test.test_threading.ThreadJoinOnShutdown)
--
Traceback (most recent call last):
File
D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\test\test_threading.py,
line 677, in test_6_daemon_threads
rc, out, err = assert_python_ok('-c', script)
File
D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\test\script_helper.py,
line 50, in assert_python_ok
return _assert_python(True, *args, **env_vars)
File
D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\test\script_helper.py,
line 42, in _assert_python
stderr follows:\n%s % (rc, err.decode('ascii', 'ignore')))
AssertionError: Process return code is 3, stderr follows:
Assertion failed: PyUnicode_Check(*filename), file ..\Python\_warnings.c, line
501
http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/4881/steps/test/logs/stdio
--
components: Library (Lib), Tests, Windows
messages: 139577
nosy: haypo
priority: normal
severity: normal
status: open
title: test_threading.test_6_daemon_threads(): Assertion failed:
PyUnicode_Check(*filename), file ..\Python\_warnings.c, line 501
versions: Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12467
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12455] urllib2 forces title() on header names, breaking some requests
Cal Leeming cal.leem...@simplicitymedialtd.co.uk added the comment: Thats full understandable that the default won't change. I'll put this in my todo list to write a patch in a week or two. On 1 Jul 2011 08:45, R. David Murray rep...@bugs.python.org wrote: R. David Murray rdmur...@bitdance.com added the comment: Quoting http://tools.ietf.org/html/rfc2068#section-4.2: Field names are case-insensitive. Which is only logical, since they are modeled on email headers, and email header names are case insensitive. So, the server in question is broken, yes, but that doesn't mean we can't provide a facility to allow Python to inter-operate with it. Email, for example, preserves the case of the field names it parses or receives from the application program, but otherwise treats them case-insensitively. However, since the current code coerces to title case, we have to provide this feature as a switchable facility defaulting to the current behavior, for backward compatibility reasons. And someone needs to write a patch -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12455 ___ -- nosy: +sleepycal Added file: http://bugs.python.org/file22537/unnamed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12455 ___pThats full understandable that the default won#39;t change. I#39;ll put this in my todo list to write a patch in a week or two./p div class=gmail_quoteOn 1 Jul 2011 08:45, quot;R. David Murrayquot; lt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt; wrote:br type=attributiongt; brgt; R. David Murray lt;a href=mailto:rdmur...@bitdance.com;rdmur...@bitdance.com/agt; added the comment:br gt; brgt; Quoting a href=http://tools.ietf.org/html/rfc2068#section-4.2;http://tools.ietf.org/html/rfc2068#section-4.2/a:brgt; brgt; Field names are case-insensitive.brgt; brgt; Which is only logical, since they are modeled on email headers, and email header names are case insensitive. So, the server in question is broken, yes, but that doesn#39;t mean we can#39;t provide a facility to allow Python to inter-operate with it. Email, for example, preserves the case of the field names it parses or receives from the application program, but otherwise treats them case-insensitively. However, since the current code coerces to title case, we have to provide this feature as a switchable facility defaulting to the current behavior, for backward compatibility reasons.br gt; brgt; And someone needs to write a patchbrgt; brgt; --brgt; brgt; ___brgt; Python tracker lt;a href=mailto:rep...@bugs.python.org;rep...@bugs.python.org/agt;br gt; lt;a href=http://bugs.python.org/issue12455;http://bugs.python.org/issue12455/agt;brgt; ___br/div ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12363] test_signal.test_without_siginterrupt() sporadic failures on FreeBSD 6.4
Roundup Robot devnull@devnull added the comment: New changeset 8250f04d5a41 by Victor Stinner in branch '3.2': Issue #12363: improve siginterrupt() tests http://hg.python.org/cpython/rev/8250f04d5a41 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12363 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12400] regrtest: always run tests in verbose mode, but hide the output on success
STINNER Victor victor.stin...@haypocalc.com added the comment: Ok, no more regression / bug related to this issue, let close it. -- resolution: - fixed status: open - closed versions: -Python 2.7, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12231] regrtest: add -k and -K options to filter tests by function/file names
STINNER Victor victor.stin...@haypocalc.com added the comment: regrtest_regex-2.patch: minor update, just ensure that the patch applies correctly on the default branch. -- Added file: http://bugs.python.org/file22538/regrtest_regex-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12231 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12363] test_signal.test_without_siginterrupt() sporadic failures on FreeBSD 6.4
Roundup Robot devnull@devnull added the comment: New changeset 3f30cfe51315 by Victor Stinner in branch '3.2': Issue #12363: increase the timeout of siginterrupt() tests http://hg.python.org/cpython/rev/3f30cfe51315 New changeset 423268537083 by Victor Stinner in branch 'default': (merge 3.2) Issue #12363: increase the timeout of siginterrupt() tests http://hg.python.org/cpython/rev/423268537083 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12363 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
STINNER Victor victor.stin...@haypocalc.com added the comment: The initial problem was test_3_join_in_forked_from_thread() and the hangs does still happen: [324/356] test_threading Timeout (1:00:00)! Thread 0x404248c0: File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 1498 in _communicate_with_poll File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 1423 in _communicate File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 836 in communicate File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/script_helper.py, line 32 in _assert_python File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/script_helper.py, line 50 in assert_python_ok File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 434 in _run_and_join File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 493 in test_3_join_in_forked_from_thread File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 407 in _executeTestPart File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 462 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 514 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 105 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 67 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 105 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 67 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/runner.py, line 168 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/support.py, line 1259 in _run_suite File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/support.py, line 1285 in run_unittest File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 774 in test_main File ./Lib/test/regrtest.py, line 1070 in runtest_inner File ./Lib/test/regrtest.py, line 861 in runtest File ./Lib/test/regrtest.py, line 669 in main File ./Lib/test/regrtest.py, line 1648 in module http://www.python.org/dev/buildbot/all/builders/x86%20Ubuntu%20Shared%203.x/builds/4081/steps/test/logs/stdio (neologix's patch doesn't change anything for x86 Ubuntu Shared 3.x buildbot, which is a Linux, not a FreeBSD) I don't know why it only hangs on this Linux buildbot. It's maybe an old Linux kernel, an old GNU libc version, or something like that? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Charles-François Natali neolo...@free.fr added the comment: Well, I ping my view that we should: Could you please detail the following points: - what would be the API of this atfork() mechanism (with an example of how it would be used in the library)? - how do you find the correct order to acquire locks in the parent process? - what do you do with locks that can be held for arbitrarily long (e.g. I/O locks)? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11873] test_regexp() of test_compileall fails occassionally
Roundup Robot devnull@devnull added the comment: New changeset f8ece8c93918 by R David Murray in branch '3.2': #11873: fix test regex so it covers windows os.sep as well. http://hg.python.org/cpython/rev/f8ece8c93918 New changeset e543c0ddec63 by R David Murray in branch 'default': merge #11873: fix test regex so it covers windows os.sep as well. http://hg.python.org/cpython/rev/e543c0ddec63 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11873] test_regexp() of test_compileall fails occassionally
R. David Murray rdmur...@bitdance.com added the comment: Yeah, that's why I had reopened the issue...hopefully it is fixed now. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9253] argparse: optional subparsers
Changes by Dan Sully dsu...@gmail.com: -- nosy: +dsully ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9253 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12291] file written using marshal in 3.2 can be read by 2.7, but not 3.2 or 3.3
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12346] Python source code build fails with old mercurial
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12346 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12457] type() returns incorrect type for nested classes
Changes by Daniel Urban urban.dani...@gmail.com: -- nosy: +durban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12457 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12456] Hangs in concurrent.futures
Antoine Pitrou pit...@free.fr added the comment: This patch should fix the issue. Can you confirm? -- keywords: +patch stage: - patch review Added file: http://bugs.python.org/file22539/cfshutdown.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12456 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12346] Python source code build fails with old mercurial
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12346 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12213] BufferedRandom, BufferedRWPair: issues with interlaced read-write
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12213 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12215] TextIOWrapper: issues with interlaced read-write
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12291] file written using marshal in 3.2 can be read by 2.7, but not 3.2 or 3.3
Antoine Pitrou pit...@free.fr added the comment: Latest patch looks ok to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12291 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11873] test_regexp() of test_compileall fails occassionally
R. David Murray rdmur...@bitdance.com added the comment: I guess I'm just really bad at regexes. http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/4885/steps/test/logs/stdio -- status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12468] longjmp causes uninitialized stack frame
New submission from Kiril Mikos kiril.mik...@gmail.com: *** longjmp causes uninitialized stack frame ***: /usr/bin/python2.7 terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f2415de61d7] /lib/x86_64-linux-gnu/libc.so.6(+0xfe169)[0x7f2415de6169] /lib/x86_64-linux-gnu/libc.so.6(__longjmp_chk+0x33)[0x7f2415de60d3] /usr/lib/libcurl-gnutls.so.4(+0xbb45)[0x7f241528bb45] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfc60)[0x7f2416f11c60] /lib/x86_64-linux-gnu/libpthread.so.0(sem_wait+0x30)[0x7f2416f0fea0] /usr/bin/python2.7(PyThread_acquire_lock+0x11)[0x4aed31] /usr/bin/python2.7[0x4afd3e] /usr/bin/python2.7(PyEval_EvalFrameEx+0x361)[0x4965f1] /usr/bin/python2.7(PyEval_EvalCodeEx+0x145)[0x49d325] /usr/bin/python2.7(PyEval_EvalFrameEx+0x802)[0x496a92] /usr/bin/python2.7(PyEval_EvalCodeEx+0x145)[0x49d325] /usr/bin/python2.7(PyEval_EvalFrameEx+0x802)[0x496a92] /usr/bin/python2.7(PyEval_EvalCodeEx+0x145)[0x49d325] /usr/bin/python2.7[0x4c4526] /usr/bin/python2.7(PyObject_Call+0x44)[0x45d864] /usr/bin/python2.7[0x45f43f] /usr/bin/python2.7[0x45b8ff] /usr/bin/python2.7(PyObject_CallMethod+0xa8)[0x4c7e68] /usr/bin/python2.7(Py_Finalize+0x4a)[0x42cf19] /usr/bin/python2.7(Py_Main+0xb5d)[0x418d32] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xff)[0x7f2415d06eff] /usr/bin/python2.7[0x4c62b1] === Memory map: 0040-0062f000 r-xp 08:13 524506 /usr/bin/python2.7 0082e000-0082f000 r--p 0022e000 08:13 524506 /usr/bin/python2.7 0082f000-00897000 rw-p 0022f000 08:13 524506 /usr/bin/python2.7 00897000-008a9000 rw-p 00:00 0 02243000-024f3000 rw-p 00:00 0 [heap] 7f2408ffa000-7f2408ffb000 ---p 00:00 0 7f2408ffb000-7f24097fb000 rw-p 00:00 0 7f24097fb000-7f24097fc000 ---p 00:00 0 7f24097fc000-7f2409ffc000 rw-p 00:00 0 7f2409ffc000-7f2409ffd000 ---p 00:00 0 7f2409ffd000-7f240a7fd000 rw-p 00:00 0 7f240a7fd000-7f240a7fe000 ---p 00:00 0 7f240a7fe000-7f240affe000 rw-p 00:00 0 7f240affe000-7f240afff000 ---p 00:00 0 7f240afff000-7f240b7ff000 rw-p 00:00 0 7f240b7ff000-7f240b80 ---p 00:00 0 7f240b80-7f240c00 rw-p 00:00 0 7f240c00-7f240c047000 rw-p 00:00 0 7f240c047000-7f241000 ---p 00:00 0 7f24100fb000-7f241011 r-xp 08:13 1317460 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f241011-7f241030f000 ---p 00015000 08:13 1317460 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f241030f000-7f241031 r--p 00014000 08:13 1317460 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f241031-7f2410311000 rw-p 00015000 08:13 1317460 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f2410311000-7f2410352000 rw-p 00:00 0 7f2410352000-7f2410353000 ---p 00:00 0 7f2410353000-7f2410b53000 rw-p 00:00 0 7f2410b53000-7f2410b54000 ---p 00:00 0 7f2410b54000-7f2411354000 rw-p 00:00 0 7f2411354000-7f2411355000 ---p 00:00 0 7f2411355000-7f2411b55000 rw-p 00:00 0 7f2411b55000-7f2411b56000 ---p 00:00 0 7f2411b56000-7f2412458000 rw-p 00:00 0 7f2412458000-7f241247f000 r-xp 08:13 1317525 /lib/x86_64-linux-gnu/libexpat.so.1.5.2 7f241247f000-7f241267f000 ---p 00027000 08:13 1317525 /lib/x86_64-linux-gnu/libexpat.so.1.5.2 7f241267f000-7f2412681000 r--p 00027000 08:13 1317525 /lib/x86_64-linux-gnu/libexpat.so.1.5.2 7f2412681000-7f2412682000 rw-p 00029000 08:13 1317525 /lib/x86_64-linux-gnu/libexpat.so.1.5.2 7f2412682000-7f2412691000 r-xp 08:13 538071 /usr/lib/python2.7/lib-dynload/pyexpat.so 7f2412691000-7f241289 ---p f000 08:13 538071 /usr/lib/python2.7/lib-dynload/pyexpat.so 7f241289-7f2412891000 r--p e000 08:13 538071 /usr/lib/python2.7/lib-dynload/pyexpat.so 7f2412891000-7f2412893000 rw-p f000 08:13 538071 /usr/lib/python2.7/lib-dynload/pyexpat.so 7f2412893000-7f24128a6000 r-xp 08:13 538046 /usr/lib/python2.7/lib-dynload/datetime.so 7f24128a6000-7f2412aa6000 ---p 00013000 08:13 538046 /usr/lib/python2.7/lib-dynload/datetime.so 7f2412aa6000-7f2412aa7000 r--p 00013000 08:13 538046 /usr/lib/python2.7/lib-dynload/datetime.so 7f2412aa7000-7f2412aab000 rw-p 00014000 08:13 538046 /usr/lib/python2.7/lib-dynload/datetime.so 7f2412aab000-7f2412aec000 rw-p 00:00 0 7f2412aec000-7f2412b09000 r-xp 08:13 538049 /usr/lib/python2.7/lib-dynload/_io.so 7f2412b09000-7f2412d08000 ---p 0001d000 08:13 538049
[issue12468] longjmp causes uninitialized stack frame
Eric V. Smith e...@trueblade.com added the comment: Do you have a python code snippet which triggers this? -- nosy: +eric.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12460] SocketServer.shutdown() does not have timeout=None parameter
R. David Murray rdmur...@bitdance.com added the comment: Well, it's not applicable to 2.x, since it is a feature request. As such it could only go into 3.3. I don't have an opinion on the merits of the suggestion. -- nosy: +r.david.murray versions: +Python 3.3 -Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12460 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12459] time.sleep(-1.0) behaviour
Changes by Santoso Wijaya santoso.wij...@gmail.com: -- nosy: +santa4nt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12459 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12463] Calling SocketServer.shutdown() when server_forever() was not called will hang
Changes by Santoso Wijaya santoso.wij...@gmail.com: -- nosy: +santa4nt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12463 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12460] SocketServer.shutdown() does not have timeout=None parameter
Changes by Santoso Wijaya santoso.wij...@gmail.com: -- nosy: +santa4nt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12460 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12468] longjmp causes uninitialized stack frame
Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: +skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12456] Hangs in concurrent.futures
Ross Lagerwall rosslagerw...@gmail.com added the comment: Yes, the patch does appear to fix the issue. Thanks -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12456 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12213] BufferedRandom, BufferedRWPair: issues with interlaced read-write
Changes by Antoine Pitrou pit...@free.fr: -- priority: normal - critical type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12213 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11873] test_regexp() of test_compileall fails occassionally
Roundup Robot devnull@devnull added the comment: New changeset 6fdb1f000d36 by R David Murray in branch '3.2': #11873: another try at fixing the regex, courtesy of Victor Stinner http://hg.python.org/cpython/rev/6fdb1f000d36 New changeset 775356b583d1 by R David Murray in branch 'default': merge #11873: another try at fixing the regex, courtesy of Victor Stinner http://hg.python.org/cpython/rev/775356b583d1 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
New submission from STINNER Victor victor.stin...@haypocalc.com: test_faulthandler fails on the FreeBSD 6 buildbot since my commit 024827a9db64990865d29f9d525694f51197e770: Issue #12392: fix thread initialization on FreeBSD 6 On FreeBSD6, pthread_kill() doesn't work on the main thread before the creation of the first thread. Create therefore a dummy thread (no-op) a startup to initialize the pthread library. Add also a test for this use case, test written by Charles-François Natali. -- components: Library (Lib) messages: 139595 nosy: haypo priority: normal severity: normal status: open title: test_faulthandler failures on FreeBSD 6 versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12392] pthread_kill() doesn't work on the main thread on FreeBSD6
STINNER Victor victor.stin...@haypocalc.com added the comment: This issue introduced regressions in the faulthandler module: see issue #12469. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12392 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11873] test_regexp() of test_compileall fails occassionally
R. David Murray rdmur...@bitdance.com added the comment: I'm going to be an optimist and close this again. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11873 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
STINNER Victor victor.stin...@haypocalc.com added the comment: Debug session with gdb: --- [vstinner@buildbot-freebsd ~/cpython]$ gdb -args ./python x.py GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd...run (gdb) run Starting program: /usr/home/vstinner/cpython/python x.py warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100106] [New Thread 0x81f8000 (LWP 100089)] Program received signal SIGBUS, Bus error. [Switching to Thread 0x81f8000 (LWP 100083)] stack_overflow (min_sp=0xb97fe7f0, max_sp=0xc5ffe7f0, depth=0xbfbfe7f0) at ./Modules/faulthandler.c:870 870 buffer[0] = 1; (gdb) signal SIGBUS Continuing with signal SIGBUS. [New LWP 100083] Program received signal SIGBUS, Bus error. [Switching to LWP 100083] 0x2824df2a in signalcontext () from /lib/libc.so.6 (gdb) handle SIGBUS nostop SignalStop Print Pass to program Description SIGBUSNoYes Yes Bus error (gdb) run The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /usr/home/vstinner/cpython/python x.py warning: Unable to get location for thread creation breakpoint: generic error [New LWP 100096] [New Thread 0x81f8000 (LWP 100096)] Program received signal SIGBUS, Bus error. [New LWP 100096] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. --- If I revert the commit, faulthandler is able to dump the traceback on a stack overflow. But if I create a thread (and wait until it exits), faulthandler signal handler (for SIGBUS) is no more called. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Nir Aides n...@winpdb.org added the comment: - what would be the API of this atfork() mechanism (with an example of how it would be used in the library)? The atfork API is defined in POSIX and Gregory P. Smith proposed a Python one above that we can look into. http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html We may need an API to reset a lock. - how do you find the correct order to acquire locks in the parent process? One option is to use the import graph to determine call order of atfork handlers. If a current std library does not fit into this scheme we can possibly fix it when writing its handlers. - what do you do with locks that can be held for arbitrarily long (e.g. I/O locks)? It is likely that such a lock does not need acquiring at the parent, and re-initializing the library in the child handler will do. A critical section lock that protects in-memory data should not be held for long. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
STINNER Victor victor.stin...@haypocalc.com added the comment: By the way, the failures: Re-running test 'test_faulthandler' in verbose mode test_disable (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_traceback (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_traceback_file (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_traceback_threads (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_traceback_threads_file (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_tracebacks_later (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_tracebacks_later_cancel (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_tracebacks_later_file (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_tracebacks_later_repeat (test.test_faulthandler.FaultHandlerTests) ... ok test_dump_tracebacks_later_twice (test.test_faulthandler.FaultHandlerTests) ... ok test_enable_file (test.test_faulthandler.FaultHandlerTests) ... ok test_enable_single_thread (test.test_faulthandler.FaultHandlerTests) ... ok test_fatal_error (test.test_faulthandler.FaultHandlerTests) ... ok test_gil_released (test.test_faulthandler.FaultHandlerTests) ... ok test_is_enabled (test.test_faulthandler.FaultHandlerTests) ... ok test_read_null (test.test_faulthandler.FaultHandlerTests) ... ok test_register (test.test_faulthandler.FaultHandlerTests) ... ok test_register_file (test.test_faulthandler.FaultHandlerTests) ... FAIL test_register_threads (test.test_faulthandler.FaultHandlerTests) ... FAIL test_sigabrt (test.test_faulthandler.FaultHandlerTests) ... ok test_sigbus (test.test_faulthandler.FaultHandlerTests) ... ok test_sigfpe (test.test_faulthandler.FaultHandlerTests) ... ok test_sigill (test.test_faulthandler.FaultHandlerTests) ... ok test_sigsegv (test.test_faulthandler.FaultHandlerTests) ... ok test_stack_overflow (test.test_faulthandler.FaultHandlerTests) ... FAIL test_unregister (test.test_faulthandler.FaultHandlerTests) ... ok == FAIL: test_register (test.test_faulthandler.FaultHandlerTests) -- Traceback (most recent call last): File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 498, in test_register self.check_register() File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 489, in check_register self.assertRegex(trace, regex) AssertionError: Regex didn't match: '^Traceback \\(most recent call first\\):\n File string, line 6 in func\n File string, line 17 in module$' not found in 'Traceback (most recent call first):' == FAIL: test_register_file (test.test_faulthandler.FaultHandlerTests) -- Traceback (most recent call last): File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 505, in test_register_file self.check_register(filename=filename) File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 489, in check_register self.assertRegex(trace, regex) AssertionError: Regex didn't match: '^Traceback \\(most recent call first\\):\n File string, line 6 in func\n File string, line 17 in module$' not found in 'Traceback (most recent call first):\n File string, line 19 in module' == FAIL: test_register_threads (test.test_faulthandler.FaultHandlerTests) -- Traceback (most recent call last): File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 508, in test_register_threads self.check_register(all_threads=True) File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 489, in check_register self.assertRegex(trace, regex) AssertionError: Regex didn't match: '^Current thread XXX:\n File string, line 6 in func\n File string, line 17 in module$' not found in 'Current thread XXX:' == FAIL: test_stack_overflow (test.test_faulthandler.FaultHandlerTests) -- Traceback (most recent call last): File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 185, in test_stack_overflow other_regex='unable to raise a stack overflow') File /usr/home/db3l/buildarea/3.x.bolen-freebsd/build/Lib/test/test_faulthandler.py, line 104, in check_fatal_error self.assertRegex(output, regex) AssertionError: Regex didn't match: '^Fatal Python error: (?:Segmentation fault|Bus error)\n\nCurrent\\ thread\\ XXX:\n File string, line 3 in module$|unable to
[issue10898] posixmodule.c redefines FSTAT
Alan Hourihane al...@fairlite.co.uk added the comment: Hi Antoine, Unfortunately the #undef is too early and later #includes redefine it. We should move the #undef closer to the code that actually uses them. -- resolution: fixed - accepted status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Charles-François Natali neolo...@free.fr added the comment: The initial problem was test_3_join_in_forked_from_thread() and the hangs does still happen: Yes, the patch was there to fix test_2_join_in_forked_from_thread. [324/356] test_threading Timeout (1:00:00)! Thread 0x404248c0: File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 1498 in _communicate_with_poll File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 1423 in _communicate File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/subprocess.py, line 836 in communicate File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/script_helper.py, line 32 in _assert_python File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/script_helper.py, line 50 in assert_python_ok File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 434 in _run_and_join File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 493 in test_3_join_in_forked_from_thread File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 407 in _executeTestPart File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 462 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/case.py, line 514 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 105 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 67 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 105 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/suite.py, line 67 in __call__ File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/unittest/runner.py, line 168 in run File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/support.py, line 1259 in _run_suite File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/support.py, line 1285 in run_unittest File /srv/buildbot/buildarea/3.x.bolen-ubuntu/build/Lib/test/test_threading.py, line 774 in test_main File ./Lib/test/regrtest.py, line 1070 in runtest_inner File ./Lib/test/regrtest.py, line 861 in runtest File ./Lib/test/regrtest.py, line 669 in main File ./Lib/test/regrtest.py, line 1648 in module http://www.python.org/dev/buildbot/all/builders/x86%20Ubuntu%20Shared%203.x/builds/4081/steps/test/logs/stdio This means that the subprocess hangs, but without a backtrace of the child process (issue #12413), it's hard to analyse it further. I've had a look at the code, and couldn't find anything obviously wrong; Gregory's patches to sanitize threading's lock should have fixed this. I also tried running this test in a loop for 48 hours but couldn't reproduce it. One possible explanation (but it's just a wild guess) is that with a certain kernel/libc configuration, the lock deallocation code can deadlock (I've seen pthread_cond_destroy() block, this could maybe happen with sem_destroy()). So I suggest to try to come up with a solution to #12413, which should help analyzing this - and similar - issues. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12191] Add shutil.chown to allow to use user and group name (and not only uid/gid)
Sandro Tosi sandro.t...@gmail.com added the comment: I've applied some of the suggestions Victor made (and also refresh to be cleanly applicable on default). -- Added file: http://bugs.python.org/file22540/shutil_chown-default-v4.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
Roundup Robot devnull@devnull added the comment: New changeset 45b27448f95c by Antoine Pitrou in branch '2.7': Really fix issue #10898: posixmodule.c redefines FSTAT http://hg.python.org/cpython/rev/45b27448f95c -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
Antoine Pitrou pit...@free.fr added the comment: Ah, sorry. Can you check with the changeset I've just pushed (it's on branch 2.7)? If ok, I'll port it to 3.2/3.x and close again. -- resolution: accepted - fixed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12470] Fix cutpaste typo in test_shutil
New submission from Sandro Tosi sandro.t...@gmail.com: There is a cut paste typo in test_shutil file, this patch fixes it. -- components: Tests files: shutil_tests_cut_paste_typo.patch keywords: patch messages: 139606 nosy: sandro.tosi priority: normal severity: normal stage: patch review status: open title: Fix cutpaste typo in test_shutil versions: Python 3.2, Python 3.3 Added file: http://bugs.python.org/file22541/shutil_tests_cut_paste_typo.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12470 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12471] wrong TypeError message on '%i' formatting
New submission from Renaud Blanch rndbl...@gmail.com: The TypeError message is erroneous when attempting to format a non number object with a '%i' string (notice the '%d' in the error message): '%i' % 's' Traceback (most recent call last): File stdin, line 1, in module TypeError: %d format: a number is required, not str This is because PyUnicode_Format aliases i to d for the formatting handling, but this has the side effect of performing the substitution in the error message too. The attached patch (against 3.3, but this behaviour has been there since 2.6) suppress the side effect and corrects the error message. -- components: Interpreter Core files: PyUnicode_Format_TypeError_message.patch keywords: patch messages: 139607 nosy: rndblnch priority: normal severity: normal status: open title: wrong TypeError message on '%i' formatting type: behavior versions: Python 3.3 Added file: http://bugs.python.org/file22542/PyUnicode_Format_TypeError_message.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12471 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6721] Locks in python standard library should be sanitized on fork
Charles-François Natali neolo...@free.fr added the comment: - how do you find the correct order to acquire locks in the parent process? One option is to use the import graph to determine call order of atfork handlers. If a current std library does not fit into this scheme we can possibly fix it when writing its handlers. Sorry, I fail to see how the import graph is related to the correct lock acquisition order. Some locks are created dynamically, for example. That's why I asked for a specific API: when do you register a handler? When are they called? When are they reset? - what do you do with locks that can be held for arbitrarily long (e.g. I/O locks)? It is likely that such a lock does not need acquiring at the parent, and re-initializing the library in the child handler will do. The whole point of atfork is to avoid breaking invariants and introduce invalid state in the child process. If there is one thing we want to avoid, it's precisely reading/writting corrupted data from/to files, so eluding the I/O problem seems foolish to me. A critical section lock that protects in-memory data should not be held for long. Not necessarily. See for example I/O locks and logging module, which hold locks until I/O completion. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6721 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
New submission from kais58 kai...@sucs.org: I'm trying to build Python 2.7.2 on IRIX 6.5.30 and get the attached error in ./Modules/signalmodule.c -- components: None files: error.txt messages: 139609 nosy: kais58 priority: normal severity: normal status: open title: Build failure on IRIX type: compile error versions: Python 2.7 Added file: http://bugs.python.org/file22543/error.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12468] longjmp causes uninitialized stack frame
Charles-François Natali neolo...@free.fr added the comment: longjmp() is used in only two places: ./Modules/fpectlmodule.c:longjmp(PyFPE_jbuf, 1); ./Modules/readline.c:longjmp(jbuf, 1); Both use it to jump out of a signal handler, which can lead to undefined behaviour (see https://www.securecoding.cert.org/confluence/display/seccode/SIG32-C.+Do+not+call+longjmp()+from+inside+a+signal+handler). Now, there are two reasons for this behaviour: /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f2415de61d7] /lib/x86_64-linux-gnu/libc.so.6(+0xfe169)[0x7f2415de6169] /lib/x86_64-linux-gnu/libc.so.6(__longjmp_chk+0x33)[0x7f2415de60d3] see the __longjmp_chk and __fortify_fail? That means that Python's been compiled with gcc -D_FORTIFY_SOURCE option option, and the runtime check probably detects this and aborts the program (and the fact that it's a multi-threaded application probably. The other reason is that it's a multi-threaded application, so if you end up doing a longjmp and restore the environment saved by another thread, you're screwed. -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
Alan Hourihane al...@fairlite.co.uk added the comment: No, that patch still doesn't work. -- resolution: fixed - accepted ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
Antoine Pitrou pit...@free.fr added the comment: Hum, can you propose something? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
Charles-François Natali neolo...@free.fr added the comment:
That's because struct timeval is not defined by sys/time.h on IRIX, or it
doesn't get included in Modules/signalmodule.c.
Can you try to compile the following code with the same compiler/options?
#include sys/time.h
int main(int argc, char *argv[])
{
struct timeval tv;
return 0;
}
By the way, is IRIX an officially supported platform?
--
nosy: +haypo, neologix
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12472
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
kais58 kai...@sucs.org added the comment: ./test.c: In function 'main': ./test.c:5: warning: unused variable 'tv' is what it gives back. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10898] posixmodule.c redefines FSTAT
Alan Hourihane al...@fairlite.co.uk added the comment: I've had to split the three #undef's up to just before they're used. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10898 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
Charles-François Natali neolo...@free.fr added the comment: Ok, what happens if you change, in Modules/signalmodule.c 20 #ifdef HAVE_SYS_TIME_H 21 #include sys/time.h 22 #endif to 21 #include sys/time.h and rebuild Python? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
kais58 kai...@sucs.org added the comment: In file included from ./Modules/signalmodule.c:23: /usr/include/sys/time.h:186: error: static declaration of 'select' follows non-static declaration /usr/include/unistd.h:479: error: previous declaration of 'select' was here make: *** [Modules/signalmodule.o] Error 1 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
Charles-François Natali neolo...@free.fr added the comment: What happens if you create the thread after having registered the SIGBUS handler? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12472] Build failure on IRIX
Charles-François Natali neolo...@free.fr added the comment: You can't include both unistd.h and sys/time.h on IRIX... Nice one! A couple suggestions (in this order): 1) try putting #include sys/time.h before #include Python.h 2) try this: 20 #undef select 21 #include sys/time.h 3) fix the header yourself (remove the static storage class from select in sys/time.h) 4) complain loudly to your vendor... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12472 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
STINNER Victor victor.stin...@haypocalc.com added the comment: On FreeBSD 6, os.kill(os.getpid(), signum) calls immediatly the signal handler before the creation of the first thread (which was the case by default before my commit 024827a9db64), whereas the signal handler is called later (when exactly?) after the creation of the first thread (default after my commit). The traceback is sometimes truncated because tstate-frame is NULL. I suppose that the signal handler is called after the execution of the last instruction, after PyEval_EvalFrameEx() has set tstate-frame to f-f_back (which is NULL for the last frame). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12469 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12469] test_faulthandler failures on FreeBSD 6
STINNER Victor victor.stin...@haypocalc.com added the comment:
What happens if you create the thread after having registered
the SIGBUS handler?
I reverted my commit and created the thread after the call to
faulthandler.register(). It changes nothing, the signal handler is still called
later sometimes.
On FreeBSD 6, os.kill(os.getpid(), signum) calls immediatly
the signal handler before the creation of the first thread (...),
whereas the signal handler is called later (when exactly?) after
the creation of the first thread (default after my commit).
It looks like a kernel/libc bug. At least, it doesn't conform to POSIX.1-2001.
Extract of the Linux manual page of the kill function (syscall):
POSIX.1-2001 requires that if a process sends a signal to itself, and the
sending thread does not have the signal blocked, and no other thread has it
unblocked or is waiting for it in sigwait(3), at least one unblocked signal
must be delivered to the sending thread before the kill() returns.
I see two options:
- revert my commit and fix #12392 (test_signal) differently
- skip test_register, test_register_file, test_register_threads and
test_stack_overflow can on freebsd6
I prefer to revert my commit because it introduced an unexpected behaviour on
signal handling. It calls the signal handler later when the process sends a
signal to itself, even if the application don't use threads.
The new fix for #12392 is to ensure that at least one thread was created. We
can for example use the following code at the beginning of test_signal:
if sys.platform in ('freebsd5', 'freebsd6'):
# On FreeBSD6, pthread_kill() doesn't work on the main thread
# before the creation of the first thread
import threading
t = threading.Thread(target=lambda: None)
t.start()
t.join()
Then test_signal.test_pthread_kill_main_thread() should be skipped or patched
for freebsd6.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12469
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12457] type() returns incorrect type for nested classes
Peter Williams pwil3...@bigpond.net.au added the comment: The class I was pickling was a top level class but a field inside that class had an instance of a nested class set as its value. The error message produced indicated that the reason for failure was the inability of pickle to find the class definition and (I think) that was caused by the problem with type()'s returned value. Perhaps fixing the problem with type() would allow the restriction on pickling nested classes to be removed? Was that restriction a deliberate design decision (illogical) or the result of not being able to get it to work? Re whether the behaviour of type() is a problem: I believe it is as, in addition to the inconsistencies between type() and isinstance() that I described in my original report, there is the confusion that arises if two separate classes have nested classes with the same name (see mini program confusion.py as an example). This seems to compromise the whole purpose of namespaces and is inconsistent with the way modules are treated in determining the name reported by type(). -- type: behavior - crash Added file: http://bugs.python.org/file22544/confusion.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12457 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7846] Fnmatch cache is never cleared during usage
Tom Rini tom.r...@gmail.com added the comment: So yes, we have some code that was doing, roughly: if any(fnmatchcase(key, pat) for pat in pattern): refs.add(key) on 200-300 elements, a lot. That said, many of them were not globs so we've worked around this to only use fnmatchcase on globs and just key in set otherwise. Things are now usable on python 2.6.6+ (so Ubuntu 10.10) and noise otherwise. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7846 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
