Justin Arthur added the comment:
> So the behaviour you describe will happen anyway.
Unless we make your change against the 3.9 branch, in which case the fix will
make it into the 3.9.x series of patch releases.
--
___
Python tracker
<
Justin Arthur added the comment:
I believe the documentation may be referring to the English set and not a
Python set, but I could be wrong.
Yury changed the wording from sequence to set in 3.7, but we didn't document a
breaking change as far as I know. The purpose of those set
Justin Arthur added the comment:
Your change makes perfect sense to me. It would be a backport-only change as
the 2nd set creation is actually getting removed for the development version
(3.10) to finalize the deprecation of wait's coroutine scheduling.
--
nosy: +JustinTArthur
Justin Arthur added the comment:
The "'NoneType' object has no attribute 'close'" error is likely caused by a
race against the loop calling the test protocol object's connection_made
callback. I was able to reproduce this case occasionally on macOS and it's
likely platform-agnos
Change by Justin Arthur :
--
nosy: +JustinTArthur
nosy_count: 5.0 -> 6.0
pull_requests: +21662
pull_request: https://github.com/python/cpython/pull/22691
___
Python tracker
<https://bugs.python.org/issu
Change by Justin Arthur :
--
versions: +Python 3.10 -Python 3.8
___
Python tracker
<https://bugs.python.org/issue33533>
___
___
Python-bugs-list mailin
Change by Justin Arthur :
--
title: Provide an async-generator version of as_completed -> Provide an async
iterator version of as_completed
___
Python tracker
<https://bugs.python.org/issu
Justin Arthur added the comment:
Thanks, Hrvoje. I've updated the patch to match this bug's suggested format and
have updated the documentation and What's New.
The one quirk that comes with the benefit of getting the same futures back is
that we still allow both coroutines and futures
Justin Arthur added the comment:
Not sure if there is consensus on how to fix, but fixing #12731 will fix this
for most of the cases I've seen complaints about as a side effect.
--
___
Python tracker
<https://bugs.python.org/issue38
Justin Arthur added the comment:
I've added a new PR, PR 22491. This one has as_completed returning an iterator
and includes tests for both the old and new style.
I see a trivial amount of latency added in extra call stack over Guido's
original implementation. Should we decide to deprecate
Change by Justin Arthur :
--
nosy: +JustinTArthur
nosy_count: 5.0 -> 6.0
pull_requests: +21508
pull_request: https://github.com/python/cpython/pull/22491
___
Python tracker
<https://bugs.python.org/issu
Change by Justin Arthur :
--
nosy: +JustinTArthur
___
Python tracker
<https://bugs.python.org/issue12731>
___
___
Python-bugs-list mailing list
Unsubscribe:
Justin Arthur added the comment:
Ned, can you confirm that 2to3 is not intended for cumulative/incremental runs
over the same codebase?
If it's not intended to be run on previously ported code, this will just need
to be fixed on the lib2to3 downstream projects like awpa and Black
New submission from Justin ARthur :
Python 3 code with an identifier that has a non-spacing mark in it does not get
tokenized by lib2to3 and will result in an exception thrown in the parsing
process.
Parsing the attached file (badvar.py), results in `ParseError: bad token:
type=58, value
14 matches
Mail list logo
