[issue38290] cleanup ababstractproperty in typing.py

New submission from hongweipeng : `abc.ababstractproperty` was deprecated since version 3.3. https://docs.python.org/3/library/abc.html#abc.abstractproperty I checked the code and found that only `typing.py` is still used. I created a PR and replaced it with the one written in the documentati

[issue38290] cleanup ababstractproperty in typing.py

Change by hongweipeng : -- keywords: +patch pull_requests: +16011 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16432 ___ Python tracker ___

[issue38290] cleanup ababstractproperty in typing.py

Change by miss-islington : -- pull_requests: +16012 pull_request: https://github.com/python/cpython/pull/16433 ___ Python tracker ___ __

[issue38290] cleanup ababstractproperty in typing.py

Change by Ivan Levkivskyi : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 ___ Python tracker ___ ___

[issue38160] Add a "PyInterpreterState *" field to PyTypeObject.

Petr Viktorin added the comment: > only if PEP 573 makes it *compulsory* for heap types to contain a pointer to > their module And that's impossible without either breaking API (or some hackery). PyType_FromSpec doesn't get the information, and it can be easily outside module initialization.

[issue38269] AMD64 Debian PGO 3.x, AMD64 Clang UBSan 2.7 buildbots: No space left on device

STINNER Victor added the comment: > Can we close this issue? When it's an issue about specific buildbots, I prefer to first check that the buildbot is back to green. > https://buildbot.python.org/all/#/builders/47/builds/3578 AMD64 Debian PGO 3.x buildbot is back to green. > https://buildb

[issue38269] AMD64 Debian PGO 3.x, AMD64 Clang UBSan 2.7 buildbots: No space left on device

Change by STINNER Victor : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue38160] Add a "PyInterpreterState *" field to PyTypeObject.

STINNER Victor added the comment: > No, but it means that a type A *knows* that it was created in interpreter 1 > without relying on the current thread local storage. What's wrong with _PyInterpreterState_GET_UNSAFE()? This macro is based on _Py_atomic_load_relaxed(&_PyRuntime.gilstate.tsta

[issue38234] The value of Py_SetPath is not used to populate the configuration

Change by Kubilay Kocak : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue38174] Security vulnerability in bundled expat CVE-2019-15903 (fix available in expat 2.2.8)

Change by STINNER Victor : -- pull_requests: +16013 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/16434 ___ Python tracker ___ __

[issue37431] test_asyncio: test_start_tls_server_1() failed on ARMv7 Debian buster 3.7

STINNER Victor added the comment: New fail on ARMv7 Debian buster 3.x: https://buildbot.python.org/all/#/builders/176/builds/1356 == ERROR: test_start_tls_server_1 (test.test_asyncio.test_sslproto.SelectorStartTLSTests) -

[issue22107] tempfile module misinterprets access denied error on Windows

And Clover added the comment: Attempting to answer the question "did this open call fail because the path was a directory" by implication from "do we think we ought to be able to write a file to this directory" is IMO doomed. There's no reliable way to determine whether one should be able to

[issue38206] Clarify that tp_dealloc must decref for heap allocated type

Change by miss-islington : -- pull_requests: +16014 pull_request: https://github.com/python/cpython/pull/16436 ___ Python tracker ___ __

[issue38206] Clarify that tp_dealloc must decref for heap allocated type

miss-islington added the comment: New changeset 5faff977adbe089e1f91a5916ccb2160a22dd292 by Miss Islington (bot) (Ammar Askar) in branch 'master': bpo-38206: Clarify tp_dealloc requirements for heap allocated types. (GH-16248) https://github.com/python/cpython/commit/5faff977adbe089e1f91a5916

[issue38206] Clarify that tp_dealloc must decref for heap allocated type

miss-islington added the comment: New changeset 14ddca726a8cd337d0461934374b5e6bf65bf812 by Miss Islington (bot) in branch '3.8': bpo-38206: Clarify tp_dealloc requirements for heap allocated types. (GH-16248) https://github.com/python/cpython/commit/14ddca726a8cd337d0461934374b5e6bf65bf812

[issue38291] Unclear status of the typing.io and typing.re pseudo-modules in docs and runtime

New submission from dgelessus : According to bpo-35089 (and the GitHub issues linked there), the typing.io and typing.re modules should no longer be used. Starting with Python 3.6, the typing documentation no longer mentions the typing.io and typing.re modules, and instead documents their con

