[issue38565] Expose the value passed of typed passed to functools.lru_cache

Manjusaka added the comment: I have already make a PR for this issue but here's a problem. add a new field to cache_info maybe cause some special problem for the third-party libs what're dependent the cache_info -- ___ Python tracker

[issue38572] Misleading AttributeError accessing fileno attribute in tarfile

New submission from Karthikeyan Singaravelan : This came up during https://github.com/psf/requests/issues/5229 . While fileno returns True as an attribute the actual implementation uses self.raw.fileno where the AttributeError is raised at https://github.com/python/cpython/blob/96b06aefe23521

[issue38565] Expose the value passed of typed passed to functools.lru_cache

Change by Manjusaka : -- keywords: +patch pull_requests: +16445 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16915 ___ Python tracker ___ __

[issue33348] lib2to3 doesn't parse f(*[] or [])

miss-islington added the comment: New changeset d04661f9ca4a082a2dd9de52df687600d574407e by Miss Skeleton (bot) in branch '3.8': bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586) https://github.com/python/cpython/commit/d04661f9ca4a082a2dd9de52df687600d574407e -- ___

[issue33348] lib2to3 doesn't parse f(*[] or [])

miss-islington added the comment: New changeset 0160a70acbd9c530802effdf320ab08c7132f4bf by Miss Skeleton (bot) in branch '3.7': bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586) https://github.com/python/cpython/commit/0160a70acbd9c530802effdf320ab08c7132f4bf -- ___

[issue33348] lib2to3 doesn't parse f(*[] or [])

miss-islington added the comment: New changeset 96b06aefe23521b61e4e9cdd44f5d30b00c7eb95 by Miss Skeleton (bot) (Zsolt Dollenstein) in branch 'master': bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586) https://github.com/python/cpython/commit/96b06aefe23521b61e4e9cdd44f5d30b00c

[issue33348] lib2to3 doesn't parse f(*[] or [])

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

[issue33348] lib2to3 doesn't parse f(*[] or [])

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

[issue38571] Segfault with StopIteration

Gregory P. Smith added the comment: There isn't really much we can do without a reasonable repeatable way to reproduce the problem. -- nosy: +gregory.p.smith ___ Python tracker _

[issue36541] Make lib2to3 grammar better match Python, support the := walrus

Change by Gregory P. Smith : -- title: Make lib2to3 grammar more closely match Python -> Make lib2to3 grammar better match Python, support the := walrus ___ Python tracker ___

[issue36541] Make lib2to3 grammar more closely match Python

Change by Gregory P. Smith : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mai

[issue33348] lib2to3 doesn't parse f(*[] or [])

Change by Gregory P. Smith : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue33348] lib2to3 doesn't parse f(*[] or [])

Change by Gregory P. Smith : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mai

[issue32496] lib2to3 fails to parse a ** of a conditional expression

Change by Gregory P. Smith : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> lib2to3 doesn't parse f(*[] or []) versions: +Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker

[issue33348] lib2to3 doesn't parse f(*[] or [])

Change by Gregory P. Smith : -- versions: +Python 3.9 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue36541] Make lib2to3 grammar more closely match Python

Change by Gregory P. Smith : -- versions: +Python 3.9 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue38565] Expose the value passed of typed passed to functools.lru_cache

Change by Karthikeyan Singaravelan : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue20443] __code__. co_filename should always be an absolute path

Gregory P. Smith added the comment: Please revert. An absolute path changes semantics in many real world situations (altering symlink traversals, etc). People expect the current sys.argv[0] behavior which is "similar to C argv" and matches what was passed on the interpreter command line.

[issue38565] Expose the value passed of typed passed to functools.lru_cache

Manjusaka added the comment: I think it's a good idea to expose the full arguments that people use in lru_cache() -- nosy: +Manjusaka ___ Python tracker ___ _

[issue38559] async generators aclose() behavior in 3.8

