[issue7143] get_payload(decode=True) eats last newline in base64 encoded payload
Joaquin Cuenca Abela e98cu...@gmail.com added the comment: Thanks David and Barry! As much as it flatters my ego to be in the first place is MISC/ACK, I have to confess that my family name is Cuenca Abela, Cuenca is not a middle name. Cheers, -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7143 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Ned Deily n...@acm.org added the comment: It looks like the patches were not applied correctly. -- status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8047] Serialiser in ElementTree returns unicode strings in Py3k
Stefan Behnel sco...@users.sourceforge.net added the comment: Antoine, in the same comment, you say that it was not backported to Py2 in order to prevent breaking existing code, and then you ask if it's difficult to support in lxml. ;-) Supporting the same behaviour in lxml would either mean that it breaks existing code in Py2 (when making the API consistent), or that you can safely (and correctly) write the return value to a file in Py2, but that you can't do the same in Py3 (when adopting the change only in Py3). Previously, in ElementTree, serialising without an explicit encoding was a way to get a byte encoded serialisation without an XML declaration header, so I expect there to be code that depends on this. Since ElementTree 1.3 uses the same keyword argument as lxml for this feature, I assume that Florent's patches provide at least an alternative here, even if it requires users to adapt their code. I just wish this backwards incompatible feature had been advertised at the time, or at least *documented* in any way. Even the latest 3.2-dev docs still state that the default encoding of the serialiser is US-ASCII, not a word about *ever* returning a unicode string, especially not by default, and totally not the required big fat warning that writing to a file will fail with mysterious errors if no encoding is specified. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8047 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8047] Serialiser in ElementTree returns unicode strings in Py3k
Florent Xicluna florent.xicl...@gmail.com added the comment: With ET 1.3, you should have an explicit keyword argument xml_declaration: # if xml_declaration or (xml_declaration is None and encoding not in (utf-8, us-ascii)): if method == xml: write(?xml version='1.0' encoding='%s'?\n % encoding) # In ET 1.2.6, the same snippet looks like: # if encoding != utf-8 and encoding != us-ascii: file.write(?xml version='1.0' encoding='%s'?\n % encoding) # -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8047 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1052827] filelist.findall should use os.lstat
Pádraig Brady p...@draigbrady.com added the comment: Packaging dangling symlinks is often required, so this is a problem. For e.g. in my package I want to install this symlink: /etc/apache2/sites-enabled/000-default - ../sites-available/myapp.conf -- nosy: +pixelbeat versions: +Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1052827 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: PyImport_Import() clears errors if a module has no globals, whereas PyEval_GetGlobals() doesn't set any exception on failure. = import_no_global.patch removes this unnecessary PyErr_Clear(). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: Py_InitializeEx() calls PyErr_Clear() if PyCodec_Encoder() fails without checking for the exception type. Attached initiliaze_pycodec_error.patch checks for error type: if the error is not an LookupError, display the error and exit (as done for initsite() iny my initsite.patch). -- Added file: http://bugs.python.org/file16491/initiliaze_pycodec_error.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: tok_stdin_decode() clears error without check for the type. tokenizer_error.patch stops the tokenizer with an E_ERROR if the exception is not an UnicodeDecodeError. Fix also err_input() to support E_ERROR: leave the global exception (PyErr_*) unchanged. -- Added file: http://bugs.python.org/file16492/tokenizer_error.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16489/main_pending_calls.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: Remove main_pending_calls.patch hack: replaced by tokenizer_error.patch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Added file: http://bugs.python.org/file16493/import_no_global.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: Remove main_pending_calls.patch hack: replaced by tokenizer_error.patch. With extra tests, I realized that this patchs is still useful to process a SIGINT emitted between Py_Initialize() and PyRun_AnyFileExFlags(). Without the patch, if a SIGINT is emitted just after Py_Initialize(): it's only proceed when the user press enter in the interactive interpreter (when the tokenizer decodes the input string to the terminal charset). -- Added file: http://bugs.python.org/file16494/main_pending_calls.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8050] smtplib SMTP.sendmail (TypeError: expected string or buffer)
Allison Vollmann allisonv...@gmail.com added the comment: i believe which the parameter msg must be referenced as a string type when called sendmail nor as an MIME[Message, Multipart, Text, Base, Audio] and this is obvious way to do it. but i'm not Dutch :-) -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8050 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1530559] struct.pack raises TypeError where it used to convert
Meador Inge mead...@gmail.com added the comment: (2) For 2.x, I'm a bit uncomfortable with introducing the extra Python layer on top of the C layer. Partly I'm worried about accidentally breaking something (it's not 100% clear to me whether there might be hidden side-effects to such a change), I understand. I am worried about that as well. The main area that concerns me is the interface for the 'Struct' class. I did my best to match the methods and functions from the C implementation. I need to look into this in more detail, though. One quirk I currently know about is that the following methods: '__delattr__', '__getattribute__', '__setattr__', '__new__' show up in 'help' for the C implementation, but not the Python one. Although, the implementations do exist in both places. but I also notice that this seems to have a significant impact on performance. In fact, I seem to recall that the previously existing Python component of the struct module was absorbed into Modules/_struct.c precisely for performance reasons. A quick, unscientific benchmark: the time taken to run test_struct with this patch (excluding the changes to test_struct itself) on my machine (OS X 10.6, 64-bit non-framework non-debug build of Python) is around 1.52--1.53 seconds; without the patch it's around 1.02--1.03 seconds. Agreed that this is not a really scientific benchmark. I did experiment with this idea a little further though on my machine (OS X 10.5 32-bit): == | Configuration| Seconds | == | Original | 1.26| -- | __index__ patch v1 | 1.88| -- | Hoisted imports out of functions | 1.53| -- | Hoisted imports and no __index__ | 1.34| -- So with this simple experiment pulling the 'imports' out of the function wrappers made quite a difference. And, of course, removing the '__index__' transform brought the times down even more. So, the wrapper overhead does not look to be terrible for this simple test. However, as you alluded to, we should find a better benchmark. Any ideas on a good one? (4) For 2.x, perhaps we don't need the extra __index__ functionality anyway, now that the previous use of __int__ has been restored. That would give us a bit more time to think about this for 3.x. Agreed. Thanks for taking the time to look at the patch anyway! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1530559 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Florent Xicluna florent.xicl...@gmail.com added the comment: Previous buildbot failures were in test_multiprocessing: http://bugs.python.org/issue1731717#msg100430 Now it should be fixed: - r78777, r78787, r78790 on 2.x - r78798 on 3.x -- resolution: - fixed stage: test needed - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7805] test_multiprocessing failure
Florent Xicluna florent.xicl...@gmail.com added the comment: This last bug is fixed, too. http://bugs.python.org/issue1731717#msg100643 -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7805 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2777] subprocess unit tests for kill, term and send_signal flaky
Florent Xicluna florent.xicl...@gmail.com added the comment: All this flakiness is fixed: - r78736, r78759, r78761, r78767, r78788, r78789 on 2.x - r78797 on 3.x Note: because of #3137, the send_signal(SIGINT) is retried 2 times on some platforms. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2777 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Yonas yona...@gmail.com added the comment: Florent, Have you tested any of the sample test programs mentioned in this bug report? For example, the one by Joel Martin (kanaka). I'd suggest to test those first before marking this issue as fixed. - Yonas -- status: pending - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Florent Xicluna florent.xicl...@gmail.com added the comment: import subprocess, signal signal.signal(signal.SIGCLD, signal.SIG_IGN) 0 subprocess.Popen(['echo','foo']).wait() foo Traceback (most recent call last): File stdin, line 1, in module File ./Lib/subprocess.py, line 1229, in wait pid, sts = _eintr_retry_call(os.waitpid, self.pid, 0) File ./Lib/subprocess.py, line 482, in _eintr_retry_call return func(*args) OSError: [Errno 10] No child processes You're right, I fixed something giving the same ECHILD error in multiprocessing. But it was not related. -- resolution: fixed - stage: committed/rejected - needs patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Changes by Florent Xicluna florent.xicl...@gmail.com: -- keywords: -buildbot ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Yonas yona...@gmail.com added the comment: http://groups.google.com/group/comp.lang.python/browse_thread/thread/9a853d0308c8e55a I'm also glad to see a test case that causes exactly the same error with or without the presence of a ‘daemon.DaemonContext’. Further research shows that handling of ‘SIGCLD’ (or ‘SIGCLD’) is fairly OS-specific, with “ignore it” or “handle it specifically” being correct on different systems. I think Python's default handling of this signal is already good (modulo bug #1731717 to be addressed in ‘subprocess’). So I will apply a change similar to Joel Martin's suggestion, to default to avoid touching the ‘SIGCLD’ signal at all, and with extra notes in the documentation that anyone using child processes needs to be wary of signal handling. This causes the above test case to succeed; the output file contains:: = Child process via os.system. Child process via 'subprocess.Popen'. Parent daemon process. Parent daemon process done. = -- By Ben Finney -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8047] Serialiser in ElementTree returns unicode strings in Py3k
Antoine Pitrou pit...@free.fr added the comment: Le Mon, 08 Mar 2010 09:01:19 +, Stefan Behnel rep...@bugs.python.org a écrit : Antoine, in the same comment, you say that it was not backported to Py2 in order to prevent breaking existing code, and then you ask if it's difficult to support in lxml. ;-) I meant breaking existing *user* code. Besides, the fact that compatibility is broken doesn't mean third-party code difficult to fix; hence my question. Supporting the same behaviour in lxml would either mean that it breaks existing code in Py2 (when making the API consistent), or that you can safely (and correctly) write the return value to a file in Py2, but that you can't do the same in Py3 (when adopting the change only in Py3). Sorry, I don't understand this. Are you saying it's impossible for you to define two different behaviours based on the current Python version? What's bad with if sys.version_info() = (3, 0, 0): # blah Previously, in ElementTree, serialising without an explicit encoding was a way to get a byte encoded serialisation without an XML declaration header, so I expect there to be code that depends on this. This doesn't seem to be documented. The doc simply says encoding is the output encoding (default is US-ASCII). In other words, undocumented (and untested) behaviour has been broken when porting to 3.0, which is the version which deliberately broke compatibility for documented things. I guess we can live with it ;) Even the latest 3.2-dev docs still state that the default encoding of the serialiser is US-ASCII, not a word about *ever* returning a unicode string, especially not by default, and totally not the required big fat warning that writing to a file will fail with mysterious errors if no encoding is specified. Ok, perhaps some documentation changes are in order :-) (I wonder why the default was US-ASCII, though. Sounds a bit braindead) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8047 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Yonas yona...@gmail.com added the comment: Ben Finney's comment suggests to me that this bug is being ignored. Am I wrong? with extra notes in the documentation that anyone using child processes needs to be wary of signal handling. Why should they be wary? We should just fix this bug. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8047] Serialiser in ElementTree returns unicode strings in Py3k
Changes by Antoine Pitrou pit...@free.fr: -- assignee: - georg.brandl components: +Documentation nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8047 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Yonas yona...@gmail.com added the comment: By the way, in three months from today, this bug will be 3 years old. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7624] isinstance(... , collections.Callable) fails with oldstyle class instances
Florent Xicluna florent.xicl...@gmail.com added the comment: Fixed in r78800. Additional tests backported to 3.x. -- resolution: accepted - fixed stage: commit review - committed/rejected status: open - closed title: isinstance(... ,collections.Callable) fails with oldstyle class i nstances - isinstance(... ,collections.Callable) fails with oldstyle class instances ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7624 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8050] smtplib SMTP.sendmail (TypeError: expected string or buffer)
R. David Murray rdmur...@bitdance.com added the comment: On the other hand, having a facility somewhere in the stdlib to pass a Message object to SMTP sendmail would be handy. I've made a note of this in my working notes for email6 to see if there's something we want to do about it. -- nosy: +r.david.murray priority: - normal resolution: - invalid stage: - committed/rejected ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8050 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
New submission from Ezio Melotti ezio.melo...@gmail.com: assertSameElements fails with sequences that contain unorderable types such as [2j, 5j, set(), frozenset()]. See also msg98744 in #7837. -- assignee: flox messages: 100654 nosy: ezio.melotti, flox, michael.foord priority: normal severity: normal stage: needs patch status: open title: assertSameElements fails with sequences that contain unorderable types type: behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Changes by Ezio Melotti ezio.melo...@gmail.com: -- components: +Library (Lib) versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Changes by Florent Xicluna florent.xicl...@gmail.com: -- keywords: +patch resolution: - accepted stage: needs patch - patch review Added file: http://bugs.python.org/file16495/issue8088_unordered_elements.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Florent Xicluna florent.xicl...@gmail.com added the comment: Patch against trunk. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Changes by Ezio Melotti ezio.melo...@gmail.com: -- versions: -Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7837] assertSameElements doesn't filter enough py3k warnings
Ezio Melotti ezio.melo...@gmail.com added the comment: Fixed in r78757 (trunk). I opened #8088 for the unorderable types problem. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7837 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Gregory P. Smith g...@krypto.org added the comment: I really don't care about the age of a bug. This bug is young. I've fixed many bugs over twice its age in the past. Regardless, I've got some serious subprocess internal refactoring changes coming in the very near future to explicitly deal with thread safety issues. I'm adding this one to my list of things to tackle. -- assignee: astrand - gregory.p.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7723] sqlite only accept buffer() for BLOB objects (input/output)
Florent Xicluna florent.xicl...@gmail.com added the comment: So we keep buffer() as the standard way to create BLOBs for 2.x? It is the only use of py3k deprecated buffer() which cannot be replaced in 2.x. Set to release blocker until a decision is made. -- priority: critical - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1731717] race condition in subprocess module
Yonas yona...@gmail.com added the comment: Gregory, Awesome! Approx. how long until we hear back from you in this report? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1731717 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1530559] struct.pack raises TypeError where it used to convert
Florent Xicluna florent.xicl...@gmail.com added the comment: I would suggest to raise a py3k warning instead of a plain warning. AFAIU the implicit conversion is OK in 2.7, and it is removed in 3.x. -- nosy: +flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1530559 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Ronald Oussoren ronaldousso...@mac.com added the comment: 2.6 should be fixed in r78805. I won't have time to merge the fix into the other branches until at best later tonight. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8032] Add gdb7 hooks to make it easier to debug Python
Dave Malcolm dmalc...@redhat.com added the comment: Martin: thanks for reviewing this. Re msg100537: sorry about the inauspicious start. I've added some bulletproofing for the case you discovered, and added two new unit tests. Re msg100538: OK. I've removed my name and the copyright notice in all places apart from the Misc/ACKS file. There are still some comments in the code where I use the first person singular. I'm attaching an updated patch against trunk -- Added file: http://bugs.python.org/file16496/add-gdb7-python-hooks-to-trunk-v2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8032 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
New submission from Ned Deily n...@acm.org: 2.6.5 release blocker 3.1.2 release blocker For 10.6, new universal build options were added to reflect the dropping of support in 10.6 for the ppc64 arch. The new options: --universal-archs=3-way - -arch {i386,x86_64,ppc) --universal-archs=intel - -arch {i386,x86_64} however do not add the executables and symlinks to select a -32 or -64 variant like the existing --universal-archs=all does and so these new build variants always run in 64-bit with no way to override it. A simple test in configure.in needs to be changed to recognize these new options. Trunk (2.7) and py3k (3.2) use a new execution-time mechanism to select 32- vs 64-bit execution and so do not exhibit this problem. (Ronald and I agree this should be a release-blocker. Patch to follow.) -- assignee: ronaldoussoren components: Macintosh messages: 100663 nosy: barry, benjamin.peterson, ned.deily, ronaldoussoren severity: normal status: open title: 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6 versions: Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8032] Add gdb7 hooks to make it easier to debug Python
Changes by Dave Malcolm dmalc...@redhat.com: Added file: http://bugs.python.org/file16497/diff-of-gdb7-hooks-v2-relative-to-v1.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8032 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8038] Provide unittest.TestCase.assertNotRegexpMatches
Ryszard Szopa ryszard.sz...@gmail.com added the comment: Here's the patch against unittest2 that implements assertNotRegexpMatches. -- keywords: +patch Added file: http://bugs.python.org/file16498/assertNotRegexpMatches.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8038 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Changes by Barry A. Warsaw ba...@python.org: -- priority: - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Barry A. Warsaw ba...@python.org added the comment: On Mar 08, 2010, at 08:20 PM, Ned Deily wrote: (Ronald and I agree this should be a release-blocker. Patch to follow.) BTW, the right thing to do in this case (for 2.6 anyway) is to set the issue to be a release blocker, so it gets my attention. I can always knock it down if I don't agree. In this case I do, so I've set the priority for you. Please try to fix this asap so we can get rc2 out. -Barry -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Florent Xicluna florent.xicl...@gmail.com added the comment: It could be fixed as part of #7832. -- superseder: - assertSameElements([0, 1, 1], [0, 0, 1]) does not fail ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: SIGINT.patch is the sum of all patches, it should be easier to review it. -- Added file: http://bugs.python.org/file16499/SIGINT.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8088] assertSameElements fails with sequences that contain unorderable types
Changes by Florent Xicluna florent.xicl...@gmail.com: -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8063] Call _PyGILState_Init() earlier in Py_InitializeEx()
STINNER Victor victor.stin...@haypocalc.com added the comment: My SIGINT.patch for #3137 moves the call to _PyGILState_Init() just before initsite(), so it doesn't change too much Py_InitializeEx() and it's enough for me :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5228] multiprocessing not compatible with functools.partial
joseph.h.garvin joseph.h.gar...@gmail.com added the comment: I think this bug still exists in Python 2.6.4, and I haven't tested 2.6.5, but since 2.6.4 was released 6 months after this bug was closed I assume it's still an issue. Running ndbecker's test program as is produces the following output on Solaris 10: Process PoolWorker-1: Process PoolWorker-2: Traceback (most recent call last): Traceback (most recent call last): File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 232, in _bootstrap File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 232, in _bootstrap Process PoolWorker-3: Traceback (most recent call last): File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 232, in _bootstrap self.run() self.run() File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 88, in run File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 88, in run self._target(*self._args, **self._kwargs) self._target(*self._args, **self._kwargs) File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/pool.py, line 57, in worker File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/pool.py, line 57, in worker self.run() task = get() task = get() File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/queues.py, line 352, in get File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/process.py, line 88, in run File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/queues.py, line 352, in get self._target(*self._args, **self._kwargs) File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/pool.py, line 57, in worker return recv() return recv() TypeError: type 'partial' takes at least one argument TypeError: type 'partial' takes at least one argument task = get() File /opt/app/g++lib6/python-2.6/lib/python2.6/multiprocessing/queues.py, line 352, in get return recv() TypeError: type 'partial' takes at least one argument -- nosy: +joseph.h.garvin versions: +Python 2.6 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5228 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7966] mhlib does not emit deprecation warning
Sjoerd Mullender sjo...@acm.org added the comment: mhlib is not officially deprecated, if I may believe PEP 4. Therefore I do not agree with the change that was made to this bug report. As far as I am concerned, the bug remains that mhlib uses a deprecated module. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7966 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8090] PEP 4 should say something about the standard library
New submission from Sjoerd Mullender sjo...@acm.org: When a module or feature is deprecated, all uses of the deprecated module/feature should be removed from the non-deprecated part of the distribution (and, I would argue, also from the other deprecated modules). I think PEP 4 should say something to this effect. I suggest adding a sentence to the section Procedure for declaring a module deprecated, something like: The proposal MUST include patches to remove any use of the deprecated module from the standard library. -- assignee: georg.brandl components: Documentation messages: 100671 nosy: georg.brandl, sjoerd severity: normal status: open title: PEP 4 should say something about the standard library ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8090 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8090] PEP 4 should say something about the standard library
Brian Curtin cur...@acm.org added the comment: I don't really think this is a documentation bug, more of an issue you have with the policy, in which case this is better being discussed on python-dev. -- nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8090 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7804] test_readline failure
Barry A. Warsaw ba...@python.org added the comment: I see this in 2.6 also, Ubuntu 9.10 and 10.04 (alpha). Marking this a release blocker for now, though I'll check to see if it's a regression or not. -- nosy: +barry priority: normal - release blocker versions: +Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7804 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8091] TypeError at the end of 'make test'
New submission from Barry A. Warsaw ba...@python.org: 'make test' on Ubuntu 10.04 alpha produces: 328 tests OK. 1 test failed: test_readline 37 tests skipped: test_aepack test_al test_applesingle test_bsddb test_bsddb185 test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_curses test_dl test_gl test_imageop test_imgfile test_kqueue test_linuxaudiodev test_macos test_macostools test_normalization test_ossaudiodev test_pep277 test_py3kwarn test_scriptpackages test_smtpnet test_socketserver test_startfile test_sunaudiodev test_timeout test_urllib2net test_urllibnet test_winreg test_winsound test_zipfile64 1 skip unexpected on linux2: test_bsddb Exception TypeError: TypeError('NoneType' object is not callable,) in bound method Popen.__del__ of subprocess.Popen object at 0x5d63650 ignored make: *** [test] Error 1 The readline failure is reported elsewhere. It's the TypeError at the end that's the problem here. I think this does not happen on Ubuntu 9.10. -- messages: 100674 nosy: barry priority: release blocker severity: normal status: open title: TypeError at the end of 'make test' versions: Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8065] Memory leak in readline.get_current_history_length
Changes by Zvezdan Petkovic zvez...@zope.com: -- nosy: +zvezdan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8065 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8091] TypeError at the end of 'make test'
Barry A. Warsaw ba...@python.org added the comment: flox barry, Taggnostr: all the tests using subprocess [17:42] flox test_bz2 test_cmd_line test_platform test_popen2 test_popen test_pydoc test_quopri test_signal test_subprocess test_sys test_threading test_unicodedata test_winsound flox you may test with this list as parameter, then shorten the list to find the culprit [17:43] flox (if it is repeatable) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8091] TypeError at the end of 'make test'
Barry A. Warsaw ba...@python.org added the comment: Does not error on Ubuntu 9.10 as far as I can tell. Seems to be only 10.04 (alpha) for some reason. I've only tested on 64 bit. This is probably not a release blocker. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Changes by Florent Xicluna florent.xicl...@gmail.com: Removed file: http://bugs.python.org/file16087/issue7832_assertItemsEqual.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Florent Xicluna florent.xicl...@gmail.com added the comment: Patch with documentation, tests, Misc/NEWS, following a discussion with Michael, Ezio and JP. -- priority: low - normal Added file: http://bugs.python.org/file16500/issue7832_assertSameElements_v2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
New submission from STINNER Victor victor.stin...@haypocalc.com: utf8 encoder doesn't work in backslashreplace error handler: \uDC80.encode(utf8, backslashreplace) TypeError: error handler should have returned bytes -- components: Unicode messages: 100678 nosy: haypo severity: normal status: open title: utf8, backslashreplace and surrogates versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8093] IDLE processes don't close
New submission from paul stadfeld mensana...@aol.com: So I started 3.1.2... Python 3.1.2rc1 (r312rc1:78742, Mar 7 2010, 07:49:40) [MSC v.1500 32 bit (Intel)] on win32 Type copyright, credits or license() for more information. And monitored Windows Task Manager (XP): Image NameUser Name CPU Mem Usage - pythonw.exe paul_stadfeld 0011,120 K pythonw.exe paul_stadfeld 0016,816 K I assume this is normal. I deliberately do something stupid: a = 222 b = a**b Ok, that will run for a while, long enough for me to watch the Task Manager: Image NameUser Name CPU Mem Usage - pythonw.exe paul_stadfeld ~55 ~30,548 K (constantly changing) pythonw.exe paul_stadfeld 0016,828 K So I do [Restart Shell] from IDLE's [Shell] menu: RESTART And try it again. a = 222 b = a**b But now it's different: Image NameUser Name CPU Mem Usage - pythonw.exe paul_stadfeld 0013,716 pythonw.exe paul_stadfeld ~50 ~30,548 K (constantly changing) pythonw.exe paul_stadfeld ~48 ~45,548 K (constantly changing) pythonw.exe paul_stadfeld 0016,892 K Looks like the previous process was never stopped. Trying to Restart Shell again and running same creates a 5th instance of pythonw.exe. RESTART a = 222 b = a**b Image NameUser Name CPU Mem Usage - pythonw.exe paul_stadfeld 0013,716 pythonw.exe paul_stadfeld ~50 ~54,548 K (constantly changing) pythonw.exe paul_stadfeld ~25 ~42,548 K (constantly changing) pythonw.exe paul_stadfeld ~25 ~54,548 K (constantly changing) pythonw.exe paul_stadfeld 0016,892 K Only this time I got an error trying to re-start. IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection Now I'm stuck, so I close the Python Shell window. But closing the window only stopped one of the pythonw.exe instances. The three active processes are still running full tilt (the one quiescent process remains quiescent.) This appears to be a process leak in addition to it being a memory leak. Also, had one of the processes that won't stop opened a script from a USB port, then Windows would refuse to eject the USB drive as it correctly thinks some process is still using it. Of course, since the application is closed, there's not suppoed to be any such process, so it's not obvious where the problem is unless you look at the process table in Windows Task Manager and manually halt all the renegade pythonw.exe processes that are still running. At which point Windows will allow the USB to be ejected. -- components: IDLE messages: 100679 nosy: mensanator severity: normal status: open title: IDLE processes don't close versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8093 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6697] Check that _PyUnicode_AsString() result is not NULL
STINNER Victor victor.stin...@haypocalc.com added the comment: See also issue #8092. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6697 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
STINNER Victor victor.stin...@haypocalc.com added the comment: See also issue #6697. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
STINNER Victor victor.stin...@haypocalc.com added the comment: As requested by Guido, here is a new patch including the fix for the site module: catch errors in execsitecustomize() and execusercustomize(). -- Added file: http://bugs.python.org/file16501/SIGINT-2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16488/initsite.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16491/initiliaze_pycodec_error.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16492/tokenizer_error.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16493/import_no_global.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16494/main_pending_calls.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3137] Python doesn't handle SIGINT well if it arrives during interpreter startup
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file16499/SIGINT.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3137 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6697] Check that _PyUnicode_AsString() result is not NULL
STINNER Victor victor.stin...@haypocalc.com added the comment: unicode_fromformat_U.patch: replace PyUnicode_FromFormat(..%s..., ..., _PyUnicode_AsString(obj)) by PyUnicode_FromFormat(...%U..., ..., obj). It replaces also %.200s by %U, so the output is no more truncated. -- Added file: http://bugs.python.org/file16502/unicode_fromformat_U.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6697 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8093] IDLE processes don't close
Changes by Brian Curtin cur...@acm.org: -- components: +Windows nosy: +brian.curtin priority: - normal stage: - needs patch type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8093 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6538] MatchObject is not a hyperlink in the 're' module documentation
Asheesh Laroia ashe...@asheesh.org added the comment: Hey Ryan, I took a look at the diff you attached here. It looks like you did There are some whitespace-only changes -- for example, you remove and then re-insert the line beginning with The name of the last matched capturing group. Can you re-submit your most recent patch without the unneeded whitespace-only changes? There's a light at the end of the tunnel! -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6538 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Ezio Melotti ezio.melo...@gmail.com added the comment: To summarize, the possible behaviors are: 1) check order, check duplicates (i.e. assertSequenceEqual); 2) check order, ignore duplicates (probably useless); 3) ignore order, check duplicates (useful but missing); 4) ignore order, ignore duplicates (i.e. assertSameElements now); The possible solutions are: a) change assertSameElements to match behavior 3 (see Florent patch): pros: implements 3 (i.e. the expected behavior); 4 can be replaced easily *; shorter function call for common use; cons: breaks compatibility; the name is still kind of confusing; b) add check_order to assertSequenceEqual, leave assertSameElements unchanged: pros: covers 1, 3 and 4; backward compatible; cons: assertSameElements is still confusing; c) add check_order to assertSequenceEqual, deprecate and then remove assertSameElements: pros: covers 1 and 3; removes a confusing function; 4 can be replaced easily *; cons: deprecates a quite new function; d) add check_duplicates to assertSameElements: pros: covers 1, 3 and 4; backward compatible (with default == False); cons: assertSameElements would be even more confusing; * assertSameElements can be replaced by assert[Set]Equal(set(a), set(b)), but this doesn't work with unhashable elements (they worked with assertSameElements). I like c) because it removes a confusing function, and simplifies the API of unittest that IMHO it's already growing too complex (even if it would be handy to have a function that does 3 directly without having to write check_order=False). -- priority: normal - low ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4180] warnings.simplefilter(always) does not make warnings always show up
Antoine Pitrou pit...@free.fr added the comment: It sounds like it would be cleaner to apply Brett's idea in msg75122, rather than have the user override (and alternate implementations implement) another obscure hook. We have enough hooks that nobody knows about, IMHO. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4180 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
STINNER Victor victor.stin...@haypocalc.com added the comment: This issue is a regression introduced by r72208 to fix the issue #3672. Attached patch fixes PyUnicode_EncodeUTF8() if unicode_encode_call_errorhandler() returns an unicode string (eg. backslackreplace error handler). I don't know unicodeobject.c code (very well), and my patch should be far from being perfect. I suppose that the maximum length of an escaped characters is 8 bytes (xmlcharrefreplace error error for U+D). When the first lone surrogate is found, reallocate the buffer to size*8 bytes. The escaped character have to be an ASCII character or an UnicodeEncodeError is raised. Note: unicode_encode_ucs1() doesn't have hardcoded for the maximum length ot escaped string. Its code might be reused in PyUnicode_EncodeUTF8() to remove the hardcoded limits. -- keywords: +patch Added file: http://bugs.python.org/file16503/utf8_surrogate_error.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6538] MatchObject is not a hyperlink in the 're' module documentation
Brian Curtin cur...@acm.org added the comment: I've reviewed the patch and do not see any unnecessary whitespace changes in his patch. -- nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6538 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8092] utf8, backslashreplace and surrogates
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +lemburg, loewis priority: - normal stage: - patch review type: - behavior versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8091] TypeError at the end of 'make test'
Antoine Pitrou pit...@free.fr added the comment: Probably a duplicate of issue5099. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6538] MatchObject is not a hyperlink in the 're' module documentation
Changes by Ryan Arana ryan.ar...@gmail.com: Removed file: http://bugs.python.org/file16274/MatchObjectLinksFix.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6538 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5099] subprocess.POpen.__del__() AttributeError (os module == None!)
Antoine Pitrou pit...@free.fr added the comment: By the way, stderr will contain [XXX refs] as the last line with Python compiled in debug mode. The remove_stderr_debug_decorations() function will help you ignore this line. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5099 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6538] MatchObject is not a hyperlink in the 're' module documentation
Ryan Arana ryan.ar...@gmail.com added the comment: I tried to format the methods of the class(es) as they are formatted in other files, which is why I added the whitespace. I can go back and remove that if that's what would be preferred. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6538 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Gregory P. Smith g...@krypto.org added the comment: Looking through the thousands of uses of assertSameElements in our internal code base at work I see many uses of it that are likely not hashable items in the sequences being compared. The largest use of course is with lists and tuples of hashables where another assert method may have even made more sense, but that is not the only use. As documented in Python 3.1 I think the behavior of assertSameElements is accurate and makes sense. We should add an extra note to the documentation to explicitly mention that it does not care how many of a given element occur in either sequence. [0, 1, 1] and [0, 0, 1] do in fact have the same elements. If you want a different behavior please add that as a feature. As such, Ezio's option (b) and (d) are the only ones I'm in favor of. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Ned Deily n...@acm.org added the comment: The attached patches fix the problem for 2.6 and 3.1: 1. configure(.in) is changed to invoke the existing 4way build targets for --with-universal-archs values of 3-way and intel as well as all. 2. configure(.in) passes the necessary lipo -extract arch values into the Mac/Makefile for building Python-32 and Python-64. (Note, the solution here is simpler than what was required for trunk and py3k because the use of lipo is isolated to the 4way build targets which can only be used for universal builds on 10.5+.) 3. a typo in the 2.6 Mac/README file is corrected and the previous updates are copied over from 2.6 to the 3.1 Mac/README. Since configure.in is updated, it is necessary to run autoconf on both 2.6 and 3.1 after applying these patches. -- Added file: http://bugs.python.org/file16504/issue-sl-configure-32-26.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file16505/issue-sl-configure-32-31.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6538] MatchObject is not a hyperlink in the 're' module documentation
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6538 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8091] TypeError at the end of 'make test'
Barry A. Warsaw ba...@python.org added the comment: Not a release blocker. -- priority: release blocker - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Barry A. Warsaw ba...@python.org added the comment: It sounds like this is fixed for 2.6.5 now. I'm bumping the priority down and removing 2.6 from the Versions. -- priority: release blocker - high versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Ned Deily n...@acm.org added the comment: Correct inadvertent deletion in the 3.1 Mac/README. -- Added file: http://bugs.python.org/file16506/issue-sl-configure-32-31-rev1.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8089] 2.6/3.1 32-bit/64-bit universal builds always run in 64-bit on 10.6
Changes by Ned Deily n...@acm.org: Removed file: http://bugs.python.org/file16505/issue-sl-configure-32-31.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7804] test_readline failure
Changes by Barry A. Warsaw ba...@python.org: -- priority: release blocker - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7804 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6877] enable compilation of readline module on Mac OS X 10.5 and 10.6
Ned Deily n...@acm.org added the comment: Also note that this feature has not been backported to 3.1 which means it will not be in the upcoming 3.1.2 release. (It will not be an issue for the python.org 3.1.2 installer which will be built with GNU readline as usual to support older systems.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6877 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Ned Deily n...@acm.org added the comment: Fix verified for 2.6. It should still be considered a release blocker for 3.1.2. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Changes by Benjamin Peterson benja...@python.org: -- priority: high - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8036] Interpreter crashes on invalid arg to spawnl on Windows
Gabriel Genellina gagsl-...@yahoo.com.ar added the comment: In case it matters, 3.0.1 does NOT crash. -- nosy: +gagenellina ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8036 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Florent Xicluna florent.xicl...@gmail.com added the comment: Gregory P. Smith wrote: Looking through the thousands of uses of assertSameElements in our internal code base at work I see many uses of it that are likely not hashable items in the sequences being compared. The method assertSameElements will still support unhashable elements. In this case the fixed behaviour will be harmless for your code base, like for many other users. Example with unhashable entries: assertSameElements(list([3], [None], [3]), tuple([None], [3], [3])) == pass assertSameElements(list([3], [None], [3]), tuple([None], [None], [3])) == fails The patch only fix the 2nd case here. Before the patch it didn't fail on this case. I still don't see real cases where we need that [0, 0, 1] and [0, 1, 1] compare equal. And this enhancement will be less surprising for the user. Currently, if someone uses assertSameElements it could expect that it fails when the count of elements is not the same. And it will never notice that he's wrong and that his unittest have a flaw. In a sense, it is not helpful for the end user to preserve the current behaviour. There's a risk that tests will not fail when they should. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7832] assertSameElements([0, 1, 1], [0, 0, 1]) does not fail
Changes by Florent Xicluna florent.xicl...@gmail.com: -- priority: low - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7832 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8067] OS X Installer: build errors on 10.6 when targeting 10.4 and earlier
Ronald Oussoren ronaldousso...@mac.com added the comment: 3.2 and 3.1 should now also be fixed (in r78808 and r78809) Please test. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8067 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled
Changes by Florent Xicluna florent.xicl...@gmail.com: Removed file: http://bugs.python.org/file16075/issue7092_py3k_warnings_args_v2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled
Changes by Florent Xicluna florent.xicl...@gmail.com: Removed file: http://bugs.python.org/file16076/issue7092_py3k_warnings_noargs_v2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com