[issue38239] test_gdb fails on AMD64 Fedora Stable LTO 3.8 and AMD64 RHEL8 LTO 3.x: Unexpected gdb output

STINNER Victor added the comment: > AMD64 RHEL8 LTO 3.x is green again. I will keep the issue open until all > mentionned buildbots are back to green (when test_gdb pass on these workers). I checked an all buildbots mentioned in this issues are back to green (success). I close the issue. >

[issue38270] Tests: Avoid MD5 or check for MD5 availablity

miss-islington added the comment: New changeset 90558158093c0ad893102158fd3c2dd9f864e82e by Miss Islington (bot) (Christian Heimes) in branch 'master': bpo-38270: More fixes for strict crypto policy (GH-16418) https://github.com/python/cpython/commit/90558158093c0ad893102158fd3c2dd9f864e82e

[issue38292] tkinter variable classes don't link to widget if matplotlib's set_cmap() function is called before the tkinter GUI is instantiated

New submission from Amir Emami : TkInter variable classes don't link to a widget (tested on Checkbutton and Scale) if matplotlib.pyplot.set_cmap() function is called before the tkinter.Tk() call which instantiates the root of a TkInter GUI. There is no problem if it is called after this, thou

[issue22107] tempfile module misinterprets access denied error on Windows

Erik Aronesty added the comment: i would like to point out that the primary reason any of this nonsense exists is because of short filename restrictions. i've replaces nearly all of my temp file creation code in all of my project to `return os.urandom(32).hex()` ... which is reliable secu

[issue38270] Tests: Avoid MD5 or check for MD5 availablity

Change by Christian Heimes : -- pull_requests: +16015 pull_request: https://github.com/python/cpython/pull/16437 ___ Python tracker ___

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Eric Snow added the comment: FWIW, I support reverting the removal of PyThreadState_DeleteCurrent(). We only reverted under the assumption that no one was using this function. Clearly we were mistaken. :) I'll re-open #37878 to revive the discussion about documenting the function (which w

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Eric Snow added the comment: FWIW, when we un-revert we should be sure to move PyThreadState_DeleteCurrent() from Include/pystate.h to Include/cpython/pystate.h. (I suppose that could be done in a separate PR to keep the git history clear.) -- __

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Eric Snow added the comment: s/un-revert/revert/ -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Joannah Nanjekye added the comment: +1 for moving from Include/pystate.h to Include/cpython/pystate.h -- ___ Python tracker ___ ___

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Joannah Nanjekye added the comment: I will handle this later today. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

STINNER Victor added the comment: If we want to make the function "fully public", I suggest to write documentation and have a simple unit test. -- ___ Python tracker ___

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Eric Snow added the comment: I *was* going to suggest that we also put an underscore prefix on the name, but I couldn't think of a reason why we would want to discourage use (other than to reduce the size of the [supported] public API). Moving it to Include/cpython/pystate.h is probably eno

[issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal

Eric Snow added the comment: @Joannah, sounds good. Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()

Eric Snow added the comment: I've re-opened this issue to address the original point: documenting PyThreadState_DeleteCurrent(). FWIW, I don't see a problem with documenting it if we're keeping it around (which it looks like we are). We will address reverting GH-15315 in #38266. --

[issue35886] Move PyInterpreterState into Include/internal/pycore_pystate.h

Eric Snow added the comment: +1 to the suggested "whatsnew" updates. If no one beats me to it I'll work on a PR soon. -- ___ Python tracker ___ _

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

Christian Heimes added the comment: Łukasz, I haven't been able to verify that the last patches are sufficient to prevent Python from segfaulting. We need to wait until rc1 is out. I need a proper release or RPM build to run the tests on our internal test infrastructure. You have to release

[issue38187] test.test_tools.test_c_analyzer fails in refleak mode

Eric Snow added the comment: New changeset 6693f730e0eb77d9453f73a3da33b78a97e996ee by Eric Snow in branch 'master': bpo-38187: Fix a refleak in Tools/c-analyzer. (gh-16304) https://github.com/python/cpython/commit/6693f730e0eb77d9453f73a3da33b78a97e996ee -- ___

[issue38187] test.test_tools.test_c_analyzer fails in refleak mode

Change by Eric Snow : -- assignee: -> eric.snow resolution: -> fixed stage: patch review -> resolved status: open -> pending ___ Python tracker ___ __

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Rainer Keller added the comment: We have been experiencing the same problem with compiling Python-3.7.4 on a system with CentOS 7.6 (aka glib-2.17): Intel Compiler 2019.6 implements stdatomic.h. but lacks the definition of atomic_uintptr_t. >From a configure-point of view just failing to def

[issue13214] Cmd: list available completions from the cmd.Cmd subclass and filter out EOF handler(s)

Kimball Leavitt added the comment: I know that many people do something like: def do_EOF(self, arg): return True to exit the program when you press Ctrl+d. Others might prefer something like ngie https://bugs.python.org/issue13214#msg145856: def do_EOF(self, arg): raise EOFError Th

[issue38293] Deepcopying property objects results in unexpected TypeError

New submission from Guðni Nathan : Currently, attempting to deepcopy a property object will result in an unexpected TypeError: >>> import copy >>> obj = property() >>> new_obj = copy.deepcopy(obj) Traceback (most recent call last): File "", line 1, in File "C:\Program Files\WindowsApps\Py

[issue38293] Deepcopying property objects results in unexpected TypeError

Guðni Nathan added the comment: A small change: The fix should go to Lib/copy.py:198, not line 208. -- ___ Python tracker ___ ___ P

[issue38206] Clarify that tp_dealloc must decref for heap allocated type

Change by Ammar Askar : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue38293] Deepcopying property objects results in unexpected TypeError

Serhiy Storchaka added the comment: But the property object is not atomic. It's attribute __doc__ is writeable. -- nosy: +serhiy.storchaka ___ Python tracker ___ _

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

Pablo Galindo Salgado added the comment: There is this PR that avoids a hard crash in the interpreter: https://github.com/python/cpython/pull/15645 -- ___ Python tracker ___

[issue32820] Add and document __format__ method for IPv[46]Address

Serhiy Storchaka added the comment: New changeset 5d6f5b629394066a5249af25cc01f1a1f0edc138 by Serhiy Storchaka in branch 'master': bpo-32820: Simplify __format__ implementation for ipaddress. (GH-16378) https://github.com/python/cpython/commit/5d6f5b629394066a5249af25cc01f1a1f0edc138 --

[issue38294] re.escape seems to miss some importante regex characters

New submission from Ricardo Bánffy : Under Python 3.6, re.escape escapes "/" In [1]: import re In [2]: re.escape('http://workday.com') Out[2]: 'http\\:\\/\\/workday\\.com' Under 3.7 and 3.8, "/" is not escaped. In [1]: import re In [2]: re.escape('http://workday.com') Out[2]: 'http://workday

[issue38294] re.escape no longer escapes "/" or ":"

Change by Ricardo Bánffy : -- title: re.escape seems to miss some importante regex characters -> re.escape no longer escapes "/" or ":" ___ Python tracker ___ _

[issue38295] macOS Catalina test failures

New submission from Barry A. Warsaw : test_py_compile fails on macOS Catalina beta (19A573a) == ERROR: test_relative_path (test.test_py_compile.PyCompileTestsWithSourceEpoch)

[issue38296] unittest expectedFailure does not differentiate errors from failures

New submission from Kit Choi : I expect the following test to fail, because an "error" is not a "failure". Unexpectedly, the test passes: ``` class TestFailure(unittest.TestCase): @unittest.expectedFailure def test_expected_failure(self): raise TypeError() # for example, a ty

[issue38294] re.escape no longer escapes "/" or ":"

Serhiy Storchaka added the comment: Yes, it is deliberate. "/" and ":" do not have special meaning in regular expressions and do not need escaping. re.escape() now produces more human-readable result and works faster. -- nosy: +serhiy.storchaka __

[issue38293] Deepcopying property objects results in unexpected TypeError

Guðni Nathan added the comment: Function objects are considered "atomic" here and I believe you can also write to their __doc__ (among other attributes). -- ___ Python tracker ___

[issue38297] Imports at top of module is often not used

New submission from Dominic Littlewood <11dlittlew...@gmail.com>: In PEP 8, it is stated that: "Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants." Note the word "always". This advice makes sense because it cut

[issue38298] Base class of generic type has wrong `cls` argument in classmethods

New submission from Kefei Lu : This is a new regression in Python3.7. Create the following file as `test.py` ``` # test.py import typing as t T = t.TypeVar("T") class BaseOfGeneric: @classmethod def f(cls): # when called from an instantiated generic type, e.g., #

