[issue4856] Remove checks for win NT
Martin v. Löwis mar...@v.loewis.de added the comment: Sure, go ahead. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4856 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6353] L integer suffix in Python 3.1 tutorial
New submission from Pierre Bourdon r...@delroth.is-a-geek.org: Chapter 14 (Floating Point Arithmetic: Issues and Limitations) of the Python 3.x tutorial contains integers with long suffix (424242L) when talking about as_integer_ratio. Patch is attached. -- assignee: georg.brandl components: Documentation files: fp-tutorial.diff keywords: patch messages: 89767 nosy: delroth, georg.brandl severity: normal status: open title: L integer suffix in Python 3.1 tutorial versions: Python 3.0, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file14374/fp-tutorial.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6353 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
New submission from Pierre Bourdon r...@delroth.is-a-geek.org: In part 3.1.1 of the Python 3.1 tutorial, the following code sample is obsolete : 8/5 # Fractions aren't lost when dividing integers 1.6001 In a fresh Python 3.1, 8/5 is now displayed as 1.6. The note below the code sample should be updated too. -- assignee: georg.brandl components: Documentation messages: 89768 nosy: delroth, georg.brandl severity: normal status: open title: Old floating point representation in 3.1 tutorial versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6355] bogus NULL check in PyCapsule
New submission from Benjamin Kramer benny@gmail.com:
Objects/capsule.c contains the following code:
if (!name1 || !name2) {
/* they're only the same if they're both NULL. */
return name2 == name2;
}
The result of this comparison will always be true. The comment says it
should be 'name1 == name2'.
--
components: Interpreter Core
files: capsulecompare.patch
keywords: patch
messages: 89769
nosy: bkramer
severity: normal
status: open
title: bogus NULL check in PyCapsule
versions: Python 3.1
Added file: http://bugs.python.org/file14375/capsulecompare.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6355
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5390] Item 'Python x.x.x' in Add/Remove Programs list still lacks an icon
Martin v. Löwis mar...@v.loewis.de added the comment: Thanks for the analysis and the patch. Fixed in r73599, r73600, r73601, r73602. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5390 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6344] mmap.read() crashes when passed a negative argument
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: + if (n 0) I suggest a comment like: /* The difference can overflow, only if self-size is greater than * PY_SSIZE_T_MAX. But then the operation cannot possibly succeed, * because the mapped area and the returned string each need more * than half of the addressable memory. So we clip the size, and let * the code below raise MemoryError. */ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6344 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6356] Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux)
New submission from str1442 lancer...@freenet.de: After playing around with the setrecursionlimit() Function in the sys module, i noticed it crashes if you set the limit to a value that is too high. I explored this further until i noticed the value from which the crashing begins is exactly 18063. I know that the highest setable value is platformdependent, but crashing seems inappropriate if a value is given that is too high. I'm using Debian GNU/Linux Testing, last upgrade one month ago. uname -svomr: Linux 2.6.27.7 #4 SMP Fri Nov 28 01:44:17 CET 2008 i686 GNU/Linux (Kernel is a pure kernel.org Kernel, self compiled) Python Version in question is 2.5.4. Searching through the tracker for setrecursionlimit brought no corresponding issues. This is a the test script I used: import sys sys.setrecursionlimit(18063) def f(): g() def g(): f() f() -- components: Interpreter Core, Library (Lib) messages: 89772 nosy: str1442 severity: normal status: open title: Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux) type: crash versions: Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6356 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6356] Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux)
Martin v. Löwis mar...@v.loewis.de added the comment: I know that the highest setable value is platformdependent, but crashing seems inappropriate if a value is given that is too high. No, it's not inappropriate. It's the only possible reaction. Closing as won't fix. -- nosy: +loewis title: Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux) - Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6356 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6356] Segfault of sys.setrecursionlimit if limit exceeds the value 18063 (GNU/Linux)
Changes by Martin v. Löwis mar...@v.loewis.de: -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6356 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4856] Remove checks for win NT
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment: Thanks, committed in r73603(trunk) and r73604(py3k). -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4856 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6267] Cumulative patch to http and xmlrpc
Martin v. Löwis mar...@v.loewis.de added the comment: Patch set 4 looks fine to me, please apply it to 2.7 and 3.2. -- assignee: - krisvale nosy: +loewis resolution: - accepted ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6267 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6237] Build errors when using LDFLAGS=-Wl,--no-undefined
Funda Wang fundaw...@gmail.com added the comment: How is this issue going? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6355] bogus NULL check in PyCapsule
Benjamin Peterson benja...@python.org added the comment: Thanks for the patch! Fixed in r73618. -- nosy: +benjamin.peterson resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6355 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
Changes by Benjamin Peterson benja...@python.org: -- nosy: +eric.smith, marketdickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2919] Merge profile/cProfile in 3.0
Alexandre Vassalotti alexan...@peadrop.com added the comment: Yesterday, I ported the _lsprof module to Python as an experiment. I still have a few issues to iron out, but the core of the functionality is there. I am not sure yet how this experiment will fit in the profile/cProfile merge. I wrote the port mainly to get a better idea of what is needed for the merge and how the profiler works. -- Added file: http://bugs.python.org/file14376/lsprof.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2919 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2919] Merge profile/cProfile in 3.0
Changes by Alexandre Vassalotti alexan...@peadrop.com: Added file: http://bugs.python.org/file14377/pyprofile.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2919 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails
Benjamin Peterson benja...@python.org added the comment: Senthil, are you still working on the 3.x version of the patch? -- nosy: +benjamin.peterson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1424152 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5254] Formatting error in findertools header
Changes by Ezio Melotti ezio.melo...@gmail.com: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5254 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5388] Green-box doc glitch: winhelp version only
Ezio Melotti ezio.melo...@gmail.com added the comment: It's probably better to split long lines (at 80 chars?) than adding an empty line in every box. Scrolling horizontally is annoying enough even without the problem you mentioned. I don't know if it's possible to split grammar lines like id_start/id_continue[1], but in this specific case is probably better to keep the definitions short and explain it further in the following paragraph. I don't have any idea about how Windows Help works, but if it uses something like CSS, some extra padding at bottom could solve the problem without having to add an empty line. [1]: http://docs.python.org/3.1/reference/lexical_analysis.html#identifiers -- nosy: +ezio.melotti priority: - low ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6349] email.Maildir cannot roundtrip messages.
R. David Murray rdmur...@bitdance.com added the comment: Did you specify 'factory=None', as instructed by the documentation? (The default is fixed in py3, by the way). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6357] tempfile.NamedTemporaryFile does not accept the delete= parameter on Windows
New submission from Daniel Stutzbach dan...@stutzbachenterprises.com:
Likely affects Python 2.7 and Python3.x as well, but I have not checked.
Under Windows:
tempfile.NamedTemporaryFile('w', delete = False)
TypeError: NamedTemporaryFile() got an unexpected keyword argument 'delete'
Under Unix:
tempfile.NamedTemporaryFile('w', delete=True)
open file 'fdopen', mode 'w' at 0x7ff199d0
--
messages: 89782
nosy: stutzbach
severity: normal
status: open
title: tempfile.NamedTemporaryFile does not accept the delete= parameter on
Windows
type: behavior
versions: Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6357
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1474680] pickling files works with protocol=2.
Alexandre Vassalotti alexan...@peadrop.com added the comment: That seems easy to fix by adding a dummy __reduce__ method to file. My only worry is this could break file subclasses which may have ad-hoc mechanisms implemented for pickling files. -- keywords: +patch nosy: +alexandre.vassalotti stage: - needs patch type: - behavior versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file14378/disable_file_pickling-py2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1474680 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5388] Green-box doc glitch: winhelp version only
Terry J. Reedy tjre...@udel.edu added the comment: The lines in the green box do not have to be long in an absolute sense, just longer than the current window width allows. As soon as the the window is narrow enough to require a horizontal scroll bar, a vertical scroll bar is added too because the horizonal scroll bar is added into the box on top of where the bottom margin and part of the last line was. I just discovered that if the vertical scroll bar is exactly centered, everything is visible because the horizontal bar is a bit under twice the width of the top and bottom margins. If only it started there... -- versions: +Python 3.2 -Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
Mark Dickinson dicki...@gmail.com added the comment: Thanks for the report! I've stolen this from Georg (sorry, Georg) and fixed this and a few other similar repr-related problems in r73636 (py3k) and r73637 (release31-maint). -- assignee: georg.brandl - marketdickinson resolution: - fixed status: open - closed versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6267] Cumulative patcc:h to http and xmlrpc
Kristján Valur Jónsson krist...@ccpgames.com added the comment: Commited to 2.7 in revision 73638 -- title: Cumulative patch to http and xmlrpc - Cumulative patcc:h to http and xmlrpc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6267 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6117] Fix O(n**2) performance problem in socket._fileobject
Kristján Valur Jónsson krist...@ccpgames.com added the comment: There is no need to port this to 3.2, it uses a completely different IO system for socket fileobjects. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6117 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6248] TCP Sockets not closed by TCPServer and StreamRequestHandler
Changes by Kristján Valur Jónsson krist...@ccpgames.com: -- status: open - closed superseder: - Cumulative patcc:h to http and xmlrpc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5388] Green-box doc glitch: winhelp version only
Ezio Melotti ezio.melo...@gmail.com added the comment: That's why I think that the Windows Help problem still need to be fixed, but limiting the length of the lines is a good idea regardless of this, since having long lines and horizontal scroll bars is annoying on the browser too. Is the Windows Help python31.chm? I installed Python 3.1 on Windows XP and tried to open that section. Here the width of the page depends on the longest line, so the whole page is large enough to contain both id_start and id_continue (however, even if this long lines go over the right limit of the page, all the other lines fit in the visible part of the page). There are no scrollbars inside the green box, just global scrollbars for the page -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5388 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
Mark Dickinson dicki...@gmail.com added the comment: See also r73640 and r73641, which take into account Pierre's point that the note below the code sample should be updated. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
Ezio Melotti ezio.melo...@gmail.com added the comment: What about http://docs.python.org/3.1/tutorial/floatingpoint.html ? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6354] Old floating point representation in 3.1 tutorial
Mark Dickinson dicki...@gmail.com added the comment: Ezio: I think Raymond updated that recently, so it should be okay. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6354 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6358] os.popen exit code inconsistent
New submission from James Abbatiello abb...@gmail.com: Start a process with os.popen() and then try to get its exit code by closing the resulting file handle. The value returned is inconsistent between 2.x and 3.x. Example: Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import os f = os.popen(exit 42, r) f.close() 42 Python 3.1 (r31:73574, Jun 26 2009, 20:21:35) [MSC v.1500 32 bit (Intel)] on win32 Type help, copyright, credits or license for more information. import os f = os.popen(exit 42, r) f.close() 10752 divmod(10752, 256) (42, 0) The docs for 2.6.2 say that the return value is the exit status of the process as returned by wait() (http://docs.python.org/library/os.html#os.popen). That's what 3.1 is doing(*) but not what 2.6 has actually been doing. In 2.6 the exit code (not exit status) is returned; if the process didn't exit cleanly then an exception is thrown. The docs for 3.1 say that os.popen() is documented in the section File Object Creation but it is not. http://docs.python.org/3.1/library/os.html#process-management http://docs.python.org/3.1/library/os.html#file-object-creation It doesn't seem to be documented at all in 3.1 although it is mentioned many times on that page. Since os.popen() is mostly for backward compatibility, should the 3.x behavior be changed to match the actual 2.6 behavior? (*) It looks like 3.1 doesn't return the right value if the subprocess is killed by a signal but I can't test this on win32. -- assignee: georg.brandl components: Documentation, Library (Lib) messages: 89792 nosy: abbeyj, georg.brandl severity: normal status: open title: os.popen exit code inconsistent versions: Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6358 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6286] distutils upload command doesn't work with http proxy
Tarek Ziadé ziade.ta...@gmail.com added the comment: merged in 3.2 in r73645 -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6286 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6164] [AIX] Patch to correct the AIX C/C++ linker argument used for 'runtime_library_dirs'
Tarek Ziadé ziade.ta...@gmail.com added the comment: merged in 3.2 in r73647 -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6164 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6192] add disable_nagle_algorithm to SocketServer.TCPServer
Kristján Valur Jónsson krist...@ccpgames.com added the comment: Merged into py3k in revision 73648 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6192] add disable_nagle_algorithm to SocketServer.TCPServer
Changes by Kristján Valur Jónsson krist...@ccpgames.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6192 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6349] email.Maildir cannot roundtrip messages.
David Bremner brem...@unb.ca added the comment: that seems to fix my test script. Thanks. I guess the bug can be closed? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6349] email.Maildir cannot roundtrip messages.
R. David Murray rdmur...@bitdance.com added the comment: Yep :) -- resolution: - invalid stage: test needed - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6359] pyexpat.c calls trace function incorrectly for exceptions
New submission from Ned Batchelder ned...@users.sourceforge.net: Pyexpat.c calls the tracing function explicitly (not sure why). When it intercepts an exception, it calls the function with PyTrace_EXCEPTION, but then leaves the scope without calling PyTrace_RETURN. This is incorrect. There should always be a PyTrace_RETURN for every PyTrace_CALL. I've attached domshow.py to demonstrate the problem. Running it produces many lines of output, including: line expatbuilder.py 222 line expatbuilder.py 223 call pyexpat.c 905 call expatbuilder.py 892 line expatbuilder.py 894 line expatbuilder.py 900 exception expatbuilder.py 900 return expatbuilder.py 900 exception pyexpat.c 905 exception expatbuilder.py 223 line expatbuilder.py 225 line expatbuilder.py 226 The exception at line 905 in pyexpat.c should be followed with a return from line 905 in pyexpat.c, but is not. After that exception, the nesting is off by one because the Calls and Returns don't match. -- components: XML files: domshow.py messages: 89798 nosy: nedbat severity: normal status: open title: pyexpat.c calls trace function incorrectly for exceptions type: behavior versions: Python 2.5, Python 2.6 Added file: http://bugs.python.org/file14379/domshow.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6359 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6267] Cumulative patcc:h to http and xmlrpc
Kristján Valur Jónsson krist...@ccpgames.com added the comment: I'm working on the 3.2 port, it needs some manual work. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6267 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1502517] crash in expat when compiling with --enable-profiling
Ezio Melotti ezio.melo...@gmail.com added the comment: I got this warning compiling Python3.1: /home/wolf/Python-3.1/Modules/expat/xmlparse.c: In function ‘doProlog’: /home/wolf/Python-3.1/Modules/expat/xmlparse.c:3771: warning: passing argument 1 of ‘normalizePublicId’ discards qualifiers from pointer target type I don't know if it's in any way related to this problem, but I found this issue while searching for 'doProlog' and 'xmlparse'. -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1502517 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6360] Simplify string decoding in xmlrpc.client.
New submission from Alexandre Vassalotti alexan...@peadrop.com: The following patch tries to improve how xmlrpc.client handles strings. In particular, it simplifies the decoding of strings by keeping them as unicode str. -- files: simplify_xmlrpc_string_decoding.diff keywords: patch messages: 89801 nosy: alexandre.vassalotti priority: normal severity: normal stage: patch review status: open title: Simplify string decoding in xmlrpc.client. type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file14380/simplify_xmlrpc_string_decoding.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6360 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2480] eliminate recursion in pickling
Alexandre Vassalotti alexan...@peadrop.com added the comment: I am closing this issue in favour of #3119, since Aaron's patch is cleaner and slightly faster. Thank you Daniel for the idea! -- dependencies: -pickle.py is limited by python's call stack resolution: - duplicate status: open - closed superseder: - pickle.py is limited by python's call stack ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2480 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6361] I/O object wrappers shouldn't close their underlying file when deleted.
New submission from Alexandre Vassalotti alexan...@peadrop.com: Here's an example of the behaviour: import io def test(buf): textio = io.TextIOWrapper(buf) buf = io.BytesIO() test(buf) print(buf.closed) # This prints True currently The problem here is TextIOWrapper closes its buffer when deleted. BufferedRWPair behalves similarly. The solution is simply to override the __del__ method of TextIOWrapper inherited from IOBase. -- messages: 89803 nosy: alexandre.vassalotti priority: normal severity: normal stage: needs patch status: open title: I/O object wrappers shouldn't close their underlying file when deleted. type: behavior versions: Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6361 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6362] multiprocessing: handling of errno after signals in sem_acquire()
New submission from Ryan Leslie ryle...@gmail.com:
While developing an application, an inconsistency was noted where,
depending on the particular signal handler in use,
multiprocessing.Queue.put() may (or may not) raise OSError() after
sys.exit() was called by the handler. The following example, which was
tested with Python 2.6.1 on Linux, demonstrates this.
#!/usr/bin/env python
import multiprocessing
import signal
import sys
def handleKill(signum, frame):
#sys.stdout.write(Exit requested by signal.\n)
print Exit requested by signal.
sys.exit(1)
signal.signal(signal.SIGTERM, handleKill)
queue = multiprocessing.Queue(maxsize=1)
queue.put(None)
queue.put(None)
When the script is run, the process will block (as expected) on the
second queue.put(). If (from another terminal) I send the process
SIGTERM, I consistently see:
$ ./q.py
Exit requested by signal.
$
Now, if I modify the above program by commenting out the 'print', and
uncommenting the 'sys.stdout' (a very subtle change), I would expect
the result to be the same when killing the process. Instead, I
consistently see:
$ ./q.py
Exit requested by signal.
Traceback (most recent call last):
File ./q.py, line 15, in module
queue.put(None)
File python2.6/multiprocessing/queues.py, line 75, in put
if not self._sem.acquire(block, timeout):
OSError: [Errno 0] Error
$
After debugging this further, the issue appears to be in
semlock_acquire() or semaphore.c in Modules/_multiprocessing:
http://svn.python.org/view/python/trunk/Modules/_multiprocessing/semaphore.c?revision=71009view=markup
The relevant code from (the Unix version of) semlock_acquire() is:
do {
Py_BEGIN_ALLOW_THREADS
if (blocking timeout_obj == Py_None)
res = sem_wait(self-handle);
else if (!blocking)
res = sem_trywait(self-handle);
else
res = sem_timedwait(self-handle, deadline);
Py_END_ALLOW_THREADS
if (res == MP_EXCEPTION_HAS_BEEN_SET)
break;
} while (res 0 errno == EINTR !PyErr_CheckSignals());
if (res 0) {
if (errno == EAGAIN || errno == ETIMEDOUT)
Py_RETURN_FALSE;
else if (errno == EINTR)
return NULL;
else
return PyErr_SetFromErrno(PyExc_OSError);
}
In both versions of the program (print vs. sys.stdout), sem_wait() is
being interrupted and is returning -1 with errno set to EINTR. This is
what I expected. Also, in both cases it seems that the loop is
(correctly) terminating with PyErr_CheckSignals() returning non-zero.
This makes sense too; the call is executing our signal handler, and then
returning -1 since our particular handler raises SystemExit.
However, I suspect that depending on the exact code executed
for the signal handler, errno may or may not wind up being reset in
some nested call of PyErr_CheckSignals(). I believe that the
error checking code below the do-while (where sem_wait() is called),
needed errno to have the value set by sem_wait(), and the author
wasn't expecting anything else to have changed it. In the print
version, errno apparently winds up unchanged with EINTR, resulting in
the `return NULL' statement. In the sys.stdout version (and probably
many others), errno winds up being reset to 0, and the error handling
results in the `return PyErr_SetFromErrno(PyExc_OSError)' statement.
To patch this up, we can probably just save errno as, say, `wait_errno'
at the end of the loop body, and then use it within the error handling
block that follows. However, the rest of the code should probably be
checked for this type of issue.
--
components: Library (Lib)
messages: 89804
nosy: ryles
severity: normal
status: open
title: multiprocessing: handling of errno after signals in sem_acquire()
type: behavior
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6362
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6362] multiprocessing: handling of errno after signals in sem_acquire()
Changes by Ryan Leslie ryle...@gmail.com: -- nosy: +jnoller ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6362 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6362] multiprocessing: handling of errno after signals in sem_acquire()
Jesse Noller jnol...@gmail.com added the comment: Thank you Ryan -- assignee: - jnoller priority: - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6362 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails
Senthil orsent...@gmail.com added the comment: Senthil, are you still working on the 3.x version of the patch? Sorry for the delay. I got to work on it. Shall start and shall try to get it in soon. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1424152 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6363] __future__ statements break doctest
New submission from Poor Yorick pooryor...@users.sourceforge.net:
(this error also occurs with print_function)
Python 3.1 (r31:73574, Jun 26 2009, 20:21:35) [MSC v.1500 32 bit
(Intel)] on win
32
Type help, copyright, credits or license for more information.
from __future__ import unicode_literals
import doctest
def func1():
...'''
... func1()
...hello
...'''
...print('hello')
...
doctest.testmod()
**
File __main__, line 3, in __main__.func1
Failed example:
func1()
Exception raised:
Traceback (most recent call last):
File c:\Python31\lib\doctest.py, line 1242, in __run
compileflags, 1), test.globs)
ValueError: compile(): unrecognised flags
**
1 items had failures:
1 of 1 in __main__.func1
***Test Failed*** 1 failures.
TestResults(failed=1, attempted=1)
--
components: Library (Lib)
messages: 89807
nosy: pooryorick
severity: normal
status: open
title: __future__ statements break doctest
versions: Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6363
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6364] freeze tool broken in Python 3.x
New submission from Hagen Fürstenau hfuerste...@gmx.net: The freeze tool seems to be severely broken in Python 3.x. Applying it to a hello world script produces: Warning: unknown modules remain: _bisect _collections _ctypes _hashlib _heapq _multiprocessing _pickle _random _socket _ssl _struct _tkinter array atexit binascii datetime fcntl itertools math mmap operator pyexpat readline select termios time and a subsequent make results in config.o:(.data+0x8): undefined reference to `init_codecs' config.o:(.data+0x18): undefined reference to `init_functools' config.o:(.data+0x28): undefined reference to `init_io' config.o:(.data+0x38): undefined reference to `init_locale' config.o:(.data+0x48): undefined reference to `init_sre' config.o:(.data+0x58): undefined reference to `init_thread' config.o:(.data+0x68): undefined reference to `init_weakref' config.o:(.data+0x78): undefined reference to `initerrno' config.o:(.data+0x88): undefined reference to `initgc' config.o:(.data+0x98): undefined reference to `initimp' config.o:(.data+0xa8): undefined reference to `initposix' config.o:(.data+0xb8): undefined reference to `initpwd' config.o:(.data+0xc8): undefined reference to `initsignal' config.o:(.data+0xd8): undefined reference to `initzipimport' -- components: Demos and Tools messages: 89808 nosy: hagen severity: normal status: open title: freeze tool broken in Python 3.x type: behavior versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6364 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6360] Simplify string decoding in xmlrpc.client.
Martin v. Löwis mar...@v.loewis.de added the comment: Did you try these changes? Can you provide a test case? -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6360 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6364] freeze tool broken in Python 3.x
Martin v. Löwis mar...@v.loewis.de added the comment: Would you like to provide a patch? -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6364 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6364] freeze tool broken in Python 3.x
Hagen Fürstenau hfuerste...@gmx.net added the comment: Would you like to provide a patch? I wouldn't mind if someone beat me to it. But if that doesn't happen, I'll look into it when I have some time to spare. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6364 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4660] multiprocessing.JoinableQueue task_done() issue
Brian br...@merrells.org added the comment: Filipe, Thanks for the confirmation. While I think the second option (ie properly protecting JoinableQueue.put()) is best, the first option (simply removing the 'task_done() called too many times' check) should be safe (presuming your get() and put() calls actually match). Jesse, any luck sorting out the best fix for this? I really think that JoinableQueue (in my opinion the most useful form of multiprocessing queues) can't be guaranteed to work on any system right now. -brian -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4660 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
