[issue22087] asyncio: support multiprocessing (support fork)

Change by Yury Selivanov : -- pull_requests: +6864 ___ Python tracker <https://bugs.python.org/issue22087> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22087] asyncio: support multiprocessing (support fork)

Change by Yury Selivanov : -- pull_requests: +6865 ___ Python tracker <https://bugs.python.org/issue22087> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue22087] asyncio: support multiprocessing (support fork)

Yury Selivanov added the comment: Even though I committed a version of Dan's patch to 3.7 and 3.8, I've finally decided to revert it and do it properly instead. We should strive to implement a proper solution, not commit some half-working code. A concrete plan (for Python 3.8 pro

[issue32684] asyncio.gather(..., return_exceptions=True) swallows cancellation

Yury Selivanov added the comment: New changeset 3ddee64587482082fcbab930ff82ed67aa9f4a0d by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-32684: Fix nits in tests (GH-7225) (#7231) https://github.com/python/cpython/commit/3ddee64587482082fcbab930ff82ed

[issue22087] asyncio: support multiprocessing (support fork)

Yury Selivanov added the comment: New changeset 99279ad823a758288e4e41962abfc4dad8943ce8 by Yury Selivanov in branch 'master': Revert "bpo-22087: Fix Policy.get_event_loop() to detect fork (GH-7208)" (#7232) https://github.com/python/cpython/commit/99279ad823a758288e4e

[issue22087] asyncio: support multiprocessing (support fork)

Yury Selivanov added the comment: New changeset af9cda9845666e2f704177a431d29f91efbf828a by Yury Selivanov in branch '3.7': Revert "bpo-22087: Fix Policy.get_event_loop() to detect fork (GH-7208)" (GH-7233) https://github.com/python/cpython/commit/af9cda9845666e2f7041

[issue32684] asyncio.gather(..., return_exceptions=True) swallows cancellation

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue32751] wait_for(future, ...) should wait for the future (even if a timeout occurs)

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior ___ Python tracker <https://bugs.python

[issue33638] condition lock not re-acquired

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue23859] asyncio: document behaviour of wait() cancellation

Yury Selivanov added the comment: New changeset f95269404c03bd769a3551cd851b51b8f89672df by Yury Selivanov (Miss Islington (bot)) in branch '3.7': [3.7] bpo-23859: Document that asyncio.wait() does not cancel its futures (GH-7217) (#7227) https://github.com/python/cpyt

[issue33649] asyncio docs overhaul

Yury Selivanov added the comment: > Yury: do you want to do the re-organization into high- and low-level APIs? > If you'd like me to do it, I'll need a more explicit listing of which APIs > fall into which category. Sure, I'll update this issue tomorrow or t

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Yury Selivanov added the comment: I can't reproduce test_start_tls_server_1 fails when I do (screenshot attached) 1. run test_asyncio 2. run test_asyncio.test_sslproto 3. run test_asyncio.test_sslproto -m test_start_tls_server_1 I run them in Windows 7 VM on Mac OS. All other tests

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Yury Selivanov added the comment: > We can remove the socket buffers size manipulation at all without any problem. When I tried to do that I think I was having more failures with that test. But really up to you. -- ___ Python tracker <

[issue33727] Server.wait_closed() doesn't always wait for its transports to fihish

New submission from Yury Selivanov : Server.wait_closed() currently does two checks: 1. if _sockets is None -- means that Server.close() was called 2. if self._waiters is None -- means that Server._wakeup() was called if (1) *or* (2) is true, wait_closed() just returns without waiting on

[issue33733] Add utilities to get/set pipe and socket buffer sizes?

Change by Yury Selivanov : -- nosy: +njs ___ Python tracker <https://bugs.python.org/issue33733> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

New submission from Yury Selivanov : I've ported asyncio's sslproto.py to uvloop and released a new major version of it yesterday. Hynek discovered that the default SSL handshake timeout (10 seconds currently) is too low, and that there's a critical code path that is br

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: For the reference, we added SSL handshake timeout a while ago in bpo-29970. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Change by Yury Selivanov : -- keywords: +patch pull_requests: +6950 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33734> ___ ___ Py

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: > What was the effective timeout before? Depending on the old value, 60s could > be excessive for clients and might lead to self-DoS on the client side… Previous timeout was effectively infinite. -- ___

[issue33650] Prohibit adding a signal handler for SIGCHLD

Yury Selivanov added the comment: To clarify this ticket: I'm talking about prohibiting `loop.add_signal_handler(SIGCHLD)` as it would break child processes watchers that asyncio installs. In other words, setting a custom SIGCHLD breaks asyncio internals. We can allow user-set SI

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

New submission from Yury Selivanov : We can allow using ... to navigate the "parent" path: >>> import pathlib >>> p = pathlib.Path('a/b/c') >>> p PosixPath('a/b/c') >>> p / ... PosixPath('a/b')

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Change by Yury Selivanov : -- keywords: +patch pull_requests: +6958 ___ Python tracker <https://bugs.python.org/issue33739> ___ ___ Python-bugs-list mailin

[issue33739] pathlib: Allow ellipsis to appear after "/" to navigate to parent path

Yury Selivanov added the comment: Since nobody likes the idea I'm withdrawing the proposal. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.pyth

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: New changeset 9602643120a509858d0bee4215d7f150e6125468 by Yury Selivanov in branch 'master': bpo-33734: asyncio/ssl: a bunch of bugfixes (#7321) https://github.com/python/cpython/commit/9602643120a509858d0bee4215d7f1

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: New changeset 87936d03cb29ca039c5799190e8da764e62b7882 by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-33734: asyncio/ssl: a bunch of bugfixes (GH-7321) (GH-7396) https://github.com/python/cpython/commit/87936d03cb29ca039c5799190e8da7

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: Fixes are in master and 3.7 now, so this should be fixed in 3.7.0rc1. Ned, I'm not sure what's the workflow here, please feel free to close this issue and change its priority. -- ___ Python track

[issue33734] asyncio/ssl: Fix AttributeError, increase default handshake timeout

Yury Selivanov added the comment: > Since it apparently does not apply to 3.6, we should just close it like any > other issue, right? So doing! Sure. My understanding is that all changes including this one in 3.7 branch will end up in 3.7.0rc1,

[issue33769] Cleanup start_tls() implementation

New submission from Yury Selivanov : Current start_tls() implementation might raise an incorrect error message. It should also consistently cancel callbacks that it schedules in case of unhandled error. -- assignee: yselivanov components: asyncio messages: 318688 nosy: asvetlov

[issue33769] Cleanup start_tls() implementation

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7030 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33769> ___ ___ Py

[issue33769] Cleanup start_tls() implementation

Yury Selivanov added the comment: New changeset 415bc46a78e785f357c8960ae70f18a6b6cccbb6 by Yury Selivanov in branch 'master': bpo-33769: start_tls: Fix error message; cancel callbacks on error (GH-7403) https://github.com/python/cpython/commit/415bc46a78e785f357c8960ae70f18

[issue33769] Cleanup start_tls() implementation

Yury Selivanov added the comment: New changeset 79c7e57c46a9e5ae2b99a821e152f334b775df2d by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-33769: start_tls: Fix error message; cancel callbacks on error (GH-7403) (GH-7428) https://github.com/python/cpyt

[issue33769] Cleanup start_tls() implementation

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33776] Segfault when passing invalid argument to asyncio.ensure_future

Yury Selivanov added the comment: Thanks for reporting it. Looks like this has been fixed in 3.6 (not yet released) and 3.7.0b5 in issue 33584. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracke

[issue33786] @asynccontextmanager doesn't work well with async generators

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7089 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33786> ___ ___ Py

[issue33786] @asynccontextmanager doesn't work well with async generators

Yury Selivanov added the comment: Would be nice to fix this in 3.7.0 -- components: +Interpreter Core -asyncio nosy: +ned.deily priority: normal -> release blocker type: -> behavior versions: +Python 3.6, Python 3.8 ___ Python tracker

[issue30773] async generator receives wrong value when shared between coroutines

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7091 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue30773> ___ ___ Py

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Change by Yury Selivanov : -- pull_requests: +7111 ___ Python tracker <https://bugs.python.org/issue33694> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33792] asyncio: how to set a "Proactor event loop" policy? Issue with asyncio.run()

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7112 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33792> ___ ___ Py

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7132 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33803> ___ ___ Py

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Yury Selivanov added the comment: Thanks Victor for debugging this. I made a PR (which is now trivial) and double checked all other calls to GCTrack in context.c & hamt.c. -- ___ Python tracker <https://bugs.python.org/iss

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Yury Selivanov added the comment: New changeset 378c53cc3187dba57c7560ccc2557f516c8a7bc8 by Yury Selivanov in branch 'master': bpo-33803: Fix a crash in hamt.c (#7504) https://github.com/python/cpython/commit/378c53cc3187dba57c7560ccc2557f

[issue33786] @asynccontextmanager doesn't work well with async generators

Yury Selivanov added the comment: New changeset 52698c7ad9eae9feb35839fde17a7d1da8036a9b by Yury Selivanov in branch 'master': bpo-33786: Fix asynchronous generators to handle GeneratorExit in athrow() (GH-7467) https://github.com/python/cpyt

[issue33786] @asynccontextmanager doesn't work well with async generators

Change by Yury Selivanov : -- pull_requests: +7135 ___ Python tracker <https://bugs.python.org/issue33786> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Yury Selivanov added the comment: New changeset a971a6fdb111bb62911ccf45aa9fe734e2e7a590 by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-33803: Fix a crash in hamt.c (GH-7504) (GH-7505) https://github.com/python/cpython/commit/a971a6fdb111bb62911ccf45aa9fe7

[issue33792] asyncio: how to set a "Proactor event loop" policy? Issue with asyncio.run()

Yury Selivanov added the comment: New changeset 8f4042964d5b0ddf5cdf87862db962ba64e3f64a by Yury Selivanov in branch 'master': bpo-33792: Add selector and proactor windows policies (GH-7487) https://github.com/python/cpython/commit/8f4042964d5b0ddf5cdf87862db962

[issue33609] Document that dicts preserve insertion order

Yury Selivanov added the comment: New changeset 9b0d4d04a15a97a1055f1b729f14e9257f149fd3 by Yury Selivanov (Miss Islington (bot)) in branch '3.7': bpo-33609: small wording fixes to dict ordering docs (#7497) https://github.com/python/cpython/commit/9b0d4d04a15a97a1055f1b729f14e9

[issue33786] @asynccontextmanager doesn't work well with async generators

Yury Selivanov added the comment: New changeset 8de73d5a6914cfe55c23b0ad829cd2ba8954bc2e by Yury Selivanov in branch '3.6': bpo-33786: Fix asynchronous generators to handle GeneratorExit in athrow() (GH-7467) (GH-7507) https://github.com/python/cpyt

[issue33786] @asynccontextmanager doesn't work well with async generators

Change by Yury Selivanov : -- pull_requests: +7140 ___ Python tracker <https://bugs.python.org/issue33786> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33786] @asynccontextmanager doesn't work well with async generators

Yury Selivanov added the comment: New changeset b0bb9a81f60ed248a44b4c8008c0549c3e9e741d by Yury Selivanov in branch '3.6': bpo-33786: Fix asynchronous generators to handle GeneratorExit in athrow() (GH-7467) (#7514) https://github.com/python/cpyt

[issue33786] @asynccontextmanager doesn't work well with async generators

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33792] asyncio: how to set a "Proactor event loop" policy? Issue with asyncio.run()

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33803] contextvars: hamt_alloc() must initialize h_root and h_count fields

Yury Selivanov added the comment: > +if (core_config->dev_mode) { > +_PyRuntime.gc.generations[0].threshold = 5; > +} I'd love to have a flag to turn this on, or maybe we should enable it for -X dev. -- ___ Pytho

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Yury Selivanov added the comment: New changeset 4aa3006619392438b0775a2f488bbe9e7a22c468 by Yury Selivanov (Dong-hee Na) in branch 'master': bpo-33197: Add description property for _ParameterKind. (GH-7206) https://github.com/python/cpython/commit/4aa3006619392438b0775a2f488bbe

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Yury Selivanov added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Yury Selivanov added the comment: We forgot to add "versionadded: 3.8" tag to the documentation of ParameterKind.description. Dong-hee Na, could you please make a PR to add it? -- status: closed -> open ___ Python tr

[issue33736] Improve the documentation of asyncio stream API

New submission from Yury Selivanov : New changeset c0d062f523b16331444ff910e4596ee5608c8170 by Yury Selivanov (Elvis Pranskevichus) in branch 'master': bpo-33736: Improve the documentation of asyncio stream APIs (GH-7326) https://github.com/python/cpyt

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Yury Selivanov added the comment: > @yselivanov > Please take a look PR 7536 :) Thanks! Please stop posting comments like this frequently. They are highly distractive. -- ___ Python tracker <https://bugs.python.org/i

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Yury Selivanov added the comment: New changeset 4f54867e29af93779922ff23df542f2d5df4c4ee by Yury Selivanov (Dong-hee Na) in branch 'master': bpo-33197: Add versionadded tag to the documentation of ParameterKind (GH-7536) https://github.com/python/cpyt

[issue33197] Confusing error message when constructing invalid inspect.Parameters

Change by Yury Selivanov : -- stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue33197> ___ ___ Pyth

[issue30805] asyncio: race condition with debug and subprocess

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7178 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue30805> ___ ___ Py

[issue30805] asyncio: race condition with debug and subprocess

Yury Selivanov added the comment: New changeset 12f482e0ae33021c04264294f33fa6baa9617cec by Yury Selivanov in branch 'master': bpo-30805: Avoid race condition with debug logging (GH-7545) https://github.com/python/cpython/commit/12f482e0ae33021c04264294f33fa6

[issue30805] asyncio: race condition with debug and subprocess

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue33811] asyncio accepting connection limit

Yury Selivanov added the comment: In principle this sounds good, but I'm not sure how the API and implementation would look like. Maybe you can share a bit more details? -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tr

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Yury Selivanov added the comment: pause_reading and resume_reading became idempotent only in 3.7 -- ___ Python tracker <https://bugs.python.org/issue33

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

Yury Selivanov added the comment: Since it a minor change we can reconsider it as s bug fix. Feel free to make a pr. -- ___ Python tracker <https://bugs.python.org/issue33

[issue33823] A BUG in concurrent/asyncio

Yury Selivanov added the comment: > which results in the resulting statistics of the last code run cannot be > promised to be separated. I'm sorry but I cannot parse your message and the attached code snippet. Please try to formulate the actual bug/feature request m

[issue33833] ProactorEventLoop raises AssertionError

Yury Selivanov added the comment: Adding Victor as he's been helping with asyncio/proactor lately. -- nosy: +vstinner ___ Python tracker <https://bugs.python.org/is

[issue33837] Closing asyncio.Server on asyncio.ProactorEventLoop causes all active servers to stop listening

Yury Selivanov added the comment: Andrew, do you have time to take a look into this? -- ___ Python tracker <https://bugs.python.org/issue33837> ___ ___ Pytho

[issue33840] connection limit on listening socket in asyncio

Yury Selivanov added the comment: Do other frameworks (Tornado, Twisted, libuv/nodejs) have this functionality? -- ___ Python tracker <https://bugs.python.org/issue33

[issue33671] Efficient zero-copy for shutil.copy* functions (Linux, OSX and Win)

Change by Yury Selivanov : -- nosy: -yselivanov ___ Python tracker <https://bugs.python.org/issue33671> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31861] aiter() and anext() built-in functions

Yury Selivanov added the comment: > Do these really need to be builtins? We're only beginning to see async iterators being used in the wild, so we can't have a definitive answer at this point. > They seem too specialized to be widely useful; I've personally never needed

[issue33918] Hooking into pause/resume of iterators/coroutines

Yury Selivanov added the comment: You should try to use the contextvars module that was specifically created to handle local context state (for tasks & coroutines). -- ___ Python tracker <https://bugs.python.org/iss

[issue33918] Hooking into pause/resume of iterators/coroutines

Yury Selivanov added the comment: > Imagine the context manager is mock.patch used in testing and you want to run > two tests in "parallel", each with a different mocked method. mock.patch > isn't aware of `await` so patching will be incorrect. That's still doab

[issue33985] ContextVar does not have a "name" attribute

Yury Selivanov added the comment: Yeah, it seems that I forgot to implement ContextVars.name attribute. Will have a PR shortly. Expect to see this fixed in 3.7.1 in a couple of months. Adding Ned to the issue just in case. -- components: +Interpreter Core -Library (Lib) nosy

[issue33985] ContextVar does not have a "name" attribute

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7591 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33985> ___ ___ Py

[issue32996] Improve What's New in 3.7

Yury Selivanov added the comment: New changeset 4d26c8a177d8ada440b3cfdfb1d0423ab5ca81a7 by Yury Selivanov (Elvis Pranskevichus) in branch 'master': bpo-32996: Enhancements to What's New based on feedback (GH-7988) https://github.com/python

[issue27500] ProactorEventLoop cannot open connection to ::1

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7604 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue27500> ___ ___ Py

[issue27500] ProactorEventLoop cannot open connection to ::1

Yury Selivanov added the comment: > Somebody please submit a PR so this can be fixed in 3.7.1 and the fix can > be backported to 3.6.7. Somehow I overlooked this one when I was sifting the issues we needed to fix in 3.7. I've opened a PR. -- priority: nor

[issue33985] ContextVar does not have a "name" attribute

Yury Selivanov added the comment: New changeset 41cb0baea96a80360971908a0bd79d9d40dd5e44 by Yury Selivanov in branch 'master': bpo-33985: Implement ContextVar.name attribute. (GH-7980) https://github.com/python/cpython/commit/41cb0baea96a80360971908a0bd79d

[issue33985] ContextVar does not have a "name" attribute

Change by Yury Selivanov : -- priority: release blocker -> high ___ Python tracker <https://bugs.python.org/issue33985> ___ ___ Python-bugs-list mai

[issue33985] ContextVar does not have a "name" attribute

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue27500] ProactorEventLoop cannot open connection to ::1

