[issue31724] test_xmlrpc_net should use something other than buildbot.python.org

Change by Zachary Ware : -- stage: patch review -> needs patch ___ Python tracker ___

[issue31724] test_xmlrpc_net should use something other than buildbot.python.org

Change by Zachary Ware : -- keywords: +patch pull_requests: +3894 stage: needs patch -> patch review ___ Python tracker ___

[issue31724] test_xmlrpc_net should use something other than buildbot.python.org

Change by Zachary Ware : -- title: test_xmlrpc should use something other than buildbot.python.org -> test_xmlrpc_net should use something other than buildbot.python.org ___ Python tracker

[issue31724] test_xmlrpc should use something other than buildbot.python.org

New submission from Zachary Ware : With the upgrade to buildbot 0.9, the xmlrpc interface to buildbot.python.org is removed, causing test_xmlrpc to fail. The test should hit a different host, possibly on pythontest.net? -- components: Tests messages: 303894

[issue31267] threading.Timer object is affected by changes to system time: Python locks should use a monotonic clock if available

Thomas Keppler added the comment: Hello Victor, thank you for your update on this issue. By looking through the other bug reports you listed, it looks as if measures were implemented but never merged. Am I right with this observation? If so, will we ever see a switch

[issue31655] SimpleNamespace accepts non-string keyword names

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31655] SimpleNamespace accepts non-string keyword names