[issue38297] Imports at top of module is often not used

Eric V. Smith added the comment: I think PEP 8 should say "Module-level imports are always put at the top of the file, ...". -- nosy: +eric.smith ___ Python tracker ___ _

[issue38293] Deepcopying property objects results in unexpected TypeError

Guðni Nathan added the comment: This bug appears to also affect shallow copies and can be reproduced with the following code: >>> import copy >>> obj = property() >>> copy.copy(obj) Traceback (most recent call last): File "", line 1, in File "C:\Program Files\WindowsApps\PythonSoftwareFo

[issue38294] re.escape no longer escapes "/" or ":"

Ricardo Bánffy added the comment: Thanks for the clarification, Serhiy. Should we update the 3.7 docs to warn others about it? -- ___ Python tracker ___ __

[issue38293] Deepcopying property objects results in unexpected TypeError

Change by Guðni Nathan : -- keywords: +patch pull_requests: +16016 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16438 ___ Python tracker ___

[issue38294] re.escape no longer escapes "/" or ":"

Serhiy Storchaka added the comment: It is already documented. There are even examples which contain "/" and ":". -- ___ Python tracker ___

[issue38299] build errors - latest "git pull"

New submission from Geoge R. Goffe : SUMMARY: AddressSanitizer: 240 byte(s) leaked in 3 allocation(s). -- components: Build files: build-python-3.log messages: 353391 nosy: grgo...@yahoo.com priority: normal severity: normal status: open title: build errors - latest "git pull" type: com

[issue38294] re.escape no longer escapes "/" or ":"

Ricardo Bánffy added the comment: Indeed. It was easy to miss because of the joining and sorting. Being explicit on the 3.7 changes, that '!', '"', '%', "'", ',', '/', ':', ';', '<', '=', '>', '@', '`' were up to 3.6 but are no longer escaped since 3.7, would be nice. --

[issue38300] Documentation says destuction of TemporaryDirectory object will also delete it, but it does not.

New submission from Ian : The documentation found here https://docs.python.org/3.7/library/tempfile.html#tempfile.TemporaryDirectory states the following "On completion of the context or destruction of the temporary directory object the newly created temporary directory and all its contents

[issue38300] Documentation says destuction of TemporaryDirectory object will also delete it, but it does not.

Ammar Askar added the comment: Hmm, I can't recreate this locally: >>> import tempfile >>> import os >>> t = tempfile.TemporaryDirectory() >>> temp_dir = t.name >>> os.path.exists(temp_dir) True >>> del t >>> os.path.exists(temp_dir) False What version of Python are you using? -- nos

[issue37883] threading.Lock.locked is not documented

Change by Ido Michael : -- keywords: +patch pull_requests: +16017 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16420 ___ Python tracker ___

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

STINNER Victor added the comment: New changeset e8650a4f8c7fb76f570d4ca9c1fbe44e91c8dfaa by Victor Stinner (Dong-hee Na) in branch 'master': bpo-38243, xmlrpc.server: Escape the server_title (GH-16373) https://github.com/python/cpython/commit/e8650a4f8c7fb76f570d4ca9c1fbe44e91c8dfaa ---

[issue38294] re.escape no longer escapes "/" or ":"

Change by Ricardo Bánffy : -- assignee: -> docs@python components: +Documentation -Regular Expressions nosy: +docs@python type: behavior -> enhancement ___ Python tracker ___ _

[issue37883] threading.Lock.locked is not documented

Tal Einat added the comment: For future reference, there's a nicer, more concise way to reference PRs: just type GH-16420 (using the relevant PR number). -- nosy: +taleinat ___ Python tracker __

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

Change by miss-islington : -- pull_requests: +16019 pull_request: https://github.com/python/cpython/pull/16440 ___ Python tracker ___ __

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

Change by miss-islington : -- pull_requests: +16018 pull_request: https://github.com/python/cpython/pull/16439 ___ Python tracker ___ __

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

Change by STINNER Victor : -- pull_requests: +16020 pull_request: https://github.com/python/cpython/pull/16441 ___ Python tracker ___ __

[issue38234] The value of Py_SetPath is not used to populate the configuration

