[issue40275] test.support has way too many imports

Change by hai shi : -- pull_requests: +19993 pull_request: https://github.com/python/cpython/pull/20797 ___ Python tracker ___ ___

[issue31082] reduce takes iterable, not just sequence

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 6.0 -> 7.0 pull_requests: +19992 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20796 ___ Python tracker

[issue40924] Recent importlib change breaks most recent certifi == 2020.4.5.2

Jason R. Coombs added the comment: Thanks for the thorough and considerate response. I do think your original recommendation of reverting the broken feature is the best approach at this point. That is, keep resources.files with the fallback shim and eliminate support for loaders supplying

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

miss-islington added the comment: New changeset e3ce3bba9277a7c4cfde5aaf6269b6c68f334176 by Miss Islington (bot) in branch '3.9': bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769) https://github.com/python/cpython/commit/e3ce3bba9277a7c4cfde5aaf6269b6c68f334176

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +19991 pull_request: https://github.com/python/cpython/pull/20795 ___ Python tracker

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Pablo Galindo Salgado added the comment: New changeset 896f4cf63f9ab93e30572d879a5719d5aa2499fb by Lysandros Nikolaou in branch 'master': bpo-40847: Consider a line with only a LINECONT a blank line (GH-20769) https://github.com/python/cpython/commit/896f4cf63f9ab93e30572d879a5719d5aa2499fb

[issue40275] test.support has way too many imports

STINNER Victor added the comment: New changeset 7f888c7ef905842bf7739cc03bd20398329951b5 by Hai Shi in branch 'master': bpo-40275: Add import_helper submodule in test.support (GH-20794) https://github.com/python/cpython/commit/7f888c7ef905842bf7739cc03bd20398329951b5 --

[issue40924] Recent importlib change breaks most recent certifi == 2020.4.5.2

Łukasz Langa added the comment: I thought about this all day. Given the scope of the change you made I think no option looks ideal. If we revert the entire feature, it's a big bummer for everybody involved and it might be an overreaction. If we keep the feature at the state of Beta 1, it

[issue40878] Use c99 on the aixtools bot

