[issue35100] urllib.parse.unquote_to_bytes: needs "escape plus" option

Change by andrew-g : -- keywords: +patch pull_requests: +12331 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35100> ___ ___ Python-

[issue36517] typing.NamedTuple does not support mixins

New submission from Andrew Wason : Subclassing typing.NamedTuple an inheriting from a mixin class does not work. It does work for collections.namedtuple, and can be worked around by modifying typing.NamedTupleMeta: >>> import collections >>> import typing >>> >&

[issue34139] Remove stale unix datagram socket before binding

Andrew Svetlov added the comment: Done -- nosy: -miss-islington resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue32451] python -m venv activation issue when using cygwin on windows

Andrew Stanton added the comment: I dont think this is a Cygwin only problem, as this is happening to me when running WSL (Windows subsystem for Linux). I can run Scripts\Activate.ps1 from powershell, Scripts\activate.bat from cmd, but running scripts/activate from wsl reports this same

[issue36626] asyncio run_forever blocks indefinitely

Andrew Svetlov added the comment: Callin `self._write_to_self()` from `loop.stop()` should fix your problem. Would you provide a patch? -- ___ Python tracker <https://bugs.python.org/issue36

[issue36626] asyncio run_forever blocks indefinitely

Change by Andrew Svetlov : -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue36626> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36626] asyncio run_forever blocks indefinitely

Andrew Svetlov added the comment: Not sure about `create_task()`. Usually you create tasks from async code, where the `_write_to_self()` call is not needed. Handling writing to self-pipe is not free, starting very many tasks at once can hit performance. Stopping the loop is another beast

[issue36626] asyncio run_forever blocks indefinitely

Andrew Svetlov added the comment: Technically signal handlers are called from main thread, while loop can be executed in another one. *In general* `call_soon_threadsafe()` is the correct solution. Also, it works fine just now with Python 3.5+ Let's close as won&

[issue36626] asyncio run_forever blocks indefinitely

Change by Andrew Svetlov : -- resolution: -> wont fix stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

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

Andrew Svetlov added the comment: Thanks for the report! I see 3 ways to fix the bug: 1. Guard _all_tasks with threading.Lock. It hurts performance significantly. 2. Retry list(_all_tasks) call in a loop if RuntimeError was raised. A chance of collision is very low, the strategy is good

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

Andrew Svetlov added the comment: The fix can be applied to 3.7 and 3.8 only, sorry. Python 3.6 is in security mode now. -- versions: +Python 3.8 -Python 3.6 ___ Python tracker <https://bugs.python.org/issue36

[issue35100] urllib.parse.unquote_to_bytes: needs "escape plus" option

andrew-g added the comment: pinging the issue to try get the PR reviewed -- nosy: +andrew-g ___ Python tracker <https://bugs.python.org/issue35100> ___ ___ Pytho

[issue36651] Asyncio Event Loop documentation inconsistency (call_later and call_at methods)

Change by Andrew Svetlov : -- versions: +Python 3.7 ___ Python tracker <https://bugs.python.org/issue36651> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36651] Asyncio Event Loop documentation inconsistency (call_later and call_at methods)

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

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

Andrew Svetlov added the comment: Sorry, I've missed that the loop has hashable requirement already. Would you prepare a patch for number 3? I am afraid we can add another hard-to-debug multi-threaded problem by complicating the data structure. I'm just curious why do you call

[issue36295] Need to yield (sleep(0)) twice in asyncio

Andrew Svetlov added the comment: In asyncio `await asyncio.sleep(0)` is for switching execution context from the current task to other code. There is no guarantee for finishing already running tasks before returning from `asyncio.sleep(0)` call etc. Also, your code snippet has a logical

[issue35792] Specifying AbstractEventLoop.run_in_executor as a coroutine conflicts with implementation/intent

Andrew Svetlov added the comment: I would rather change the implementation by converting it into async function. It can break some code, sure -- but in a very explicit way (coroutine `run_in_executor is never awaited` error). Making existing third-party code forward-compatible is trivial

[issue18675] Daemon Threads can seg fault

Change by Andrew Svetlov : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue18675> ___ ___

[issue36745] A possible reference leak in PyObject_SetAttr()

Andrew Svetlov added the comment: thanks! -- nosy: +asvetlov resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue34616] implement "Async exec"

Change by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker <https://bugs.python.org/issue34616> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34616] implement "Async exec"