Yury Selivanov added the comment: The more I think about this the more I like new 3.8 behavior. I'm going to close this issue; if anything comes up I'll reopen it later. Sorry for the noise. -- resolution: -> not a bug stage: -> resolved status: open -> closed

[issue38567] urllib.parse.unquote_plus raises incorrect error message when string parameter is bytes

Change by Emmanuel Arias : -- nosy: +eamanu title: urllib.parse.unquote_plus raises incorrect errormessage when string parameter is bytes -> urllib.parse.unquote_plus raises incorrect error message when string parameter is bytes ___ Python tracker

[issue38092] environment variables not passed correctly using new virtualenv launching in windows and python3.7+

Eryk Sun added the comment: This should revert to setting `_python_exe = sys.executable` in Lib/multiprocessing/spawn.py. Then the code in Lib/multiprocessing/popen_spawn_win32.py will set __PYVENV_LAUNCHER__ in the spawned process to the virtual environment's sys.executable. Otherwise the

[issue38571] Segfault with StopIteration

New submission from Kevin Chen : Unfortunately, I don't currently have a simple test case, but after migrating an app from python 3.6 to python 3.7, python frequently (but not always) segfaults when running tests for my app in code related to StopIteration (perhaps somehow related to the impl

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

Yury Selivanov added the comment: I'll elevate the status so that we don't forget before 3.8.1 is too close -- priority: normal -> deferred blocker ___ Python tracker ___

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

Yury Selivanov added the comment: I think this broke asyncio a bit. These two uvloop sock_* API tests no longer pass on asyncio 3.8: * https://github.com/MagicStack/uvloop/blob/master/tests/test_sockets.py#L192 * https://github.com/MagicStack/uvloop/blob/master/tests/test_sockets.py#L238 A

[issue30618] readlink for pathlib paths

Gregory P. Smith added the comment: Thanks Girts! -- resolution: -> fixed stage: patch review -> commit review status: open -> closed ___ Python tracker ___ _

[issue34776] Postponed annotations break inspection of dataclasses

Yury Selivanov added the comment: > Yury: I'm okay with merging. If I recall, you were going to add a comment or > two about the approach (a closure, if I remember correctly). Sure, I'll rebase and add a comment in a couple of days. I'll elevate the status so that I don't forget before 3.8.

[issue34776] Postponed annotations break inspection of dataclasses

Eric V. Smith added the comment: Yury: I'm okay with merging. If I recall, you were going to add a comment or two about the approach (a closure, if I remember correctly). I think we should backport to 3.8 and 3.7: it's a bug. -- ___ Python tracker

[issue34776] Postponed annotations break inspection of dataclasses

Yury Selivanov added the comment: FWIW we discussed my patch with Eric at PyCon 2019 and I think he had no issues with it. Eric, can I merge it? Should we backport to 3.8? -- ___ Python tracker __

[issue38560] Allow iterable argument unpacking after a keyword argument?

Brandt Bucher added the comment: I've found one occurrence of this in the CPython codebase, in test_ast.py. Basically it makes sure that the following expression parses and compiles correctly: f(1,2,c=3,*d,**e) I doubt that this is to protect against regressions in this specific syntax. Mo

[issue30618] readlink for pathlib paths

miss-islington added the comment: New changeset a01ba333affcc0677146dc8af57179bdb808d608 by Miss Skeleton (bot) (Girts) in branch 'master': bpo-30618: add readlink to pathlib.Path (GH-8285) https://github.com/python/cpython/commit/a01ba333affcc0677146dc8af57179bdb808d608 -- nosy: +m

[issue38570] Shlex does not parse commands containing single quotes correctly

New submission from timonegk : Steps to reproduce: >>> from shlex import split >>> line = "export F=$'\\''" >>> split(line) ValueError: No closing quotation However, when printing the line >>> print(line) export F=$'\'' and pasting the output in bash, no further quotation marks are required.

[issue34384] os.readlink does not accept pathlib.Path on Windows

