[issue7481] Failing to start a thread leaves zombie thread in initial state
Changes by Nir Aides n...@winpdb.org: -- nosy: +nirai ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7481 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7006] The replacement suggested for callable(x) in py3k is not equivalent
Trundle andy-pyt...@hammerhartes.de added the comment: What Joe Amenta stumbled across is that ABCMeta caches its subclass checks. If you call ``isinstance(spam, Callable)`` and after that delete `type(spam).__call__`, every other call of ``isinstance(spam, Callable)`` will still return True. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7576] Avoid warnings in PyModuleDef_HEAD_INIT
New submission from Ronald Oussoren ronaldousso...@mac.com: When running GCC with warnings the compiler can warn about incomplete structure initializers. This gives spurious warnings when initializing a PyModuleDef structure using PyModuleDef_HEAD_INIT The attached patchs changes PyModuleDef_HEAD_INIT to explicitly initialize all fields in PyModuleDef_Base. An example warning that is silenced by this patch: Modules/objc/test/structpointer2.m:19: warning: missing initializer Modules/objc/test/structpointer2.m:19: warning: (near initialization for ‘mod_module.m_base.m_init’) -- files: moduleobject-init-warnings.patch keywords: needs review, patch, patch messages: 96881 nosy: ronaldoussoren priority: normal severity: normal stage: patch review status: open title: Avoid warnings in PyModuleDef_HEAD_INIT type: compile error versions: Python 3.2 Added file: http://bugs.python.org/file15672/moduleobject-init-warnings.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7576 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7006] The replacement suggested for callable(x) in py3k is not equivalent
Nick Coghlan ncogh...@gmail.com added the comment: Ah yes, I misread the example. Agreed that that is a change in behaviour then - it is possible to clear the caches if absolutely necessary, but doing so isn't particularly portable. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7006] The replacement suggested for callable(x) in py3k is not equivalent
Joe Amenta ament...@msu.edu added the comment: I believe that this patch works like you described... Attached a patch with more test cases to show this. (the [1:] parts are to make the test cases readable; they will still pass if all the leading newlines are removed from the triple-quoted strings and all [1:] are removed :-) -- Added file: http://bugs.python.org/file15673/new_callable_semantics_moretests.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7484] smtplib: verify breaks with Postfix servers
Pablo Mouzo pablomo...@gmail.com added the comment: This patch solves the problem with the VRFY command, but I'm still wondering if this happens with other commands too. -- keywords: +patch nosy: +pablomouzo Added file: http://bugs.python.org/file15674/issue7484-trunk.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7484] smtplib: verify breaks with Postfix servers
Changes by Pablo Mouzo pablomo...@gmail.com: Added file: http://bugs.python.org/file15675/issue7484-py3k.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7484 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7006] The replacement suggested for callable(x) in py3k is not equivalent
Joe Amenta ament...@msu.edu added the comment: To elaborate on my last comment: - touch_import looks for the required import binding in any scope, and it will add a global import if not found, otherwise it leaves it alone - the import added does not have a newline prefix, so if the newlines were left in, (without [1:]) the tests would fail. However, I found that the test cases are easier to read if they all start on the same indentation level, so adding a newline for the reader but telling the parser to ignore it makes readable, correct test cases. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6710] hotshot stats load causes TypeError when multiple files are loaded
Ezio Melotti ezio.melo...@gmail.com added the comment: The change that causes this problem has been introduced in r60149 to fix #1269. -- nosy: +ezio.melotti, georg.brandl, therve priority: - normal stage: - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6710 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7519] ConfigParser can't read files with BOM markers
Changes by Benjamin Peterson benja...@python.org: -- title: CompileParser can't read files with BOM markers - ConfigParser can't read files with BOM markers ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7519 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