Andrew Svetlov added the comment: I recall the idea of passing a specific flag to `compile()` for accepting await and family on top level of passed code string. Than compile can return a code object with CO_COROUTINE flag set. Returned code object can be analyzed for this flag and executed

[issue36512] future_factory argument for Thread/ProcessPoolExecutor

Andrew Svetlov added the comment: What is your use case? -- nosy: +asvetlov ___ Python tracker <https://bugs.python.org/issue36512> ___ ___ Python-bugs-list m

[issue36341] bind() on AF_UNIX socket may fail in tests run as non-root

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

[issue36613] asyncio._wait() don't remove callback in case of exception

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

[issue24638] asyncio "loop argument must agree with future" error message could be improved

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

[issue24638] asyncio "loop argument must agree with future" error message could be improved

Andrew Svetlov added the comment: New changeset 4737b923df6fbdb9e2bf3fdccea2112270556e0a by Andrew Svetlov (Zackery Spytz) in branch 'master': bpo-24638: Improve the error message in asyncio.ensure_future() (#12848) https://github.com/python/cpyt

[issue32309] Implement asyncio.run_in_executor shortcut

Andrew Svetlov added the comment: In Python 3.7 loop.run_in_executor() is the only user-faced method that requires a loop. asyncio.ThreadPool() sounds great. Maybe thread group can provide better api. But for Python 3.8 adding `run_in_executor` top-level function looks the only easy and

[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: outdated -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36789] Unicode HOWTO incorrectly states that UTF-8 contains no zero bytes

Andrew Svetlov added the comment: This is right for 99.99% cases: utf8 doesn't encode any character except explicit zero with zero bytes. UTF-16 for example encodes 'a' as b'\xff\xfea\x00' -- nosy: +asvetlov _

[issue34616] implement "Async exec"

Andrew Svetlov added the comment: Sorry, I don't know all the compilation workflow details to help you quickly (and will be very busy on other tasks during the sprint). Yuri will be absent on sprints. -- ___ Python tracker &

[issue33530] Implement Happy Eyeball in asyncio

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

[issue36801] Wait for connection_lost in StreamWriter.drain

New submission from Andrew Svetlov : Now `await writer.drain()` performs `await sleep(0)` if underlying transport is closing. It works well only for plain sockets. SSL transport needs more context switches to shut down the SSL connection. Drain wakes up too early to check if the transport is

[issue36801] Wait for connection_lost in StreamWriter.drain

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13011 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36801> ___ ___ Py

[issue36802] Revert back StreamWriter awrite/aclose but provide await writer.write() and await writer.close()

New submission from Andrew Svetlov : Yuri and I decided that `writer.awrite()` and `writer.aclose()` look ugly. Instead, we return awaitable object from these methods to allow both `writer.write(b'data')` and `await writer.write(b'data')` for the method. The same for `

[issue36802] Revert back StreamWriter awrite/aclose but provide await writer.write() and await writer.close()

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13012 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36802> ___ ___ Py

[issue36801] Wait for connection_lost in StreamWriter.drain

Change by Andrew Svetlov : -- versions: +Python 3.7 ___ Python tracker <https://bugs.python.org/issue36801> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36805] Don't close subprocess stream if it's stdin is closed

New submission from Andrew Svetlov : Closing stdin FD by child stream is a legal operation, there is no reason to close entire subprocess transport immediately. -- components: asyncio messages: 341467 nosy: asvetlov, yselivanov priority: normal severity: normal status: open title

[issue36806] Forbid creating of stream objects outside of asyncio

New submission from Andrew Svetlov : They were intended to be used by asyncio factories like open_connection from the very beginning but internals was leaked into asyncio top-level namespace. The idea is: 1. provide `_asyncio_internal` keyword-only parameter to leaked classes constructor 2

[issue36806] Forbid creating of stream objects outside of asyncio

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13014 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36806> ___ ___ Py

[issue36790] test_asyncio fails with application verifier!

Change by Andrew Svetlov : -- components: +asyncio ___ Python tracker <https://bugs.python.org/issue36790> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36806] Forbid creating of stream objects outside of asyncio

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

[issue36794] asyncio.Lock documentation in Py3.8 lacks parts presented in documentation in Py3.6

Andrew Svetlov added the comment: I would say that unblock order is an implementation detail (which is unlikely be changed though). I'm biased how should we document it. Yuri, your opinion is very welcome. -- ___ Python tracker &

[issue35125] asyncio shield: remove inner callback on outer cancellation

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 ___ Python tracker <https://bugs.python.or

[issue36840] Add stream.abort() async method

New submission from Andrew Svetlov : It should call underlying `transport.abort()`, then wait for closing event (`await self.wait_closed()`) -- components: asyncio messages: 341811 nosy: asvetlov, yselivanov priority: normal severity: normal status: open title: Add stream.abort

[issue34616] implement "Async exec"

Andrew Svetlov added the comment: Matthias, please use GH-13148 for pointing on github pull requests. # is for links to this tracker issues. -- stage: patch review -> ___ Python tracker <https://bugs.python.org/issu

[issue36801] Wait for connection_lost in StreamWriter.drain

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

[issue36840] Add stream.abort() async method

Andrew Svetlov added the comment: The reason is: until connection_lost() is called the transport is in the active state. Destruction of closing-but-not-closed-yet trasport raises a ResourceWarning. Plain TCP socket calls connection_lost() on the next loop iteration after .abort() call

[issue36802] Revert back StreamWriter awrite/aclose but provide await writer.write() and await writer.close()

Andrew Svetlov added the comment: New changeset a076e4f5e42b85664693191d04cfb33e2f9acfa5 by Andrew Svetlov in branch 'master': bpo-36802: Drop awrite()/aclose(), support await write() and await close() instead (#13099) https://github.com/python/cpyt

[issue36802] Revert back StreamWriter awrite/aclose but provide await writer.write() and await writer.close()

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

[issue36884] DeprecationWarning in test_asyncio.test_pep492.StreamReaderTests.test_readline

Andrew Svetlov added the comment: Nice catch! -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36512] future_factory argument for Thread/ProcessPoolExecutor

Andrew Svetlov added the comment: Sorry, but in the provided snippet I see a class with an interface which looks close to executor. There is no clear relationship with standard executors (e.g. is it inherited from ThreadExecutor?). Proposed `future_factory` is also absent. Please, provide

[issue36889] Merge StreamWriter and StreamReader into just asyncio.Stream

New submission from Andrew Svetlov : The separation was a bad idea, sorry. Both classes are coupled too much. 1. Writer should know about the reader to make `drain()` work 2. Reader has no .close() method. The idea is: 1. Merge StreamReader and StreamWriter into just a Stream. 2. The Stream

[issue36889] Merge StreamWriter and StreamReader into just asyncio.Stream

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13162 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36889> ___ ___ Py

[issue34975] start_tls() difficult when using asyncio.start_server()

Andrew Svetlov added the comment: I believe stream transport should be replaced. If you have time please do this change. Also please take a look at #36889 for merging StreamWriter and StreamReader. It can simplify the replacement strategy. Anyway, please keep your PR open at least. The plan

[issue36780] Interpreter exit blocks waiting for futures of shut-down ThreadPoolExecutors

Andrew Svetlov added the comment: Should wait_on_exit be True only on application exit? Do application exit means interpreter shutdown (sys.is_finalizing() == True)? -- nosy: +asvetlov ___ Python tracker <https://bugs.python.org/issue36

[issue36780] Interpreter exit blocks waiting for futures of shut-down ThreadPoolExecutors

Andrew Svetlov added the comment: As documentation reader I have a mental problem to figure out when use non-default `wait_at_exit=False` flag and when don't. The rule like: "if you tried to call `executor.shutdown(wait=False)` and it still hangs try `executor.shutdown(

[issue36916] Swallow unhandled exception report introduced by 36802

New submission from Andrew Svetlov : In #36802 when old-style writer.write() is used without awaiting and an exception is raised from writer.drain() method asyncio reports about the unhandled exception. The proposed fix adds a done callback to task for swallowing the exception in such case

[issue36916] Swallow unhandled exception report introduced by 36802

Change by Andrew Svetlov : -- components: +Library (Lib), asyncio nosy: +yselivanov type: -> behavior versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issu

[issue36916] Swallow unhandled exception report introduced by 36802

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13223 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36916> ___ ___ Py

[issue36790] test_asyncio fails with application verifier!

Andrew Svetlov added the comment: What is "Application Verifier"? Could you provide an instruction on how to install and run it to reproduce the issue? -- ___ Python tracker <https://bugs.python.o

[issue36870] test_asyncio: test_drain_raises() fails randomly on Windows

Andrew Svetlov added the comment: Please postpone the reversion for a while. I think #36916 fixes a message about the never retrieved exception. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36870] test_asyncio: test_drain_raises() fails randomly on Windows

Andrew Svetlov added the comment: Agree with your conclusion -- ___ Python tracker <https://bugs.python.org/issue36870> ___ ___ Python-bugs-list mailin

[issue36801] Wait for connection_lost in StreamWriter.drain

Andrew Svetlov added the comment: Looks like the change introduced by the PR is not stable at least on Windows boxes -- resolution: fixed -> stage: resolved -> status: closed -> open ___ Python tracker <https://bugs.python.or

[issue36801] Wait for connection_lost in StreamWriter.drain

Change by Andrew Svetlov : -- pull_requests: +13242 ___ Python tracker <https://bugs.python.org/issue36801> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36801] Wait for connection_lost in StreamWriter.drain

Andrew Svetlov added the comment: New changeset 54b74fe9df89f0e5646736f1f60376b4e37c422c by Andrew Svetlov in branch 'master': bpo-36801: Temporarily fix regression in writer.drain() (#13330) https://github.com/python/cpython/commit/54b74fe9df89f0e5646736f1f60376

[issue36916] Swallow unhandled exception report introduced by 36802

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

[issue36921] Deprecate yield from and @coroutine in asyncio

Change by Andrew Svetlov : -- components: asyncio nosy: asvetlov, yselivanov priority: normal severity: normal status: open title: Deprecate yield from and @coroutine in asyncio versions: Python 3.8 ___ Python tracker <https://bugs.python.

[issue36921] Deprecate yield from and @coroutine in asyncio

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +13246 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36921> ___ ___ Py

[issue36921] Deprecate yield from and @coroutine in asyncio

Change by Andrew Svetlov : -- pull_requests: +13257 ___ Python tracker <https://bugs.python.org/issue36921> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35589] BaseSelectorEventLoop.sock_sendall() performance regression: extra copy of data

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

[issue32528] Change base class for futures.CancelledError

Andrew Svetlov added the comment: Inheritance from Exception is very annoying, I saw issues with unexpected suppressing CancelledError many times. Even experienced people constantly forget to add a separate `except asyncio.CancelledError` clause everywhere. But proposed change is backward

[issue32528] Change base class for futures.CancelledError

Andrew Svetlov added the comment: Honestly I have no strong opinion. Correct code should not be affected, if somebody want to handle task cancellation explicitly -- he already have `except CancelledError` in his code. What are use cases for intentional catching Exception for task

[issue32564] Syntax error on using variable async

New submission from Andrew Olefira : In python 3.6 you can use name "async" for variable: >>> class A: ... async = True ... >>> but in python 3.7a4 you catch syntax error: >>> class A: ... async = True File "", line 2 async

[issue32564] Syntax error on using variable async

Andrew Olefira added the comment: Yes, I understand, but "not recommended" != "not allowed". For example library Pika (https://pypi.python.org/pypi/pika) use variable "async", so no one project that use lib Pika can

[issue32564] Syntax error on using variable async

Change by Andrew Olefira : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue32564> ___ ___

[issue32410] Implement loop.sock_sendfile method

Andrew Svetlov added the comment: New changeset 6b5a27975a415108a5eac12ee302bf2b3233f4d4 by Andrew Svetlov in branch 'master': bpo-32410: Implement loop.sock_sendfile() (#4976) https://github.com/python/cpython/commit/6b5a27975a415108a5eac12ee302bf

[issue32410] Implement loop.sock_sendfile method

Change by Andrew Svetlov : -- pull_requests: +5088 ___ Python tracker <https://bugs.python.org/issue32410> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32311] Implement asyncio.create_task() shortcut

Change by Andrew Svetlov : -- pull_requests: +5089 ___ Python tracker <https://bugs.python.org/issue32311> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32410] Implement loop.sock_sendfile method

Andrew Svetlov added the comment: New changeset 7464e87a6511d3626b04c9833a262a77b1f21e23 by Andrew Svetlov in branch 'master': bpo-32410: Make SendfileNotAvailableError exception public (#5243) https://github.com/python/cpython/commit/7464e87a6511d3626b04c9833a262a

[issue32410] Implement loop.sock_sendfile method

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

[issue32472] Mention of __await__ missing in Coroutine Abstract Methods

Change by Andrew Svetlov : -- resolution: not a bug -> stage: resolved -> status: closed -> open ___ Python tracker <https://bugs.python.org/issue32472> ___ ___

[issue32610] asyncio.all_tasks() should return only non-finished tasks.

New submission from Andrew Svetlov : Current behavior has a subtle pitfall. The function returns a list of *existing* tasks (not removed by decref or explicit call). If user's code has a strong reference to some task the task will be in return list for unpredictable amount of time, even i

[issue32458] test_asyncio failures on Windows

Andrew Svetlov added the comment: Hmm, the scheduled call was executed sooner than expected. Actually we had 0.1 sec delay, checked for at least 0.08 but actual call time was 0.078 BTW I recall an issue with Windows when call_later() was executed sooner already

[issue32622] Implement loop.sendfile

Change by Andrew Svetlov : -- components: asyncio nosy: asvetlov, yselivanov priority: normal severity: normal status: open title: Implement loop.sendfile versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue32

[issue32622] Implement loop.sendfile

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +5115 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue32622> ___ ___ Py

[issue32624] Implement WriteTransport.is_protocol_paused()

New submission from Andrew Svetlov : The method should return True is write is suspended -- components: asyncio messages: 310439 nosy: asvetlov, yselivanov priority: normal severity: normal status: open title: Implement WriteTransport.is_protocol_paused() versions: Python 3.7

[issue32391] Add StreamWriter.wait_closed()

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +5127 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue32391> ___ ___ Py

[issue32633] Warnings from test_asyncio.test_tasks.SetMethodsTest

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

[issue32633] Warnings from test_asyncio.test_tasks.SetMethodsTest

Andrew Svetlov added the comment: New changeset 6934831e43d66222a626403dd775429d1c8963f3 by Andrew Svetlov (Nathaniel J. Smith) in branch 'master': bpo-32633: Fix some warnings in test_asyncio.test_tasks (#5280) https://github.com/python/cpython/commit/6934831e43d66222a626403dd77542

[issue32410] Implement loop.sock_sendfile method

Change by Andrew Svetlov : -- pull_requests: +5141 stage: resolved -> patch review ___ Python tracker <https://bugs.python.org/issue32410> ___ ___ Python-

[issue32650] Debug support for native coroutines is broken

New submission from Andrew Svetlov : pdb (and other Python debuggers) are built on top of bdb.py module. The module has a support for stepping to next line in function (next command). The command checks frame flags and do extra steps if the flags contains CO_GENERATOR. But CO_COROUTINE is

[issue32410] Implement loop.sock_sendfile method

Andrew Svetlov added the comment: New changeset 0a5e71b4c70aab87125a54d7a59765e18d7583a4 by Andrew Svetlov in branch 'master': bpo-32410: Improve sock_sendfile tests (#5294) https://github.com/python/cpython/commit/0a5e71b4c70aab87125a54d7a59765

[issue32410] Implement loop.sock_sendfile method

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

[issue32391] Add StreamWriter.wait_closed()

Andrew Svetlov added the comment: New changeset fe133aad5949db7309c26c58b066c22e714e by Andrew Svetlov in branch 'master': bpo-32391: Implement StreamWriter.wait_closed() (#5281) https://github.com/python/cpython/commit/fe133aad5949db7309c26c58b0

[issue32391] Add StreamWriter.wait_closed()

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

[issue32622] Implement loop.sendfile

New submission from Andrew Svetlov : New changeset 7c684073f951dd891021676ecfd86ffc18b8895e by Andrew Svetlov in branch 'master': bpo-32622: Implement loop.sendfile() (#5271) https://github.com/python/cpython/commit/7c684073f951dd891021676ecfd86f

[issue32622] Implement loop.sendfile

Change by Andrew Svetlov : -- pull_requests: +5210 ___ Python tracker <https://bugs.python.org/issue32622> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32650] Debug support for native coroutines is broken

Andrew Svetlov added the comment: New changeset 46877024423e98d1b872bf308dacacd583327207 by Andrew Svetlov (Pablo Galindo) in branch 'master': bpo-32650: Add native coroutine support to bdb when stepping over line (GH-5400) https://github.com/python/cpyt

[issue32650] Debug support for native coroutines is broken

Andrew Svetlov added the comment: New changeset 543ec005a4c83fcc0d14ac1e4c0f1a36bf84640b by Andrew Svetlov (Miss Islington (bot)) in branch '3.6': bpo-32650: Add native coroutine support to bdb when stepping over line (GH-5400) (#5402) https://github.com/python/cpyt

[issue32650] Debug support for native coroutines is broken

Change by Andrew Svetlov : -- pull_requests: +5244 ___ Python tracker <https://bugs.python.org/issue32650> ___ ___ Python-bugs-list mailing list Unsubscribe:

<    12   13   14   15   16   17   18   19   20   21   >