Stefan Krah added the comment: So it would still be interesting to see what happens if you compile libmpdec with c99_r (emphasis mine): """ This command supports all ISO C99 language features, but does not support IBM language extensions. Use this invocation for *strict* conformance to the

[issue40878] Use c99 on the aixtools bot

Stefan Krah added the comment: Thanks for this information. The buildbot, however, fails to compile C99 extern inline functions. Example: ld: 0711-317 ERROR: Undefined symbol: .mpd_issnan I understand the C99 extern inline feature like in this explanation:

[issue29847] Path takes and ignores **kwargs

Change by Rémi Lapeyre : -- versions: +Python 3.10, Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39385] Add an assertNoLogs context manager to unittest TestCase

Change by Rémi Lapeyre : -- versions: +Python 3.10 -Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40902] Speed up PEG parser by using operator precedence for binary operators

Change by Pablo Galindo Salgado : -- resolution: -> postponed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue40902] Speed up PEG parser by using operator precedence for binary operators

Change by Pablo Galindo Salgado : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue40680] thread_cputime isn't supported by AIX5

STINNER Victor added the comment: According to https://www.ibm.com/support/pages/aix-support-lifecycle-information I suggest to require AIX 7.1 and newer. -- ___ Python tracker

[issue40680] thread_cputime isn't supported by AIX5

STINNER Victor added the comment: AIX 5 was released 16 years ago, do you we really care? -- ___ Python tracker ___ ___

[issue40275] test.support has way too many imports

Change by hai shi : -- pull_requests: +19990 pull_request: https://github.com/python/cpython/pull/20794 ___ Python tracker ___ ___

[issue30064] BaseSelectorEventLoop.sock_{recv, sendall}() don't remove their callbacks when canceled

Fantix King added the comment: I'm checking now -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

Change by Antoine Pitrou : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

miss-islington added the comment: New changeset 972aba86ede0bf254e16a760639a1ff8df298578 by Antoine Pitrou in branch '3.8': [3.8] bpo-40895: Update weakref documentation to remove old warnings (GH-20687) (GH-20792)

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

miss-islington added the comment: New changeset 049039832da3d02592d680cebf71ab8a665a6564 by Antoine Pitrou in branch '3.7': [3.7] bpo-40895: Update weakref documentation to remove old warnings (GH-20687) (GH-20793)

[issue40680] thread_cputime isn't supported by AIX5

Batuhan Taskaya added the comment: @vstinner what are your thoughts on this? I can propose a patch that introduces a build value to generate this conditionally depending on if the system has it or not. But I am not sure about if our motivation behind this is going to be supporting (very)

[issue40906] Unable to import module due to python unable to resolve dependecies

Steve Dower added the comment: add_dll_directory can be safely used within your library, so if you have any .py files that will be imported first (such as your package __init__.py), you can add it then. The safest way is to use something like: with os.add_dll_directory(THE_DIR): import

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

miss-islington added the comment: New changeset 18e07ba931c68eb5ab5262d4e57fe58c302686de by Miss Islington (bot) in branch '3.9': bpo-40895: Update weakref documentation to remove old warnings (GH-20687) https://github.com/python/cpython/commit/18e07ba931c68eb5ab5262d4e57fe58c302686de

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

Change by Antoine Pitrou : -- pull_requests: +19989 pull_request: https://github.com/python/cpython/pull/20793 ___ Python tracker ___

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

Change by Antoine Pitrou : -- nosy: +pitrou nosy_count: 3.0 -> 4.0 pull_requests: +19988 pull_request: https://github.com/python/cpython/pull/20792 ___ Python tracker ___

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

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

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

miss-islington added the comment: New changeset 1642c0ef750f96664a98cadb09301d492098d2fb by Daniel Fortunov in branch 'master': bpo-40895: Update weakref documentation to remove old warnings (GH-20687) https://github.com/python/cpython/commit/1642c0ef750f96664a98cadb09301d492098d2fb

[issue30064] BaseSelectorEventLoop.sock_{recv, sendall}() don't remove their callbacks when canceled

STINNER Victor added the comment: Another kind of failure on x86 Gentoo Installed with X 3.x: https://buildbot.python.org/all/#/builders/128/builds/1030 ERROR: test_sock_client_racing (test.test_asyncio.test_sock_lowlevel.EPollEventLoopTests)

[issue40680] thread_cputime isn't supported by AIX5

Michael Felt added the comment: No, it is not supported - asin there are no new patches - but there are organizations that use it. imho - those organizations are not likely to be using the latest Python - but I have been packaging Python on AIX 5.3 and AIX 6.1 - as these packages run

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

STINNER Victor added the comment: > Why doesn't SuppressCrashReport suppress the hard error dialog (i.e. > SEM_FAILCRITICALERRORS)? This dialog gets created by the NtRaiseHardError > system call. Would you mind to open a separated issue? -- ___

[issue40878] Use c99 on the aixtools bot

Michael Felt added the comment: Actually, iirc - xlc is c99 plus a few extra settings. The configuration files for xlc are, traditionally, in /etc (the later versions of the compiler have moved them into /opt/show/where so that multiple versions of the compiler can be installed.

[issue40945] TKinter.Tk.geometry(Tk.winfo_geometry()) should be idempotent

Change by Ben Li-Sauerwine : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40945] TKinter.Tk.geometry(Tk.winfo_geometry()) should be idempotent

New submission from Ben Li-Sauerwine : One would expect that calling TKinter.Tk.geometry(tk.winfo_geometry()) would be idempotent. However, based on the system window frame, it is not and doing so moves the window down the screen. Running the example below reproduces the issue. --

[issue40913] time.sleep ignores errors on Windows

Eryk Sun added the comment: > is there any straightforward way to cause WaitForSingleObjectEx to fail? The wait can fail for ERROR_INVALID_HANDLE or ERROR_ACCESS_DENIED (i.e. the handle lacks SYNCHRONIZE access). If _PyOS_SigintEvent were replaced with get/set functions, then a non-waitable

[issue40944] email.message.EmailMessage address parser fails to handle 'example@'

Change by Roundup Robot : -- keywords: +patch nosy: +python-dev nosy_count: 3.0 -> 4.0 pull_requests: +19985 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20790 ___ Python tracker

[issue40944] email.message.EmailMessage address parser fails to handle 'example@'

New submission from Ivan Savin : How to reproduce: >>> import email.message >>> message = email.message.EmailMessage() >>> message['From'] = 'hey@' Traceback (most recent call last): File "/home/ivan/.pyenv/versions/3.9.0a5/lib/python3.9/email/_header_value_parser.py", line 1956, in

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

Eryk Sun added the comment: Why doesn't SuppressCrashReport suppress the hard error dialog (i.e. SEM_FAILCRITICALERRORS)? This dialog gets created by the NtRaiseHardError system call. For example: >>> NtRaiseHardError = ctypes.windll.ntdll.NtRaiseHardError >>> response =

[issue40847] New parser considers empty line following a backslash to be a syntax error, old parser didn't

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40927] ./python -m test test___all__ test_binhex fails

STINNER Victor added the comment: Rémi Lapeyre: Thanks for the bug report, it's now fixed! -- versions: +Python 3.9 ___ Python tracker ___

[issue40927] ./python -m test test___all__ test_binhex fails

STINNER Victor added the comment: New changeset af6932575391bca10f4f2145b56e3edbe9765343 by Victor Stinner in branch '3.9': bpo-40927: Fix test_binhex when run twice (GH-20764) (GH-20789) https://github.com/python/cpython/commit/af6932575391bca10f4f2145b56e3edbe9765343 --

[issue39679] functools: singledispatchmethod doesn't work with classmethod

Viktor Roytman added the comment: Sorry to bump this after months of inactivity but is there something I need to do here? -- ___ Python tracker ___

[issue39465] [subinterpreters] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

STINNER Victor added the comment: New changeset 1bcc32f0620d2e99649a6d423284d9496b7b3548 by Victor Stinner in branch 'master': bpo-39465: Use _PyInterpreterState_GET() (GH-20788) https://github.com/python/cpython/commit/1bcc32f0620d2e99649a6d423284d9496b7b3548 --

[issue40927] ./python -m test test___all__ test_binhex fails

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

[issue40927] ./python -m test test___all__ test_binhex fails

STINNER Victor added the comment: New changeset 9c24e2e4c10705d95258558348417a28007dac66 by Victor Stinner in branch 'master': bpo-40927: Fix test_binhex when run twice (GH-20764) https://github.com/python/cpython/commit/9c24e2e4c10705d95258558348417a28007dac66 --

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

STINNER Victor added the comment: New changeset c7a6c7b5279f766e65b7cc9dc5bebb73acee6672 by Victor Stinner in branch '3.8': bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779) (GH-20785) (GH-20787)

[issue39465] [subinterpreters] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

STINNER Victor added the comment: New changeset 4a4f660cfde8b683634c53e6214a6baa51de43b1 by Victor Stinner in branch '3.9': bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779) (GH-20785) https://github.com/python/cpython/commit/4a4f660cfde8b683634c53e6214a6baa51de43b1

[issue40913] time.sleep ignores errors on Windows

Tim Golden added the comment: Thinking about testing here.. is there any straightforward way to cause WaitForSingleObjectEx to fail? The code change would be fairly slight and amenable to inspection, but it would be good to actually test it ;) --

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

STINNER Victor added the comment: Thanks for the bug report David Bolen and thanks for the analysis Eryk Sun. The bug should be be fixed in the master branch, and backports to 3.8 and 3.9 are coming. -- ___ Python tracker

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

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

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

STINNER Victor added the comment: New changeset f6e58aefde2e57e4cb11ea7743955da53a3f1e80 by Victor Stinner in branch 'master': bpo-40826: Fix test_repl.test_close_stdin() on Windows (GH-20779) https://github.com/python/cpython/commit/f6e58aefde2e57e4cb11ea7743955da53a3f1e80 --

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() "#" formats when PY_SSIZE_T_CLEAN is not defined

Change by STINNER Victor : -- title: PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined -> PEP 353: Drop support for PyArg_ParseTuple() "#" formats when PY_SSIZE_T_CLEAN is not defined ___ Python tracker

[issue27499] PY_SSIZE_T_CLEAN conflicts with Py_LIMITED_API

STINNER Victor added the comment: See also bpo-40943: PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined. -- ___ Python tracker ___

[issue27499] PY_SSIZE_T_CLEAN conflicts with Py_LIMITED_API

STINNER Victor added the comment: > Oh, I can avoid this problem by setting Py_LIMITED_API to 0x3030 or > greater. Hum, maybe the behavior is different because of the following code in Include/modsupport.h: /* Due to a glitch in 3.2, the _SizeT versions weren't exported from the DLL.

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

Stefan Behnel added the comment: New changeset 9419158a3e67ba2eadf33215568003ed723b0a98 by Miss Islington (bot) in branch '3.9': bpo-40703: Let PyType_FromSpec() set "type.__module__" only if it is not set yet. (GH-20273) (GH-20782)

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

Change by Stefan Behnel : -- stage: patch review -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

STINNER Victor added the comment: I started to write a long rationale to explain why "#" variants of formats must be deprecated, before I noticed that they are already deprecated! To not lost it, here is my rationale :-) The C code base of Python switched from int to Py_ssize_t with PEP

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

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

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

STINNER Victor added the comment: New changeset d36cf5f1d20ce9f111a8fc997104785086e8eee6 by Victor Stinner in branch 'master': bpo-40943: Replace PY_FORMAT_SIZE_T with "z" (GH-20781) https://github.com/python/cpython/commit/d36cf5f1d20ce9f111a8fc997104785086e8eee6 --

[issue40925] Remove redundant macros used for stack manipulation in interpreter

Change by Dong-hee Na : -- keywords: +patch pull_requests: +19979 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/20783 ___ Python tracker

[issue40943] PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

Change by STINNER Victor : -- title: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined -> PEP 353: Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined ___ Python tracker

[issue40925] Remove redundant macros used for stack manipulation in interpreter

Dong-hee Na added the comment: AFAIK, SET_VALUE is not used in CPython master codebase. -- ___ Python tracker ___ ___

[issue40925] Remove redundant macros used for stack manipulation in interpreter

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +19977 pull_request: https://github.com/python/cpython/pull/20782 ___ Python tracker

[issue40943] Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

New submission from STINNER Victor : Follow-up of bpo-36381: In Python 3.8, PyArg_ParseTuple() and Py_BuildValue() formats using "int" when PY_SSIZE_T_CLEAN is not defined, but Py_ssize_t when PY_SSIZE_T_CLEAN is defined, were deprecated by: commit d3c72a223a5f771f964fc34557c55eb5bfa0f5a0

[issue40943] Drop support for PyArg_ParseTuple() format when PY_SSIZE_T_CLEAN is not defined

Change by STINNER Victor : -- keywords: +patch pull_requests: +19978 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20781 ___ Python tracker ___

[issue40703] PyType_FromSpec*() overwrites the type's "__module__"

Stefan Behnel added the comment: New changeset 24b8bad6d30ae4fb37ee686a073adfa5308659f9 by scoder in branch 'master': bpo-40703: Let PyType_FromSpec() set "type.__module__" only if it is not set yet. (GH-20273)

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Stefan Krah added the comment: > The first warning line in the initial message of this bug report tries to > allocate 872 petabyte. Yes, that's for systems like Linux where you never know what overallocation is going to permit and subsequently freeze the system. Special casing malloc()

[issue36543] Remove old-deprecated ElementTree features (part 2)

Stefan Behnel added the comment: The xml.etree.cElementTree module is restored. We'll see about what to do with it later. It hurts less to keep it around than to delete it. I think this ticket can be closed. -- resolution: -> fixed stage: patch review -> resolved status: open ->

[issue36543] Remove old-deprecated ElementTree features (part 2)

Stefan Behnel added the comment: New changeset 3b97d1becbe08cf56c58d9c740a4622cbf6285fd by Miss Islington (bot) in branch '3.9': bpo-36543: Revert "bpo-36543: Remove the xml.etree.cElementTree module." (GH-20117) (GH-20780)

[issue40942] BaseManager cannot start with local manager

New submission from Mike Jarvis : I had a function for making a logger proxy that could be safely passed to multiprocessing workers and log back to the main logger with essentially the following code: ``` import logging from multiprocessing.managers import BaseManager class SimpleGenerator:

[issue36543] Remove old-deprecated ElementTree features (part 2)

Change by miss-islington : -- nosy: +miss-islington nosy_count: 6.0 -> 7.0 pull_requests: +19976 pull_request: https://github.com/python/cpython/pull/20780 ___ Python tracker

[issue36543] Remove old-deprecated ElementTree features (part 2)

Stefan Behnel added the comment: New changeset ec88e1bca81a167e6d5c0ac635e22f84298cb1df by Serhiy Storchaka in branch 'master': bpo-36543: Revert "bpo-36543: Remove the xml.etree.cElementTree module." (GH-20117)

[issue40940] How to update pip permanently for new venv?

Change by Zachary Ware : -- components: +Library (Lib) -asyncio nosy: +vinay.sajip -asvetlov, yselivanov ___ Python tracker ___ ___

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Ronald Oussoren added the comment: I've filed a report with Apple about this (FB7731971), even though I expect that this behaviour will not change. That's something we should have done years ago. BTW. The link to malloc_print_configure that Victor shared seems to indicate that the default

[issue40562] SEO: differentiate between Python 2 and Python 3 docs on Google SERP

Pinto added the comment: I have the same problem on my site https://lesmarketing.fr I deactivated the breadcrumbs, you have found a solution ? -- nosy: +khaled ___ Python tracker

[issue17013] Allow waiting on a mock

Ilya Kulakov added the comment: > That is not true, is actually encouraged to check for singletons like True, > False and None. You're right, just never used it as I never needed an identity check against True / False The PR is re-done to use an additional property call_event instead of

[issue39666] IDLE: Factor out similar code in editor and hyperparser

Terry J. Reedy added the comment: The quote from #32989 is from my msg313179, msg313179. There are two levels of duplication. First, between Hyperparser and EditorWindow. Second between editor and shell branches. While I said before to resolve the first with an EditorWindow method, as

[issue40826] PyOS_InterruptOccurred() now requires to hold the GIL: PyOS_Readline() crash

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

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Stefan Krah added the comment: And indeed, with the new decimal MAX_PREC feature, you should see the misguided diagnostic as well on OS X: >>> from decimal import * >>> >>> c = getcontext() >>> c.prec = MAX_PREC >>> Decimal(4).sqrt() Decimal('2') >>> So it is real code, but extremely

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Stefan Krah added the comment: But if malloc_print_configure() is not a public API, it should probably not be used. -- ___ Python tracker ___

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Stefan Krah added the comment: No, it does not cause real issues. Adding this feature would just suppress chatty diagnostics like this one, which are a bit unfriendly: >>> [0] * 1 python3(36633,0x110c08dc0) malloc: can't allocate region :***

[issue17013] Allow waiting on a mock

Ilya Kulakov added the comment: As far as I understand it introduces 3 methods that may clash. It's unlikely but (I speculate) is still more likely than an identity check with called. That being said, the PR can be redone as a subclass. But that implementation will not play as nicely with

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Ronald Oussoren added the comment: I'm not sure if it is worthwhile to tweak CPython to work around this misfeature of libc on macOS (and likely iOS). Is this something that causes issues in real code, or just in the test suite? Looking at this particular test is seems to use a context

[issue36439] Inconsistencies with datetime.fromtimestamp(t) when t < 0

Paul Anton Letnes added the comment: I've encountered an issue on anaconda python on windows 10 v1909 which I suspect is related. It looks like no dates in 1970 can be converted to datetime.timestamp(): Python 3.8.2 (default, Apr 14 2020, 19:01:40) [MSC v.1916 64 bit (AMD64)] Type

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Rémi Lapeyre added the comment: > But is it really an use case to log any memory allocation failure? Python is > very likely to raise a MemoryError exception in this case. It's well defined, > no? Yes, we are not trying to log the allocation failure, we are just trying to suppress a dubious

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

STINNER Victor added the comment: > Would it be possible to wrap malloc_print_configure() > (https://github.com/PureDarwin/libmalloc/blob/e37056265821cd6e014ab911d9fe3b9d0da88e22/src/malloc_printf.c#L59) > in a context manager that we put in test.support? or to override >

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

STINNER Victor added the comment: > Ok, I will try to do this in the coming days. Is adding this kind of super > ugly, super specific code to pymain_init() ok? Maybe _PyPreConfig_Write() would be a better place. There is a very little risk that memory allocation done before

[issue17013] Allow waiting on a mock

Pablo Galindo Salgado added the comment: > Current implementation relies on that: Notice that this is a clear disadvantage over a subclass-based approach, which is backwards compatible and preserves the semantics of mock. -- ___ Python tracker

[issue40941] Merge generator.gi_running and frame executing flag into single frame state

New submission from Mark Shannon : Generators have a "gi_running" attribute (coroutines have an equivalent cr_running flag). Internally frame also has an executing flag. We use these, plus the test `f_stacktop pointer == NULL`, to determine what state a generator or frame is in. It would be

[issue17013] Allow waiting on a mock

Pablo Galindo Salgado added the comment: > 1. called is almost never used in practice (people just use .assert*) Sorry but saying "almost never used" is not good enough. Not only because you hold incomplete data but because backwards compatibility is mainly binary: it breaks or it does not,

[issue17013] Allow waiting on a mock

Ilya Kulakov added the comment: > Unfortunately, we take backwards compatibility very seriously in the core > team and this is a big downside of this proposal. Current implementation relies on that: 1. called is almost never used in practice (people just use .assert*) 2. The is True / False

[issue40928] OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

Stefan Krah added the comment: Changing the title to get more input from others. -- title: test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS -> OS X: malloc(): set default diagnostics to DEBUG_WRITE_ON_CRASH

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: I would probably put all that code in a separate function like init_darwin_libc(), and call init_darwin_libc() in pymain_init(). The real fun will start when we figure out which OS X versions support this feature. I hope we have a buildbot for each. :-)

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Rémi Lapeyre added the comment: Ok, I will try to do this in the coming days. Is adding this kind of super ugly, super specific code to pymain_init() ok? -- ___ Python tracker

[issue40928] test_decimal.CWhitebox.test_maxcontext_exact_arith() shows "malloc: can't allocate region" on MacOS

Stefan Krah added the comment: > What about overriding the default to DEBUG_WRITE_ON_CRASH if > MallocDebugReport is not set? That sounds like a very good compromise! -- ___ Python tracker

  1   2   >