[issue37242] sub-process would be terminated when registered finalizer are working

New submission from mrqianjinsi : Hi guys. I'm using multiprocessing module to accelerate my program. and I want to do some cleanup work when sub-process exit. but I found that sub-process would be terminated when registered finalizer are working. Is this behavior designed intentionally? co

[issue37242] sub-process would be terminated when registered finalizers are working

Change by mrqianjinsi : -- title: sub-process would be terminated when registered finalizer are working -> sub-process would be terminated when registered finalizers are working ___ Python tracker

[issue37221] PyCode_New API change breaks backwards compatibility policy

Pablo Galindo Salgado added the comment: Adding Petr, that was involved with the "tp_print" to "tp_vectorcall" renaming. -- nosy: +petr.viktorin ___ Python tracker ___ ___

[issue37087] Adding native id support for openbsd

Change by Michael Felt : -- pull_requests: +13872 pull_request: https://github.com/python/cpython/pull/13624 ___ Python tracker ___

[issue37221] PyCode_New API change breaks backwards compatibility policy

Jeroen Demeyer added the comment: Technically, tp_print was replaced by tp_vectorcall_offset. But that doesn't answer the question how we should deal with tp_print backwards compatibility. Cython does FooType.tp_print = 0; With this in mind, simply replacing tp_print by tp_vectorcall_offset

[issue37221] PyCode_New API change breaks backwards compatibility policy

Change by Jeroen Demeyer : -- keywords: +patch pull_requests: +13873 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/14009 ___ Python tracker __

[issue37221] PyCode_New API change breaks backwards compatibility policy

Jeroen Demeyer added the comment: PR 14009 deals with tp_print -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue37243] test_sendfile in asyncio crashes when os.sendfile() is not supported

New submission from Michael Felt : issue34655 added sendfile support to asyncio. However, the `test_sendfile` fails when called if there is no os.sendfile support. This patch will skip the test when @unittest.skipUnless(hasattr(os, 'sendfile'), 'test needs os.sendfile()') -- message

[issue26219] implement per-opcode cache in ceval

STINNER Victor added the comment: New changeset 996e52623af3854552d41751e0c2522bc0a7e84f by Victor Stinner (Miss Islington (bot)) in branch '3.8': bpo-26219: Fix compiler warning in _PyCode_InitOpcache() (GH-13997) (GH-14000) https://github.com/python/cpython/commit/996e52623af3854552d41751e0

[issue37242] sub-process would be terminated when registered finalizers are still running

Change by mrqianjinsi : -- title: sub-process would be terminated when registered finalizers are working -> sub-process would be terminated when registered finalizers are still running ___ Python tracker _

[issue37243] test_sendfile in asyncio crashes when os.sendfile() is not supported

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

[issue37226] Asyncio Fatal Error on SSL Transport - IndexError Deque Index Out Of Range

Ben Brown added the comment: I have created a minimal example if that helps to show the issue https://gist.github.com/bobthemac/031213b8e37960ee805f2ae1e6990b60 -- ___ Python tracker ___

[issue37226] Asyncio Fatal Error on SSL Transport - IndexError Deque Index Out Of Range

Andrew Svetlov added the comment: Thank you! Yuri, you might be interested too -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue35545] asyncio.base_events.create_connection doesn't handle scoped IPv6 addresses

Change by Michael Felt : -- pull_requests: +13875 pull_request: https://github.com/python/cpython/pull/14011 ___ Python tracker ___

[issue37221] PyCode_New API change breaks backwards compatibility policy

STINNER Victor added the comment: > Note that PyCode_New() is not the only change in 3.8 beta1 that breaks Cython > generated code. The renaming of "tp_print" to "tp_vectorcall" is equally > disruptive, because Cython has (or had) a work-around for CPython > (mis-)behaviour that reset the fi

[issue37087] Adding native id support for openbsd

Change by STINNER Victor : -- pull_requests: -13872 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue37111] Logging - Inconsistent behaviour when handling unicode

Inada Naoki added the comment: Hmm,, about encoding, I agree that default encoding of open() should be used. If we change it, encoding of log files are changed unexpectedly after upgrading Python. On the other hand, couldn't we use different default error handler? "replace" or "backslashescap

[issue36888] Create a way to check that the parent process is alive for deamonized processes