Yury Selivanov added the comment: New changeset d904c238ca3551750cb97d15d827c3e525970867 by Yury Selivanov in branch 'master': bpo-27500: Fix static version of getaddrinfo to resolve IPv6 (GH-7993) https://github.com/python/cpython/commit/d904c238ca3551750cb97d15d827c3

[issue34014] loop.run_in_executor should propagate current contextvars

Yury Selivanov added the comment: I considered enabling that, but in the end decided not to. The reason is that it's possible to use a ProcessPoolExecutor with run_in_execuror(), and context cars currently don't support pickling (and probably never will). We can't have a

[issue34014] loop.run_in_executor should propagate current contextvars

Yury Selivanov added the comment: As a workaround you can subclass the ThreadPoolExecutor and set it as a default executor. -- ___ Python tracker <https://bugs.python.org/issue34

[issue34042] Reference loss for local classes

Yury Selivanov added the comment: This isn't a real reference bug, but rather a bug in total refs accountability. It seems that I missed the fact that we track refs to the keys table with a DK_INCREF macro. The new `clone_combined_dict` uses `memcpy` to clone the keys table (along

[issue34042] Reference loss for local classes

Change by Yury Selivanov : -- keywords: +patch pull_requests: +7704 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue34042> ___ ___ Py

[issue34042] Reference loss for local classes

