[issue26571] turtle regression in 3.5

New submission from Ellison Marks: I noticed some odd behaviour when running some turtle code I wrote using python 3.5. A simplified example: >>> from turtle import Turtle >>> t = Turtle() >>> t.getscreen().bye() # or manually close the turtle window >>> t2 = Turtle() Traceback (most recent

[issue19914] help([object]) returns "Not enough memory." on standard Python types, object and object functions

Eryk Sun added the comment: For posterity for anyone that finds this old issue, I investigated this problem in the debugger in Windows 7. It turns out that more.com (the pager used by Python's help) calls MultiByteToWideChar [1] with dwFlags passed as MB_PRECOMPOSED (1), which is forbidden

[issue26570] comma-separated cookies with expires header do not parse properly

New submission from Ilya Kreymer: This is a peculiar regression in 3.5 where a comma-separated cookie following an expires field is considered invalid: Ex: which results in a silent error/empty cookie in 3.5.1 Python 3.5.1 (default, Dec 26 2015, 18:11:22) [GCC 4.2.1 Compatible Apple LLVM

[issue18320] python installation is broken if prefix is overridden on an install target

Ned Deily added the comment: Allowing prefix to be overridden after configure-time is certainly not the most critical shortcoming of the Python build system and it is possible someone is relying on that behavior. Since no one, including me, seems very interested at this point in trying to

[issue26562] Large Involuntary context switches during oom-killer

Damian Myerscough added the comment: Thanks for the feedback, I will continue to dig into this. I know processes go crazy sometimes when OOM killer kicks off, I just wanted to rule out a Python bug or if anyone in the community has seen this before. Thanks --

[issue18320] python installation is broken if prefix is overridden on an install target

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___

[issue25597] unittest.mock does not wrap dunder methods (__getitem__ etc)

Robert Collins added the comment: I think this is a valid mock bug; it likely needs some thoughtful exhaustive testing, and obviously support added for it. -- stage: -> test needed title: unittest.mock does not wrap dict objects correctly -> unittest.mock does not wrap dunder methods

[issue25894] unittest subTest failure causes result to be omitted from listing

Robert Collins added the comment: The basic model is this: - a test can have a single outcome [yes, the api is ambiguous, but there it is] - subtests let you identify multiple variations of a single test (note the id tweak etc) and *may* be reported differently We certainly must not report

[issue26295] Random failures when running test suite in parallel (-m test -j0) caused by test_regrtest

STINNER Victor added the comment: Hum, test_doctest, test_zipfile and test_pyclbr fail if test is converted to a package (if Lib/test/__init__.py is removed). Attached patch fixes test_zipfile. I created the issue #26569 for test_pyclbr failure. -- Added file:

[issue26569] pyclbr.readmodule() and pyclbr.readmodule_ex() doens't support packages

New submission from STINNER Victor: While working on the issue #26295 which converts the test module to a package, I noticed that pyclbr doesn't work with packages: test_pyclbr fails when test becomes a package. Attached patch fixes pyclbr._readmodule(): * Replace

[issue26569] pyclbr.readmodule() and pyclbr.readmodule_ex() don't support packages

Changes by STINNER Victor : -- title: pyclbr.readmodule() and pyclbr.readmodule_ex() doens't support packages -> pyclbr.readmodule() and pyclbr.readmodule_ex() don't support packages ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

Roundup Robot added the comment: New changeset 769dfcb701ee by Victor Stinner in branch 'default': Issue #26564: Fix test_capi https://hg.python.org/cpython/rev/769dfcb701ee -- ___ Python tracker

[issue26538] regrtest: setup_tests() must not replace module.__path__ (_NamespacePath) with a simple list // importlib & abspath

Roundup Robot added the comment: New changeset 96b73b649b15 by Victor Stinner in branch 'default': regrtest: Fix module.__path__ https://hg.python.org/cpython/rev/96b73b649b15 -- nosy: +python-dev ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

Roundup Robot added the comment: New changeset 8215dae7ec3c by Victor Stinner in branch 'default': Oops, revert unwanted change used to create an example https://hg.python.org/cpython/rev/8215dae7ec3c -- ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

Roundup Robot added the comment: New changeset cef6a32d805f by Victor Stinner in branch 'default': On memory error, dump the memory block traceback https://hg.python.org/cpython/rev/cef6a32d805f -- ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

Roundup Robot added the comment: New changeset 18a19e62bac5 by Victor Stinner in branch 'default': Enhance and rewrite traceback dump C functions https://hg.python.org/cpython/rev/18a19e62bac5 New changeset fea3c6e9a38e by Victor Stinner in branch '3.5': _tracemalloc: store lineno as unsigned

[issue18320] python installation is broken if prefix is overridden on an install target

Martin Panter added the comment: I agree with Martin v. Löwis that this is not a real bug. Cosmicduck doesn’t seem aware of the “configure --prefix=. . .” option, but I don’t think it is right to add hacks to the makefile to prevent overriding variables. -- nosy: +martin.panter

[issue22359] Remove incorrect uses of recursive make

Xavier de Gaye added the comment: > But I am a bit worried at the new makefile syntax [ifeq directive and > $(findstring) function]. I suspect it is Gnu specific, and that Python tries > to support other versions of Make as well. Yes, they are both GNU extensions :( To avoid modifying

[issue26568] Add a new warnings.showmsg() function taking a warnings.WarningMessage object

STINNER Victor added the comment: I'm not sure about the method names showmsg() and formatmsg(). Maybe: showwarnmsg() and formatwarnmsg()? First I used warnings.show() and warnings.format(), but "format()" is already the name of a builtin function. By the way, I would prefer to use

[issue24263] unittest cannot load module whose name starts with Unicode

Robert Collins added the comment: sih4sing5hong5 - I think we do need a test in fact - it can be done using mocks, but right now I think the patch has a bug - it looks for isidentifier on $thing.py, but not on just $thing (which we need to do to handle packages, vs modules). --

[issue26560] Error in assertion in wsgiref.handlers.BaseHandler.start_response

Changes by SilentGhost : -- nosy: +pje type: -> behavior versions: +Python 3.6 ___ Python tracker ___

[issue26565] [ctypes] Add value attribute to non basic pointers.

Changes by SilentGhost : -- nosy: +amaury.forgeotdarc, belopolsky, meador.inge versions: +Python 3.6 ___ Python tracker ___

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: Attached patch should fix the issue. -- keywords: +patch Added file: http://bugs.python.org/file42174/PyGILState_Ensure.patch ___ Python tracker

[issue20891] PyGILState_Ensure on non-Python thread causes fatal error

STINNER Victor added the comment: ptest.c: Portable example using Python API. -- Added file: http://bugs.python.org/file42173/ptest.c ___ Python tracker

[issue26102] access violation in PyErrFetch if tcur==null in PyGILState_Release

STINNER Victor added the comment: Good news: it looks like I fixed the Py_FatalError() bug in the issue #26558. Py_FatalError() can again be called with the GIL released. The bug was introduced in Python 3.0. Since your issue is a bug in your code and that Py_FatalError() was fixed, I close

[issue26558] Disable PyGILState_Check() when Py_NewInterpreter() is called and add more checks on the GIL

Roundup Robot added the comment: New changeset b394fc71f92a by Victor Stinner in branch '3.5': Fix Py_FatalError() if called without the GIL https://hg.python.org/cpython/rev/b394fc71f92a New changeset c298c6d8b324 by Victor Stinner in branch '3.5': faulthandler: Test Py_FatalError() with GIL

[issue26558] Disable PyGILState_Check() when Py_NewInterpreter() is called and add more checks on the GIL

STINNER Victor added the comment: Ok, it looks like buildbots are happy. I close the issue. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

STINNER Victor added the comment: I reviewed my own patch on Rietveld :-) -- ___ Python tracker ___ ___

[issue26568] Add a new warnings.showmsg() function taking a warnings.WarningMessage object

New submission from STINNER Victor: Currently, the warnings.showformat() function take between 4 and 6 parameters and it's not possible to add new parameters. warnings.showformat() calls warnings.formatwarnings() with 5 parameters. Again, it's not easy to pass new parameters. I would like to

[issue26567] ResourceWarning: Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is emitted

STINNER Victor added the comment: > Backward-compatibility problem: The C function PyErr_ResourceWarning() always > call warnings.showwarning() with the keyword parameter source. If an > application replaces the warnings.showwarning() function, it will probably > fail because it doesn't know

[issue26040] Improve coverage and rigour of test.test_math

Changes by Serhiy Storchaka : -- nosy: +christian.heimes, eric.smith, lemburg, serhiy.storchaka, stutzbach versions: +Python 3.5 ___ Python tracker

[issue26564] Malloc debug hooks: display memory block traceback on error

STINNER Victor added the comment: See also the issue #26567: "Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is emitted". -- ___ Python tracker

[issue26567] ResourceWarning: Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is emitted

Changes by STINNER Victor : -- title: Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is emitted -> ResourceWarning: Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is

[issue26567] Use tracemalloc to display the traceback where an object was allocated when a ResourceWarning is emitted

New submission from STINNER Victor: Python emits ResourceWarning when an object using limited resource is destroyed without being explicitly closed: files, sockets, etc. The problem is that it's hard to find where the object comes from, since the warning can occur very late, in the garbage

[issue24230] tempfile.mkdtemp() doesn't work with bytes paths

STINNER Victor added the comment: """ Today we're doing something like this: tmpdir = tempfile.mkdtemp('', 'hgtests.', d and d.decode('utf-8')).encode('utf-8') """ Don't do that. UTF-8 is not the right encoding. Use os.fsencode() and os.fsdecode(). Internally, Python uses

[issue24230] tempfile.mkdtemp() doesn't work with bytes paths

STINNER Victor added the comment: I don't understand the rationale to add new functions using bytes filenames. IMHO it's a bad practice to pass bytes filenames to write portable code. On Windows, bytes lead to strange bugs: os.listdir(bytes) gives you filenames which don't exist when a

[issue26562] Large Involuntary context switches during oom-killer

STINNER Victor added the comment: > When oom-killer is trigger IMHO this is your root problem. > When oom-killer is trigger I see a large number of involuntary context > switches ... The principle of *involuntarty* context switches is that the application is not responsible for them. > I

[issue26566] Failures on FreeBSD CURRENT buildbot

Roundup Robot added the comment: New changeset 93b998d47bc0 by Victor Stinner in branch 'default': Issue #26566: Rewrite test_signal.InterProcessSignalTests https://hg.python.org/cpython/rev/93b998d47bc0 -- nosy: +python-dev ___ Python tracker

[issue26523] multiprocessing ThreadPool is untested

Changes by Antoine Pitrou : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___

[issue26523] multiprocessing ThreadPool is untested

Roundup Robot added the comment: New changeset 4cabf12b7fc6 by Antoine Pitrou in branch '3.5': Issue #26523: The multiprocessing thread pool (multiprocessing.dummy.Pool) was untested. https://hg.python.org/cpython/rev/4cabf12b7fc6 New changeset 131f92510164 by Antoine Pitrou in branch

[issue26562] Large Involuntary context switches during oom-killer

Antoine Pitrou added the comment: Why would it be a Python issue? By construction I doubt the OOM killer lets the process run anything before force-killing it. -- nosy: +pitrou ___ Python tracker

[issue26566] Failures on FreeBSD CURRENT buildbot

Changes by koobs : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list

[issue26566] Failures on FreeBSD CURRENT buildbot

New submission from STINNER Victor: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%20CURRENT%203.x/builds/218/steps/test/logs/stdio == FAIL: test_terminate (test.test_subprocess.POSIXProcessTestCase)

[issue26523] multiprocessing ThreadPool is untested

Antoine Pitrou added the comment: > Is it worth to change multiprocessing.Pool in _TestPoolWorkerErrors > and _TestPoolWorkerLifetime? Currently they work only for processes, > but may be they can be generalized. Perhaps as another issue? It may be more involved than this one. --

[issue17758] test_site fails when the user does not have a home directory

STINNER Victor added the comment: Everything is possible. It's just a matter of priorities. Do you want to work on a patch. I'm not really interested. If you consider that it'd worth, open a new issue. I close this issue since the iniyal bug is closed. --

[issue17758] test_site fails when the user does not have a home directory

koobs added the comment: @Victor, it would be nice if this test could instead use/fake/mock what it needs in the build directory, or is this not possible because it needs an 'actual' user/group context to work? -- nosy: +koobs ___ Python tracker

[issue26499] http.client.IncompleteRead from HTTPResponse read after part reading file

Martin Panter added the comment: Here is a modified version of the tests that I propose to commit soon. I trimmed the size of the tests down and simplified some of them. I also mentioned that BufferedIOBase is supported in the documentation. -- stage: patch review -> commit review