STINNER Victor added the comment: This new test is not reliable, it failed on x86 Gentoo Refleaks 3.8: https://buildbot.python.org/all/#/builders/223/builds/9 Please fix the test or revert the change. The CI must remain green ;-) running: test_multiprocessing_spawn (31 min 51 sec), test_mul

[issue37244] test_multiprocessing_forkserver: test_resource_tracker() failed on x86 Gentoo Refleaks 3.8

New submission from STINNER Victor : x86 Gentoo Refleaks 3.8: https://buildbot.python.org/all/#/builders/223/builds/9 3:22:46 load avg: 5.83 [423/423/2] test_multiprocessing_forkserver failed (5 min 10 sec) beginning 6 repetitions 123456 ./buildbot/buildarea/cpython/3.8.ware-gentoo-x86.refleak

[issue36867] Make semaphore_tracker track other system resources

STINNER Victor added the comment: The new test is not reliable, see: bpo-37244 "test_multiprocessing_forkserver: test_resource_tracker() failed on x86 Gentoo Refleaks 3.8". -- ___ Python tracker __

[issue37244] test_multiprocessing_forkserver: test_resource_tracker() failed on x86 Gentoo Refleaks 3.8

Change by STINNER Victor : -- nosy: +pablogsal, pierreglaser, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue9665] Buid issues on Cygwin - _curses, _curses_panel, and _io

Erik Bray added the comment: I think this issue can probably be closed. It refers to a very old version of Cygwin as well as old versions of Python. I don't have any problem building the _curses or _io modules on recent versions of Cygwin (>=2.9) and with current cpython master (3.9.0a0).

[issue31829] Portability issues with pickle

miss-islington added the comment: New changeset d561f848b235f2011a43b705d112055b92fa2366 by Miss Islington (bot) in branch '3.7': bpo-31829: Make protocol 0 pickles be loadable in text mode in Python 2. (GH-11859) https://github.com/python/cpython/commit/d561f848b235f2011a43b705d112055b92fa2

[issue37245] Azure Pipeline: sick macOS job on Python 3.8?

New submission from STINNER Victor : I backported a change to 3.8: https://github.com/python/cpython/pull/14000 The macOS job of Azure Pipelines failed badly: https://dev.azure.com/Python/cpython/_build/results?buildId=45071&view=results * test_importlib/test_locks.py: test_deadlock() => TIMEO

[issue37245] Azure Pipeline: sick macOS job on Python 3.8?

STINNER Victor added the comment: os.uname: posix.uname_result(sysname='Darwin', nodename='Mac-483.local', release='17.7.0', version='Darwin Kernel Version 17.7.0: Wed Apr 24 21:17:24 PDT 2019; root:xnu-4570.71.45~1/RELEASE_X86_64', machine='x86_64') -- _

[issue37246] http.cookiejar.DefaultCookiePolicy should use current timestamp instead of last updated timestamp value for checking expiry

New submission from Karthikeyan Singaravelan : In http.cookiejar module's DefaultCookiePolicy checking for cookie expiry uses the last updated value for _now [0] which is in three actions below. So if the cookies are extracted using the policy and the policy is used for expiry check later it

[issue28869] __module__ attribute is not set correctly for a class created by direct metaclass call