Yury Selivanov added the comment: > Agreed, if it was a real reference bug, the interpreter should crash before > the total reference count gets negative ;-) First thing I checked with Serhiy's script :) A PR with a fix: https://github.com/python/cpytho

[issue34042] Reference loss for local classes

Yury Selivanov added the comment: > If you could do what you often you, and make this what distributions like > Debian pull from, it would be good enough in terms of release for me, as it > blocks Nuitka tests from passing on them. I'm not sure what you mean by "what

[issue34042] Reference loss for local classes

Yury Selivanov added the comment: New changeset 0b75228700e0077d8bf2636e74733389514b4b2f by Yury Selivanov in branch 'master': bpo-34042: Fix dict.copy() to maintain correct total refcount (GH-8119) https://github.com/python/cpython/commit/0b75228700e0077d8bf2636e747333

[issue34042] Reference loss for local classes

Yury Selivanov added the comment: Thank you for reporting the issue, Kay. And huge thanks to Antoine and Pablo for bisecting. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracke

[issue34074] Asyncio breaks coroutine finalization process

Yury Selivanov added the comment: There's no bug here. `loop.stop()` simply stops the loop, all running tasks are just paused. You can re-run the same loop, and the `work()` task will resume. In other words, `loop.stop()` does not trigger task cancellation, therefore it does not thr

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