Serhiy Storchaka added the comment: New changeset cae6e4775b37c412609d3a0d303c0831ff0012ff by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31655: Validate keyword names in SimpleNamespace constructor. (GH-3909) (#3920)

[issue31655] SimpleNamespace accepts non-string keyword names

Change by Roundup Robot : -- pull_requests: +3893 ___ Python tracker ___

[issue31655] SimpleNamespace accepts non-string keyword names

Serhiy Storchaka added the comment: New changeset 79ba471488b936abda5ba5234b1ea90cbc94cae6 by Serhiy Storchaka in branch 'master': bpo-31655: Validate keyword names in SimpleNamespace constructor. (#3909)

[issue31165] list_slice() does crash if the list is mutated indirectly by PyList_New()

Serhiy Storchaka added the comment: > What does "changing" mean exactly? I'm not a GC expert. Maybe we should add a global flag that disable calling nontrivial destructors and set it in PyObject_GC_New(). The objects with nontrivial destructor should be added to

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

Change by Oren Milman : -- keywords: +patch pull_requests: +3892 stage: -> patch review ___ Python tracker ___

[issue25862] TextIOWrapper assertion failure after read() and SEEK_CUR

Change by Zackery Spytz : -- keywords: +patch pull_requests: +3891 stage: needs patch -> patch review ___ Python tracker ___

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

Steve Dower added the comment: Okay, just tested taking out the C++ handler and it goes straight to an error report. Not ideal, especially since the error is logged against "python.exe" and "ucrtbase.dll" (which is going to make my life harder when reviewing the

[issue31701] faulthandler dumps 'Windows fatal exception: code 0xe06d7363'

Steve Dower added the comment: Haven't had a chance to test this, but I suspect our change should depend on what happens when a C++ exception is actually unhandled. In this case, the following sequence has occurred: * exception is raised * debug event is raised (if a

[issue31720] msilib.MSIError is spelled MsiError in documentation

Mariatta Wijaya added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.4, Python 3.5, Python 3.8 ___ Python tracker

[issue31720] msilib.MSIError is spelled MsiError in documentation

Mariatta Wijaya added the comment: New changeset 5f396dba1d11356ab18e3bec130596197e741a64 by Mariatta (Miss Islington (bot)) in branch '3.6': bpo-31720: msilib documentation, change MsiError into MSIError (GH-3914) (GH-3917)

[issue31695] Improve bigmem tests

Antoine Pitrou added the comment: +1 to all this :-) -- nosy: +pitrou ___ Python tracker ___

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: No, but if we need to do 3.6.4 quickly for another reason, let me know and I'll make this change. It only affects people who are trying to share intermediate build files (which for MSVC purposes, includes static libraries) between their

[issue31723] refleaks in zipimport when calling zipimporter.__init__() more than once

New submission from Oren Milman : The following code causes refleaks: import zipimport zi = zipimport.zipimporter.__new__(zipimport.zipimporter) zi.__init__('bar.zip') zi.__init__('bar.zip') zi.__init__('bar.zip\\foo') This is because zipimport_zipimporter___init___impl() (in

[issue31165] list_slice() does crash if the list is mutated indirectly by PyList_New()

Antoine Pitrou added the comment: > I think than changing the Garbage Collector would be easier. What does "changing" mean exactly? What will be the effects on normal code? How do you know that it will not create new problems that didn't exist before? --

[issue31720] msilib.MSIError is spelled MsiError in documentation

Change by Roundup Robot : -- pull_requests: +3890 ___ Python tracker ___

[issue31165] list_slice() does crash if the list is mutated indirectly by PyList_New()

Serhiy Storchaka added the comment: See a4dd011259fa6f3079bd0efd95b3a136c0e3c190. The commit message: Tentative fix for a problem that Tim discovered at the last moment, and reported to python-dev: because we were calling dict_resize() in PyDict_Next(),

[issue31720] msilib.MSIError is spelled MsiError in documentation

Change by Roundup Robot : -- pull_requests: +3889 ___ Python tracker ___

[issue31165] list_slice() does crash if the list is mutated indirectly by PyList_New()

Change by Serhiy Storchaka : -- pull_requests: +3888 ___ Python tracker ___ ___

[issue31722] _io.IncrementalNewlineDecoder doesn't inherit codecs.IncrementalDecoder

Serhiy Storchaka added the comment: As a consequence, _io.IncrementalNewlineDecoder doesn't have the error attribute. -- ___ Python tracker

[issue31718] some methods of uninitialized io.IncrementalNewlineDecoder objects raise SystemError

Change by Serhiy Storchaka : -- nosy: +benjamin.peterson, stutzbach versions: +Python 2.7, Python 3.6 ___ Python tracker

[issue31722] _io.IncrementalNewlineDecoder doesn't inherit codecs.IncrementalDecoder

New submission from Serhiy Storchaka : It is documented that io.IncrementalNewlineDecoder inherits codecs.IncrementalDecoder. And the Python implementation does. But the C implementation doesn't. >>> issubclass(_pyio.IncrementalNewlineDecoder,

[issue31721] assertion failure in FutureObj_finalize() after setting _log_traceback to True

New submission from Oren Milman : The following code causes an assertion failure in FutureObj_finalize() (in Modules/_asynciomodule.c): import asyncio asyncio.Future()._log_traceback = True Maybe we should allow Python code to only set it to False, and raise a ValueError in

[issue31720] msilib.MSIError is spelled MsiError in documentation

Change by Tzu-ping Chung : -- keywords: +patch pull_requests: +3887 stage: -> patch review ___ Python tracker ___

[issue31720] msilib.MSIError is spelled MsiError in documentation

New submission from Tzu-ping Chung : The title describes it all. -- assignee: docs@python components: Documentation messages: 303877 nosy: docs@python, uranusjr priority: normal severity: normal status: open title: msilib.MSIError is spelled MsiError in documentation

[issue31712] subprocess with stderr=subprocess.STDOUT hang

l4mer added the comment: confirm, OpenSSH_7.3p1 solve the problem. Thanks for help. -- resolution: -> third party status: -> closed ___ Python tracker

[issue31718] some methods of uninitialized io.IncrementalNewlineDecoder objects raise SystemError

Oren Milman added the comment: With regard to refleaks in __init__() methods, i started looking for similar refleaks in the codebase, and hope to open an issue to fix them soon. -- ___ Python tracker

[issue31712] subprocess with stderr=subprocess.STDOUT hang

Martin Panter added the comment: Scanning over the Open SSH commits for 7.3p1 https://github.com/openssh/openssh-portable/compare/V_7_2_P2...V_7_3_P1 it looks like this commit https://github.com/openssh/openssh-portable/commit/d2d6bf864e52af8491a60dd507f85b74361f5da3

[issue31718] some methods of uninitialized io.IncrementalNewlineDecoder objects raise SystemError

Change by Oren Milman : -- keywords: +patch pull_requests: +3886 stage: -> patch review ___ Python tracker ___

[issue31712] subprocess with stderr=subprocess.STDOUT hang

l4mer added the comment: Interesting when using faster machine with newer ssh don't see this problem :) janusz@t560:~$ ssh -V OpenSSH_7.3p1 Ubuntu-1ubuntu0.1, OpenSSL 1.0.2g 1 Mar 2016 janusz@t560:~$ ssh root@localhost -O exit; strace python test.py

[issue31712] subprocess with stderr=subprocess.STDOUT hang

l4mer added the comment: I) Manual test for subprocess32: janusz@nc6120:~$ python Python 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import subprocess32 >>> cmd =

[issue1104] msilib.SummaryInfo.GetProperty() truncates the string by one character

Change by Tzu-ping Chung : -- nosy: +uranusjr ___ Python tracker ___ ___ Python-bugs-list

[issue31712] subprocess with stderr=subprocess.STDOUT hang

l4mer added the comment: janusz@nc6120:~$ ssh -V OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g 1 Mar 2016 janusz@nc6120:~$ I) manual check janusz@nc6120:~$ ssh root@localhost -p 50494 -O exit janusz@nc6120:~$ python Python 2.7.12 (default, Nov 19 2016, 06:48:10)