Alejandro Gonzalez added the comment: >I think we can proceed with option A, but only if doesn't cause visible >slow-down for creating ABCs (which is already slower that normal classes). >TBH, I don't want to document A as "official" recipe (maybe however mention >the problem in the `pickle`

[issue35545] asyncio.base_events.create_connection doesn't handle scoped IPv6 addresses

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

[issue35545] asyncio.base_events.create_connection doesn't handle scoped IPv6 addresses

miss-islington added the comment: New changeset 32dda263e4e8c8e0fadc2bb29b9856e2f177dde9 by Miss Islington (bot) (Michael Felt) in branch 'master': bpo-35545: Skip `test_asyncio.test_create_connection_ipv6_scope` on AIX (GH-14011) https://github.com/python/cpython/commit/32dda263e4e8c8e0fadc

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

New submission from Jeroen van den Hout : Currently when building an extension which lists a SWIG interface (.i) file as a source file, SWIG creates the files correctly in the build_ext command. Unfortunately this command is run after the build_py command, so the python files (.py) created in

[issue37248] support conversion of `func(**{} if a else b)`

Change by Shen Han : -- components: 2to3 (2.x to 3.x conversion tool) nosy: Shen Han priority: normal severity: normal status: open title: support conversion of `func(**{} if a else b)` type: enhancement versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9 _

[issue28459] _pyio module broken on Cygwin / setmode not usable

Change by Erik Bray : -- pull_requests: +13877 pull_request: https://github.com/python/cpython/pull/14013 ___ Python tracker ___ ___

[issue35545] asyncio.base_events.create_connection doesn't handle scoped IPv6 addresses

miss-islington added the comment: New changeset 70a4178ec47154fdcc3ff06c13149e178d014581 by Miss Islington (bot) in branch '3.8': bpo-35545: Skip `test_asyncio.test_create_connection_ipv6_scope` on AIX (GH-14011) https://github.com/python/cpython/commit/70a4178ec47154fdcc3ff06c13149e178d0145

[issue28869] __module__ attribute is not set correctly for a class created by direct metaclass call

Ivan Levkivskyi added the comment: > Perhaps adding some section like "Notes on pickling dynamically-defined > classes" in the `pickle` module would be more appropriate? I think just a note with few sentences would be enough. -- ___ Python tracker

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

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

[issue37247] swap distutils build_ext and build_py commands to allow proper SWIG extension installation

Jeroen Demeyer added the comment: > SWIG creates the files correctly in the build_ext command One could argue that running SWIG should be an entirely different step, not part of build_ext. I'm afraid that your idea of swapping build_ext and build_py will be rejected because it has a high ch

[issue37221] PyCode_New API change breaks backwards compatibility policy

Jeroen Demeyer added the comment: I think that the PyCode_New() compatibility problem and tp_print are sufficiently closely related that they can be discussed together. In any case, I agree that it makes little sense to fix just one. -- ___ Python

[issue26110] Speedup method calls 1.2x

Jeroen Demeyer added the comment: Note that this idea has been generalized by PEP 590: any type can support this optimization by setting the Py_TPFLAGS_METHOD_DESCRIPTOR flag. -- nosy: +jdemeyer ___ Python tracker

[issue37249] Missing declaration of _PyObject_GetMethod

New submission from Jeroen Demeyer : The function _PyObject_GetMethod is internal and private, but it should still be declared properly. Currently, it is "manually" declared in two .c files where it's used. -- components: Interpreter Core messages: 345336 nosy: jdemeyer priority: norm

[issue37249] Missing declaration of _PyObject_GetMethod

Change by Jeroen Demeyer : -- nosy: +yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue37249] Missing declaration of _PyObject_GetMethod

Change by Jeroen Demeyer : -- keywords: +patch pull_requests: +13879 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14015 ___ Python tracker ___ _

[issue37250] C files generated by Cython set tp_print to NULL

New submission from STINNER Victor : Copy of Stefan Behnel's msg345305 in bpo-37221: """ Note that PyCode_New() is not the only change in 3.8 beta1 that breaks Cython generated code. The renaming of "tp_print" to "tp_vectorcall" is equally disruptive, because Cython has (or had) a work-around

[issue37221] PyCode_New API change breaks backwards compatibility policy

STINNER Victor added the comment: Jeroen Demeyer: > I think that the PyCode_New() compatibility problem and tp_print are > sufficiently closely related that they can be discussed together. IMHO these problems are different enough to justify to have a separated issue: I created https://bugs.p

[issue37250] C files generated by Cython set tp_print to NULL

Change by Jeroen Demeyer : -- keywords: +patch pull_requests: +13880 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14009 ___ Python tracker ___ _

[issue32388] Remove cross-version binary compatibility