New submission from Yury Selivanov : I've had a few conversations with people who were confused that asyncio starts to behave weirdly when a ProcessPoolExecutor is set as the default one. We don't really test that asyncio's built-in functionality (like DNS resolving) wo

[issue34074] Asyncio breaks coroutine finalization process

Yury Selivanov added the comment: > To make example more practical, let's change `loop.stop()` to `raise > KeyboardInterrupt()`. Program stops without calling `close()` Try to use the new `asyncio.run()` function (in Py 3.7) -- ___ Pyt

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Yury Selivanov added the comment: Great! Thanks for the quick reply, Guido. -- ___ Python tracker <https://bugs.python.org/issue34075> ___ ___ Python-bugs-list m

[issue34073] asyncio and ProcessPoolExecutor: OSError on loop.close()

Yury Selivanov added the comment: We plan to deprecate and later prohibit setting ProcessPoolExecutor as the default executor. See https://bugs.python.org/issue34075 for more details. -- resolution: -> remind stage: -> resolved status: open -&g

[issue34075] We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Yury Selivanov added the comment: > We should warn against this in the docs right away (and backport the warning > to all previous versions that have set_executor). I think we'll only allow instances of c.f.ThreadPoolExecutor (and its subclasses) to be passed to set_defau

[issue34075] asyncio: We should prohibit setting a ProcessPoolExecutor in with set_default_executor

Yury Selivanov added the comment: > I don't see why asyncio should prevent people to experiment their own custom > executor. You can imagine a custom "green executor" which inherit from > Executor but uses its own black magic like greenlet. Because asyncio and its e

[issue34263] asyncio: "relative *delay* or absolute *when* should not exceed one day"

New submission from Yury Selivanov : asyncio documentation has this bit on timeouts: Timeouts (relative *delay* or absolute *when*) should not exceed one day. Victor told me that the actual reason for this recommendation is a limitation in epoll (or other OS/selector) that prevents us

[issue1764286] inspect.getsource does not work with decorated functions

Yury Selivanov added the comment: > Should `getsourcefile` be changed to match? I'd say yes. There's no point in getsourcefile returning the file location of the topmost decorator. Feel free to open a new issue and submit a PR

<    8   9   10   11   12   13   14   15   16   17   >