STINNER Victor added the comment: Oh, the main issue has been fixed and I added a lot of tests. So I remove the "release blocker" priority. I would like to keep the issue open since I plan to do one more change: use PyWideStringList in _PyPathConfig for module_search_paths to support paths

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

STINNER Victor added the comment: > I haven't been able to verify that the last patches are sufficient to prevent > Python from segfaulting. We need to wait until rc1 is out. I need a proper > release or RPM build to run the tests on our internal test infrastructure. I pushed two fixes in th

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

STINNER Victor added the comment: I remove the "release blocker" priority since the regression has been fixed in Python 3.8. The main "regression" was the addition of the func_clear() function: I removed it. -- priority: release blocker -> ___ Py

[issue38291] Unclear status of the typing.io and typing.re pseudo-modules in docs and runtime

Ivan Levkivskyi added the comment: Guido, what is your final opinion on this? -- nosy: +gvanrossum, levkivskyi ___ Python tracker ___ _

[issue38242] Revert the new asyncio Streams API

Kyle Stanley added the comment: > Andrew, do you want me to submit a PR or you can do it? Since this has been elevated to a release blocker, I wouldn't mind helping to revert this ASAP. I can open a PR to fix it today. -- ___ Python tracker

[issue37883] threading.Lock.locked is not documented

Tal Einat added the comment: Looking at Lib/threading.py and Modules/_threadmodule.c, it actually appears that RLock.locked() is only implemented by the C implementation, but not the Python implementation which is used as a backup. If we're going to make the locked() method more visible by d

[issue38277] Allowing conditions with assignment expressions in comprehensions without parantheses

Change by Terry J. Reedy : -- type: -> enhancement versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list ma

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

miss-islington added the comment: New changeset 39a0c730e31c6941a78da19b6a5b61170687 by Miss Islington (bot) in branch '3.7': bpo-38243, xmlrpc.server: Escape the server_title (GH-16373) https://github.com/python/cpython/commit/39a0c730e31c6941a78da19b6a5b61170687 -- nosy: +

[issue37883] threading.Lock.locked is not documented

Change by Tal Einat : -- Removed message: https://bugs.python.org/msg353402 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38242] Revert the new asyncio Streams API

Yury Selivanov added the comment: > Since this has been elevated to a release blocker, I wouldn't mind helping to > revert this ASAP. I can open a PR to fix it today. Sure, by all means, any help would be hugely appreciated. Thank you, Kyle. You'll need to be careful to only revert the new

[issue37883] threading.Lock.locked is not documented

Change by Tal Einat : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

miss-islington added the comment: New changeset 6447b9f9bd27e1f6b04cef674dd3a7ab27bf4f28 by Miss Islington (bot) in branch '3.8': bpo-38243, xmlrpc.server: Escape the server_title (GH-16373) https://github.com/python/cpython/commit/6447b9f9bd27e1f6b04cef674dd3a7ab27bf4f28 -- __

[issue38280] Feature request: Add support to compile to native binary like as golang

Terry J. Reedy added the comment: The PSF and the core developer group do not have the resources to do this. Pie in the sky proposals like this should be floated on python-list or perhaps python-ideas, where you can get more answers as to 'Why not ...?" or perhaps 'How to ...?". (Several m

[issue38280] Add support to compile to native binary like as with golang

Change by Terry J. Reedy : -- title: Feature request: Add support to compile to native binary like as golang -> Add support to compile to native binary like as with golang ___ Python tracker

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

STINNER Victor added the comment: @Dong-hee Na: Would you mind to try to backport the change to Python 2.7 which also has the bug? -- ___ Python tracker ___ _

[issue38295] macOS Catalina test failures

Change by Terry J. Reedy : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Python 3.7 does not compile type: -> compile error ___ Python tracker __

[issue38295] macOS Catalina test failures

Terry J. Reedy added the comment: This is not a duplicate because Python *did* compile enough to fail a test. -- components: +macOS nosy: +ronaldoussoren, terry.reedy resolution: duplicate -> stage: resolved -> needs patch status: closed -> open superseder: Python 3.7 does not compile

[issue38014] Python 3.7 does not compile

Terry J. Reedy added the comment: #38295 gives error reports for test_py_compile with 3.8, which implies that Python was compiled well enough to run and fail a test. -- nosy: +terry.reedy ___ Python tracker ___