STINNER Victor added the comment: About ABI "foward compatibility", Python 3.8 introduced another backward incompatible change: bpo-37250 "C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset". -- ___

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Change by STINNER Victor : -- title: C files generated by Cython set tp_print to NULL -> C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset ___ Python tracker

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: "printfunc tp_print;" has been replaced with "Py_ssize_t tp_vectorcall_offset;": the type was basically a pointer and has been replaced with an integer. With "#define tp_print tp_vectorcall", "type->tp_print = NULL;" becomes "type->tp_vectorcall = NULL;".

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: Actually, Cython generates code setting tp_print to 0 (not NULL). -- nosy: +jdemeyer ___ Python tracker ___ _

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: inherit_slots() uses: /* Inherit tp_vectorcall_offset only if tp_call is not overridden */ if (!type->tp_call) { COPYSLOT(tp_vectorcall_offset); } PyType_Ready() contains the following assertion: /* Consistency checks

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > If -Werror is used, "type->tp_vectorcall = NULL;" would fail with a > compilation error, since NULL is not exactly an integer, no? No because tp_vectorcall is a function pointer. You're confusing with tp_vectorcall_offset which is an integer. --

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: IMHO the simplest and safest option for this issue is to revert tp_print removal and move tp_vectorcall_offset at the end of PyTypeObject. Is PEP 590 fully public in Python 3.8? It seems like _Py_TPFLAGS_HAVE_VECTORCALL at least is private. Maybe we can att

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Change by STINNER Victor : -- nosy: +petr.viktorin, scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: > No because tp_vectorcall is a function pointer. You're confusing with > tp_vectorcall_offset which is an integer. Oh. I didn't notice that your PR makes tp_print an alias to tp_vectorcall rather than tp_vectorcall_offset. Ok. -- _

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: If we decide to not reintroduce tp_print, tp_print removal must be documented at: https://docs.python.org/dev/whatsnew/3.8.html#changes-in-the-c-api -- ___ Python tracker _

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > I understand that tp_vectorcall_offset=0 is fine and the expected value for a > type which doesn't have the flag _Py_TPFLAGS_HAVE_VECTORCALL. Not necessarily. There are subtleties involved when subclassing: there are cases where tp_vectorcall_offset needs

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: Cython issue: https://github.com/cython/cython/issues/2976 -- ___ Python tracker ___ ___ Python-b

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > IMHO the simplest and safest option for this issue is to revert tp_print > removal and move tp_vectorcall_offset at the end of PyTypeObject. That's a drastic solution to a rather simple problem. PR 14009 would fix Cython just fine. -- ___

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: me: > I understand that tp_vectorcall_offset=0 is fine and the expected value for a > type which doesn't have the flag _Py_TPFLAGS_HAVE_VECTORCALL. Jeroen Demeyer: > Not necessarily. There are subtleties involved when subclassing: there are > cases where tp_

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: https://github.com/cython/cython/commit/f10a0a391edef10bd37095af87f521808cb362f7 Note for myself: this fix is already part of Cython 0.29.10 released at June 2 (10 days ago). -- ___ Python tracker

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > This code can cause subtle and annoying issue if PR 13858 is merged. I don't see how this is related to PR 13858 at all. Please explain. -- ___ Python tracker ___

[issue37248] support conversion of `func(**{} if a else b)`

New submission from Pablo Galindo Salgado : Please, can you add some text with an explanation ? -- nosy: +pablogsal ___ Python tracker ___ _

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > If we decide to not reintroduce tp_print, tp_print removal must be documented > at: https://docs.python.org/dev/whatsnew/3.8.html#changes-in-the-c-api I'll add that to PR 13844. -- ___ Python tracker

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > This code can cause subtle and annoying issue if PR 13858 is merged. Or maybe you're confusing tp_vectorcall_offset and tp_vectorcall again? -- ___ Python tracker ___

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

STINNER Victor added the comment: > Or maybe you're confusing tp_vectorcall_offset and tp_vectorcall again? The two are related, no? Honestly, reintroducing tp_print looks simple and safe enough. I'm in favor of doing that. Is there any drawback? (as I wrote, I don't think that the size of

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > Honestly, reintroducing tp_print looks simple and safe enough. Is there any > drawback? 1. The one-time effort to change the code and documentation back. 2. Stefan Behnel wanted to use tp_print for backporting vectorcall in Cython to earlier Python versio

[issue37250] C files generated by Cython set tp_print to NULL: PyTypeObject.tp_print removed, replaced with tp_vectorcall_offset

Jeroen Demeyer added the comment: > The two are related, no? Related in the same way that tp_dictoffset and tp_dict are related (i.e. not that much). -- ___ Python tracker _

[issue37251] Mocking a MagicMock with a function spec results in an AsyncMock

New submission from Jeremy Cline : This is related to the new AsyncMock[0] class in Python 3.8b1. A simple reproducer is: from unittest import mock mock_obj = mock.MagicMock() mock_obj.mock_func = mock.MagicMock(spec=lambda x: x) with mock.patch.object(mock_obj, "mock_func") as nested: p

[issue37210] Pure Python pickle module should not depend on _pickle.PickleBuffer

STINNER Victor added the comment: FYI pyperformance is affected by this issue: vstinner@apu$ env/bin/python ~/prog/python/pyperformance/pyperformance/benchmarks/bm_pickle.py unpickle --pure-python -v -p3 Traceback (most recent call last): File "/home/vstinner/prog/python/pyperformance/p

[issue37251] Mocking a MagicMock with a function spec results in an AsyncMock

Change by Karthikeyan Singaravelan : -- nosy: +lisroach, xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue37248] support conversion of `func(**{} if a else b)`

Karthikeyan Singaravelan added the comment: >From the title is this similar to the PR >https://github.com/python/cpython/pull/12703 -- nosy: +xtreak ___ Python tracker ___ __

[issue37251] Mocking a MagicMock with a function spec results in an AsyncMock

Change by Mario Corchero : -- nosy: +mariocj89 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue37210] Pure Python pickle module should not depend on _pickle.PickleBuffer

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

[issue37210] Pure Python pickle module should not depend on _pickle.PickleBuffer

STINNER Victor added the comment: I wrote a simple PR, PR 14016, to fix the pure Python implementation of pickle: simply restrict pickle to protocol 4 if PickleBuffer is missing. -- ___ Python tracker _

[issue37210] Pure Python pickle module should not depend on _pickle.PickleBuffer

Change by STINNER Victor : -- resolution: wont fix -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue34058] Default Python 3.7 install broken on openSUSE Leap 42.3: $PYTHONHOME/lib64/python3.7/lib-dynload/ not linked to $PYTHONHOME/lib/python3.7/lib-dynload/

Cooper Lees added the comment: I also have the same problem with _socket that was Fixed on the latest version of CentOS 7 building with gcc 4.8.5. Adding: sudo ln -s /usr/local/lib64/python3.7/lib-dynload/ /usr/local/lib/python3.7/lib-dynload Allowed the .so to be found and the import to wo

[issue35766] Merge typed_ast back into CPython

STINNER Victor added the comment: New changeset b2fd32b2f041402bb9fc8607f01566c055aafed9 by Victor Stinner in branch '3.8': bpo-35766: compile(): rename feature_version parameter (GH-13994) (GH-14001) https://github.com/python/cpython/commit/b2fd32b2f041402bb9fc8607f01566c055aafed9

[issue37252] devpoll test failures on Solaris

New submission from Jakub Kulik : test_devpoll currently ends with two failures with Python 3.8 on Solaris. First one is wrong number of arguments to devpoll.register function (which thrown the same error as expected in 3.7 but now acts differently). Second one is that register and modify no

[issue37252] devpoll test failures on Solaris

Change by Jakub Kulik : -- keywords: +patch pull_requests: +13882 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14017 ___ Python tracker ___

[issue35766] Merge typed_ast back into CPython

Guido van Rossum added the comment: Thanks for taking care of this! -- --Guido (mobile) -- ___ Python tracker ___ ___ Python-bugs-

[issue35066] Inconsistency between dangling '%' handling in time.strftime() and datetime.strftime()

Erik Bray added the comment: FWIW (unsurprisingly) the new test added here is broken on Cygwin, whose libc's (newlib) behavior in this undefined case. So I get: >>> from datetime import date >>> t = date(2005, 1, 1) >>> t.strftime("%Y") # ok '2005' >>> t.strftime("%%") # ok '%' >>> t.strft

[issue37251] Mocking a MagicMock with a function spec results in an AsyncMock

Change by Miro Hrončok : -- nosy: +hroncok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue37253] PyCompilerFlags got a new cf_feature_version field

New submission from STINNER Victor : The commit dcfcd146f8e6fc5c2fc16a4c192a0c5f5ca8c53c of bpo-35766 added a new cf_feature_version field to PyCompilerFlags. Each PyCompilerFlags variable must properly initialize this new field to PY_MINOR_VERSION. I propose to add a new _PyCompilerFlags_INI

[issue37253] PyCompilerFlags got a new cf_feature_version field

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

[issue37241] Item Count Error in Shelf

Jesse Bacon added the comment: I am missing keys, when extracting the data back out with todays NVD pull. --- KeyError Traceback (most recent call last) ~/anaconda3/lib/python3.6/shelve.py i

[issue37253] PyCompilerFlags got a new cf_feature_version field

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

[issue37254] POST large file to server (using http.server.CGIHTTPRequestHandler), always reset by server.

New submission from shajianrui : Windows 10, python 3.7 I met a problem when using the http.server module. I set up a base server with class HTTPServer and CGIHTTPRequestHandler(Not using thread or fork) and tried to POST a large file (>2MB), then I find the server always reset the connectio

[issue37241] Item Count Error in Shelf

Change by Jesse Bacon : Added file: https://bugs.python.org/file48413/ShelfKeys.png ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37253] PyCompilerFlags got a new cf_feature_version field

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

[issue37253] PyCompilerFlags got a new cf_feature_version field

STINNER Victor added the comment: > Something else, ast.parse() has been modified to use a (major, minor) version > tuple rather an integer to specify the Python version in feature_version, but > PyCompilerFlags still only uses the minor major. This API will be broken once > the Python major

[issue35766] Merge typed_ast back into CPython

STINNER Victor added the comment: I created bpo-37253: "PyCompilerFlags got a new cf_feature_version field". -- ___ Python tracker ___

[issue37160] thread native id netbsd support

New submission from STINNER Victor : New changeset 5287022eeeb3c017d49fc8580b52e18377bf23f3 by Victor Stinner (David Carlier) in branch 'master': bpo-37160: Thread native ID NetBSD support (GH-13835) https://github.com/python/cpython/commit/5287022eeeb3c017d49fc8580b52e18377bf23f3 --

[issue37160] thread native id netbsd support

Change by miss-islington : -- keywords: +patch pull_requests: +13886 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14021 ___ Python tracker ___ _

[issue37160] thread native id netbsd support

STINNER Victor added the comment: Since threading.get_native_id() is a new feature in Python 3.8 and the PR is small enough, IMHO it's fine to backport the change to 3.8. -- versions: +Python 3.8 ___ Python tracker

[issue37160] thread native id netbsd support

miss-islington added the comment: New changeset c9ca96dd968176580a011e852066c95a48aab7e0 by Miss Islington (bot) in branch '3.8': bpo-37160: Thread native ID NetBSD support (GH-13835) https://github.com/python/cpython/commit/c9ca96dd968176580a011e852066c95a48aab7e0 -- nosy: +miss-is

[issue37160] thread native id netbsd support

STINNER Victor added the comment: Thanks David Carlier! It's now merged into 3.8 and master. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue37251] Mocking a MagicMock with a function spec results in an AsyncMock

Lisa Roach added the comment: Following up from xtreak's proposal (https://github.com/python/cpython/pull/9296) I think checking if __code__ is actually a CodeType is a good idea. It's simple and doesn't change any other functionality in an unwanted way. --

[issue37176] super() docs don't say what super() does

Carlos André Dantas de Lima added the comment: The method says who you will use some recursion. -- nosy: +Carlos André Dantas de Lima ___ Python tracker ___ ___

[issue37255] Pathlib: Add an expandUserPath method or argument

New submission from Andrea Moro : Assuming the given path contains a '~' character, it would be nice to have a function to expand the given path so any further calls to an .exists doesn't fail. A prototype of the function could be # Expand the home path in *ix based systems if any

[issue36607] asyncio.all_tasks() crashes if asyncio is used in multiple threads

Łukasz Langa added the comment: Note: there's a discussion on GitHub on PR 13971 being a bad solution: https://github.com/python/cpython/pull/13971#issuecomment-500908198 They should be reverted (or fixed forward) for 3.8 and 3.9. I'm OK with this modifying the AbstractEventLoop API if need

[issue37241] Item Count Error in Shelf

Eric V. Smith added the comment: This still isn't an example we can copy and paste to reproduce, so I'm going to be unable to help you. Sorry. Again: please don't post images, for the reasons I previously stated. -- ___ Python tracker

  1   2   3   >