Steve Dower added the comment: Yep -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue30618] readlink for pathlib paths

Change by Gregory P. Smith : -- assignee: -> gregory.p.smith nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mai

[issue34384] os.readlink does not accept pathlib.Path on Windows

Gregory P. Smith added the comment: can this be closed? -- nosy: +gregory.p.smith status: pending -> open ___ Python tracker ___ __

[issue38569] Unknown distribution option: 'license_files'

New submission from Marco Sulla : I tried to add to `setuptools.setup()` the argument license_files. It works, but I get this warning: /usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'license_files' I suppose the warning can be removed. -- compone

[issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header Injection (follow-up of CVE-2016-5699)

Gregory P. Smith added the comment: Can you please open a separate issue for CVE-2019-18348? It is easier to track that way. (META: In general I think the CVE process is being abused and that these really did not deserve that treatment. https://lwn.net/Articles/801157/ is good reading an

[issue34776] Postponed annotations break inspection of dataclasses

Change by Gregory P. Smith : -- versions: +Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL

Ying Wang added the comment: Oh cool, I didn't know triple quotes can be used as part of f-strings! Thanks for the explanation! -- ___ Python tracker ___

[issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL

Hobs added the comment: It is a limitation of f-strings, though. We're not allowed to use backslashes within the f-string expression in curly braces. So to do what you want you have to create another variable containing the quote character: ``` >>> blah = '"hi"' >>> blah '"hi"' >>> q = '"' >>>

[issue34776] Postponed annotations break inspection of dataclasses

David Hagen added the comment: This PR has been sitting for a while. Any chance we can bring it over the finish line? -- ___ Python tracker ___ __

[issue38566] Description of '\w' behavior is vague in `re` documentation

James Gerity added the comment: Cheers for the additional context. My recommendation would be to change the language to avoid confusion with the consortium's formal specifications. Describing what SRE does should be fine: > Matches any alphanumeric Unicode character, as well as '_'. If the A

[issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL

Hobs added the comment: Not a bug. If you use quotes inside an f-string (or any other kind of string) they need to be escaped. --Hobson On Wed, Oct 23, 2019 at 12:09 PM Ying Wang wrote: > > New submission from Ying Wang : > > Hey, > > I encountered an interesting bug when trying to do string

[issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL

Zachary Ware added the comment: This is because you're trying to use the string's delimiting character (') in the string itself, which won't work for fairly apparent reasons :). Try removing the `f` prefix and see what happens. You can get around this by using a triple-quoted string which w

[issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL

New submission from Ying Wang : Hey, I encountered an interesting bug when trying to do string parsing using f-strings. I am currently under the impression that within the curly braces is any expression that can be successfully evaluated in a REPL. Here's the error: ```bash yingw787@yingw787

[issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar changes

Peter Ludemann added the comment: issue36541 and its proposed PR seem to cover my needs. -- stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue36541] Make lib2to3 grammar more closely match Python

Peter Ludemann added the comment: Also the Grammar.txt diffs look about the same size as I've seen with other upgrades to lib2to3 when the Python grammar changed. -- ___ Python tracker _

[issue38560] Allow iterable argument unpacking after a keyword argument?

Josh Rosenberg added the comment: I'd be +1 on this, but I'm worried about existing code relying on the functional use case from your example. If we are going to discourage it, I think we either have to: 1. Have DeprecationWarning that turns into a SyntaxError, or 2. Never truly remove it, b

[issue38566] Description of '\w' behavior is vague in `re` documentation

Josh Rosenberg added the comment: The definition of \w, historically, has corresponded to the set of characters that can occur in legal variable names in C (alphanumeric ASCII plus underscores, making it equivalent to [a-zA-Z0-9_] for ASCII regex). That's why, on top of the definitely wordy

[issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar changes

Brett Cannon added the comment: @Peter you can close this if issue36541 will fix your issue (i.e. both assignment expressions and positional-only parameters). -- nosy: +brett.cannon ___ Python tracker _

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted

Josh Rosenberg added the comment: It should probably be backport to all supported 3.x branches though, so people aren't required to move to 3.8 to benefit from it. -- ___ Python tracker

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted

Josh Rosenberg added the comment: Pablo's fix looks like a superset of the original fix applied here, so I'm assuming it fixes this issue as well. -- nosy: +josh.r ___ Python tracker ___

[issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header Injection (follow-up of CVE-2016-5699)

Riccardo Schirone added the comment: CVE-2019-18348 has been assigned to the issue explained in https://bugs.python.org/issue30458#msg347282 . Maybe a separate bug for it would be better though. CVE-2019-18348 is about injecting CRLF in HTTP requests through the *host* part of a URL. --

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: Merged the 2.7 fix. Let's just delete the whole block in master. -- ___ Python tracker ___ ___ Pytho

[issue37025] Misleading error message "Python failed to load the default activation context"

Steve Dower added the comment: New changeset 009a6928727b23344613ab6a9a52b9da56ab905c by Steve Dower (Zackery Spytz) in branch '2.7': bpo-37025: AddRefActCtx() shouldn't be checked for failure (GH-16897) https://github.com/python/cpython/commit/009a6928727b23344613ab6a9a52b9da56ab905c -

[issue38567] urllib.parse.unquote_plus raises incorrect errormessage when string parameter is bytes

Change by stein-k : -- keywords: +patch pull_requests: +16441 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16903 ___ Python tracker ___

[issue38567] urllib.parse.unquote_plus raises incorrect errormessage when string parameter is bytes

New submission from stein-k : urllib.parse.unquote_plus(b'abc%20def') ... TypeError: a bytes-like object is required, not 'str' -- components: Library (Lib) messages: 355242 nosy: stein-k priority: normal severity: normal status: open title: urllib.parse.unquote_plus raises incorrect er

[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support

Charalampos Stratakis added the comment: Have you also tried $ yum install openssl-devel ? That should work without requiring to compile openssl from source, unless you want a later version, which isn't advisable to install system-wide, as it could break other things. -- nosy: +cstr

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

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

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

Carlton Gibson added the comment: Super turn-around. Thank you all. -- resolution: fixed -> status: closed -> open ___ Python tracker ___

[issue38566] Description of '\w' behavior is vague in `re` documentation

New submission from James Gerity : The documentation for the `re` library¹ describes the behavior of the specifier '\w' as matching "Unicode word characters," which is very vague. The closest thing I can find that corresponds to this language is the guidance offered in Unicode Technical Standa

[issue16381] Introduce option to force the interpreter to exit upon MemoryErrors

STINNER Victor added the comment: It is possible to install a custom hook on memory allocators using the PEP 445: see for example attached fatalmalloc.c. I don't see much traction to get this feature since 2013, I reject the feature request. -- resolution: -> rejected stage: patch

[issue32856] Optimize the `for y in [x]` idiom in comprehensions

Josh Rosenberg added the comment: OOC, rather than optimizing a fairly ugly use case, might another approach be to make walrus less leaky? Even if observable leakage is considered desirable, it strikes me that use cases for walrus in genexprs and comprehensions likely break up into: 1. 90%:

[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support

Christian Heimes added the comment: Python uses https://www.gnu.org/software/autoconf-archive/ax_check_openssl.html to detect and check for OpenSSL. Please check config.log for any errors. The log file will contain an error message. How did you compile OpenSSL? Did you configure the sources

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

STINNER Victor added the comment: Yury and Andrew approved my PR 16901, so I merged it. Thanks for the bug report Carlton Gibson. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

miss-islington added the comment: New changeset cbf474c98e702d12c97cd16a1e44ede10ea52b5b by Miss Skeleton (bot) in branch '3.8': bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901) https://github.com/python/cpython/commit/cbf474c98e702d12c97cd16a1e44ede10ea52b5b

[issue34679] asyncio.add_signal_handler call fails if not on main thread

miss-islington added the comment: New changeset cbf474c98e702d12c97cd16a1e44ede10ea52b5b by Miss Skeleton (bot) in branch '3.8': bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901) https://github.com/python/cpython/commit/cbf474c98e702d12c97cd16a1e44ede10ea52b5b

[issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 > alledged missing X509_VERIFY_PARAM_set1_host() support

Malek Ghantous added the comment: I'm having a similar problem. I'm trying to compile on Red Hat 6.9 using a locally installed OpenSSL library. I've tried everything here (I think) and I still get this error: checking for openssl/ssl.h in /home/mf/dp/mpma/ghantousm/apptron/local/... yes

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

STINNER Victor added the comment: New changeset 1b53a24fb4417c764dd5933bce505f5c94249ca6 by Victor Stinner in branch 'master': bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901) https://github.com/python/cpython/commit/1b53a24fb4417c764dd5933bce505f5c94249ca6 -

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

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

[issue34679] asyncio.add_signal_handler call fails if not on main thread

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

[issue34679] asyncio.add_signal_handler call fails if not on main thread

STINNER Victor added the comment: New changeset 1b53a24fb4417c764dd5933bce505f5c94249ca6 by Victor Stinner in branch 'master': bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901) https://github.com/python/cpython/commit/1b53a24fb4417c764dd5933bce505f5c94249ca6 -

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted

STINNER Victor added the comment: What's the status of this issue? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue38564] test_asyncio: test_run_coroutine_threadsafe_with_timeout() has a race condition

Change by STINNER Victor : -- title: test_asyncio: test_run_coroutine_threadsafe_with_timeout() -> test_asyncio: test_run_coroutine_threadsafe_with_timeout() has a race condition ___ Python tracker _

[issue38564] test_asyncio: test_run_coroutine_threadsafe_with_timeout()

STINNER Victor added the comment: I can reproduce the issue with this patch: diff --git a/Lib/test/test_asyncio/test_tasks.py b/Lib/test/test_asyncio/test_tasks.py index dde84b84b1..c94113712a 100644 --- a/Lib/test/test_asyncio/test_tasks.py +++ b/Lib/test/test_asyncio/test_tasks.py @@ -3160,

[issue38564] test_asyncio: test_run_coroutine_threadsafe_with_timeout()

STINNER Victor added the comment: test_run_coroutine_threadsafe_with_timeout() has a race condition. It relies on "await asyncio.sleep(0.05)" synchronization primitive. That's not reliable. async def add(self, a, b, fail=False, cancel=False): """Wait 0.05 second and return a + b."

[issue38565] Expose the value passed of typed passed to functools.lru_cache

New submission from Scott Sanderson : In some circumstances, it's useful to be able in inspect the parameters with which an instance of functools.lru_cache was instantiated. It's currently possible to recover the cache's maxsize via the .cache_info() method, but there's no way to recover the

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

Carlton Gibson added the comment: OK, that seems fair :) Will do that tomorrow AM. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

Carlton Gibson added the comment: Thanks for the speedy patch Victor. Great effort! -- ___ Python tracker ___ ___ Python-bugs-list

[issue37224] test__xxsubinterpreters fails randomly

STINNER Victor added the comment: AMD64 FreeBSD Shared 3.x: https://buildbot.python.org/all/#/builders/371/builds/7 test_subinterpreter (test.test__xxsubinterpreters.IsRunningTests) ... Exception in thread Thread-8: Traceback (most recent call last): File "/usr/home/buildbot/python/3.x.ko

[issue38564] test_asyncio: test_run_coroutine_threadsafe_with_timeout()

New submission from STINNER Victor : AMD64 FreeBSD Shared 3.x: https://buildbot.python.org/all/#/builders/371/builds/7 This buildbot worker is known to be very slow. test_run_coroutine_threadsafe_with_timeout (test.test_asyncio.test_tasks.RunCoroutineThreadsafeTests) Test coroutine submission

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

STINNER Victor added the comment: > Thanks for the speedy patch Victor. Great effort! Can you try to manually test PR 16901? -- ___ Python tracker ___ ___

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

STINNER Victor added the comment: That's basically the same issue than bpo-34679 but on close() rather than on creating the event loop. -- nosy: +vstinner ___ Python tracker

[issue34679] asyncio.add_signal_handler call fails if not on main thread

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

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

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

[issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

Change by STINNER Victor : -- title: Asyncio regression on Windows with Python 3.8 -> ProactorEventLoop.close(): set_wakeup_fd() only works in main thread ___ Python tracker _

[issue20443] __code__. co_filename should always be an absolute path

STINNER Victor added the comment: > This change isn't in Python 3.8 though, it's only in Python 3.9 (the PR merge > date is after the beta 1 branch date). Oh, you're right. Sorry, I thought that I made the change before 3.8 branch was created. In that case, we can do whatever we want :-) (We

[issue20443] __code__. co_filename should always be an absolute path

Nick Coghlan added the comment: This change isn't in Python 3.8 though, it's only in Python 3.9 (the PR merge date is after the beta 1 branch date). Unless it was backported in a Python 3.8 PR that didn't link back to this issue or the original Python 3.9 PR? -- ___

[issue38563] Asyncio regression on Windows with Python 3.8

Andrew Svetlov added the comment: Pull Request is welcome! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38563] Asyncio regression on Windows with Python 3.8

Change by Andrew Svetlov : -- versions: +Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue38563] Asyncio regression on Windows with Python 3.8

Change by Mariusz Felisiak : -- nosy: +Mariusz Felisiak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue38563] Asyncio regression on Windows with Python 3.8

Carlton Gibson added the comment: Reproduce steps, on Windows with Python 3.8.0, and a clean venv. git clone https://github.com/django/asgiref.git cd asgiref pip install -e .[tests] py.test . -- nosy: -Mariusz Felisiak ___ Python tracker

[issue38563] Asyncio regression on Windows with Python 3.8

Change by Mariusz Felisiak : -- nosy: +Mariusz Felisiak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue38555] Undefined behavior in dictreviter_iternext

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

[issue34687] asyncio: is it time to make ProactorEventLoop as the default event loop?

Carlton Gibson added the comment: Created: https://bugs.python.org/issue38563 Thanks! -- ___ Python tracker ___ ___ Python-bugs-l

[issue38563] Asyncio regression on Windows with Python 3.8

New submission from Carlton Gibson : 6ea29c5e90dde6c240bd8e0815614b52ac307ea1 for https://bugs.python.org/issue34687 "Make asynico use ProactorEventLoop by default" This introducesd a regression in asgiref, and hence Django 3.0.x. https://github.com/django/asgiref/issues/132 https://code.d

[issue38555] Undefined behavior in dictreviter_iternext

miss-islington added the comment: New changeset c5d3ea89ee5244714f221dcfcd3be96de2f1da8d by Miss Skeleton (bot) in branch '3.8': bpo-38555: Fix an undefined behavior. (GH-16883) https://github.com/python/cpython/commit/c5d3ea89ee5244714f221dcfcd3be96de2f1da8d -- nosy: +miss-islingto

[issue38555] Undefined behavior in dictreviter_iternext

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

[issue38555] Undefined behavior in dictreviter_iternext

Serhiy Storchaka added the comment: New changeset 2e3d873d3bd0ef4708c4fa06b6cd6972574cb9af by Serhiy Storchaka in branch 'master': bpo-38555: Fix an undefined behavior. (GH-16883) https://github.com/python/cpython/commit/2e3d873d3bd0ef4708c4fa06b6cd6972574cb9af -- _

[issue34687] asyncio: is it time to make ProactorEventLoop as the default event loop?

STINNER Victor added the comment: > (I'm guessing I need to create a new issue?) Please open a new issue. -- ___ Python tracker ___ __

  1   2   >