[issue38277] Allowing conditions with assignment expressions in comprehensions without parantheses

Change by Guido van Rossum : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

Neil Schemenauer added the comment: A few comments from the "peanut gallery". Thanks to Victor and Pablo for doing the hard work of investigating this bug. First, it has been a long time since Tim and I first developed gcmodule.c. So, some of my understanding may be inaccurate due to code

[issue38296] unittest expectedFailure does not differentiate errors from failures

Terry J. Reedy added the comment: A function can fail to return an expected object by either returning a wrong object or raising an (unexpected) exception. The assertXyz methods, which ultimately raise AssertionError or something similar, are mostly about catching the first kind of failure,

[issue38294] re.escape no longer escapes "/" or ":"

Change by Roundup Robot : -- keywords: +patch pull_requests: +16021 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16442 ___ Python tracker ___ __

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

STINNER Victor added the comment: > Is the behavior of tp_clear the key to this bug? Once func_clear(my_func) is called, calling my_func() will crash: my_func() is unsuable. Because of a complex dance involving borrowed references, the function is called *after* it's cleared. Pablo's PR 15

[issue38296] unittest expectedFailure does not differentiate errors from failures

Kit Yan Choi added the comment: For your test: class T(unittest.TestCase): def test_f(self): raise TypeError() If you run this test with unittest test runner, you should get this result: E == ERROR: test_f (test_main.T)

[issue38006] Crash in remove() weak reference callback of weakref.WeakValueDictionary at Python exit

STINNER Victor added the comment: > If I understand Victor's test case correctly, the problem is caused if you > have an extension type that implements tp_traverse but not tp_clear and that > there is also a weakref involved in the trash cycle. I'm not sure that "implements tp_traverse but n

[issue38296] unittest expectedFailure does not differentiate errors from failures

Change by Kit Yan Choi : -- nosy: -Kit Choi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds

Gregory P. Smith added the comment: As a note on the general pattern, a user at work diagnosed a ^C problem in their code when running on 2.7 to be due to Queue.get's acquire() try: ... finally: release() Pattern, with the KeyboardInterrupt triggering after acquire() but before the try

[issue38301] If "_REENTARNT" is defined in the header file, we should use "-D_REENTRANT" when compiling

New submission from Jesús Cea Avión : When compiling on Solaris family, we define "_REENTRANT" in "Pyconfig.h". That file is included when compiling C extensions, but if the extension is made of several C files, it could be included only in the file that interfaces with python runtime. Unfor

[issue38301] If "_REENTRANT" is defined in the header file, we should use "-D_REENTRANT" when compiling

Change by Jesús Cea Avión : -- title: If "_REENTARNT" is defined in the header file, we should use "-D_REENTRANT" when compiling -> If "_REENTRANT" is defined in the header file, we should use "-D_REENTRANT" when compiling ___ Python tracker

[issue38242] Revert the new asyncio Streams API

Kyle Stanley added the comment: > You'll need to be careful to only revert the new functions & the > asyncio.Stream class. So far the trickiest part has proven to be the tests (specifically test_streams.py) and keeping the deprecation warning for passing explicit loop arguments. I've had to

[issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py

Dong-hee Na added the comment: Sure! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue38302] __rpow__ not reached when __ipow__ returns NotImplemented

New submission from Adi : Due to shared code between the 2 and 3 forms of pow, the following code causes a TypeError: class A: def __init__(self, val): self.val = val def __ipow__(self, other): return NotImplemented class B: def __init__(self, val): se

[issue38242] Revert the new asyncio Streams API

Kyle Stanley added the comment: Currently focusing on the Lib/asyncio/* and Lib/test/* changes. Working on doc changes next, but that should be significantly easier. In addition to https://github.com/python/cpython/commit/23b4b697e5b6cc897696f9c0288c187d2d24bff2 (main commit from Andrew th

[issue38292] tkinter variable classes don't link to widget if matplotlib's set_cmap() function is called before the tkinter GUI is instantiated

Terry J. Reedy added the comment: You neglected to state the observation that led to the conclusion of 'not linked'. Using 3.8 on Win10, I replaced "plt.set_cmap('x')" with "tk.Tk()". Then, clicking the button prints 'False' even when the checkbutton is checked. After either removing 'tk.

  1   2   >