Changes by Yury Selivanov :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
Changes by Yury Selivanov :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue29742>
___
___
Yury Selivanov added the comment:
> AttributeError: Can't pickle local object 'WeakSet.__init__.._remove'
Well, I don't think we can do something about it. Just re-pack your arguments
from WeakSet to a regular set.
--
__
Yury Selivanov added the comment:
> I am wondering how much of other uses of PyErr_SetObject() are affected by
> similar bugs?
Only when we use an exception to carry a return value. AFAIK StopIteration is
the only such case.
--
___
Python t
Yury Selivanov added the comment:
Maybe a better way would be to proceed with http://bugs.python.org/issue16500?
--
nosy: +yselivanov
___
Python tracker
<http://bugs.python.org/issue29
Yury Selivanov added the comment:
BTW, why can't you use `pthread_atfork` in numpy?
--
___
Python tracker
<http://bugs.python.org/issue29828>
___
___
Pytho
Yury Selivanov added the comment:
New changeset db522dc86294a99f46a63cd5b54c7c4ab8017c96 by Yury Selivanov in
branch '3.5':
bpo-29742: asyncio get_extra_info() throws exception (#525) (#646)
https://github.com/python/cpython/commit/db522dc86294a99f46a63cd5b54c7c
Yury Selivanov added the comment:
New changeset 2b27e2e6a35c3d3e369612b984017fe0d1bfcf0c by Yury Selivanov
(Nikolay Kim) in branch 'master':
bpo-29742: asyncio get_extra_info() throws exception (#525)
https://github.com/python/cpython/commit/2b27e2e6a35c3d3e369612b984017f
Yury Selivanov added the comment:
New changeset 99f8d33a94c8951fd6b2d5f079d20be698150993 by Yury Selivanov in
branch '3.6':
bpo-29742: asyncio get_extra_info() throws exception (#525) (#645)
https://github.com/python/cpython/commit/99f8d33a94c8951fd6b2d5f079d20b
Yury Selivanov added the comment:
New changeset f7f024a721d53978d03129e8eb5111d4f74534a9 by Yury Selivanov (Seth
M. Larson) in branch '3.5':
bpo-29704: Fix asyncio.SubprocessStreamProtocol closing (#405)
https://github.com/python/cpython/commit/f7f024a721d53978d03129e8eb5111
Yury Selivanov added the comment:
New changeset 604faba1db724951ee440337099d111e3ecade49 by Yury Selivanov (Seth
M. Larson) in branch '3.6':
bpo-29704: Fix asyncio.SubprocessStreamProtocol closing (#405)
https://github.com/python/cpython/commit/604faba1db724951ee440337099d11
Yury Selivanov added the comment:
New changeset 84af903f3bc6780cb4e73ff05ad2e242d3966417 by Yury Selivanov in
branch 'master':
bpo-28963: Fix out of bound iteration in asyncio.Future.remove_done_callback/C
(#408)
https://github.com/python/cpyt
Yury Selivanov added the comment:
New changeset 481cb70a724687d12553d38a749c16034af68a1e by Yury Selivanov (Seth
M. Larson) in branch 'master':
bpo-29704: Fix asyncio.SubprocessStreamProtocol closing (#405)
https://github.com/python/cpython/commit/481cb70a724687d12553d38a749c16
Yury Selivanov added the comment:
New changeset 8b73b6198bc0753c5ce6e8f91eb7bddc2bd42a73 by Yury Selivanov in
branch '3.5':
bpo-29703: asyncio: Fix creating new event loops in child processes. (#411)
https://github.com/python/cpython/commit/8b73b6198bc0753c5ce6e8f91eb7bd
Yury Selivanov added the comment:
New changeset 01e5230ef0b28658cf7311be199363eda98808bd by Yury Selivanov in
branch '3.6':
bpo-29703: asyncio: Fix creating new event loops in child processes. (#404)
(#410)
https://github.com/python/cpython/commit/01e5230ef0b28658cf7311be199363
Yury Selivanov added the comment:
New changeset 8d26aa930c0123933a1ceb12fceba4f5aef4e95e by Yury Selivanov in
branch 'master':
bpo-29271: Fix Task.current_task and Task.all_tasks to accept None. (#406)
https://github.com/python/cpython/commit/8d26aa930c0123933a1ceb12fceba4
Yury Selivanov added the comment:
New changeset 398ff91ac0b8f4d930cd5d9e3e6a4bf247f810ef by Yury Selivanov in
branch 'master':
bpo-28893: Set __cause__ for errors in async iteration protocol (#407)
https://github.com/python/cpython/commit/398ff91ac0b8f4d930cd5d9e3e6a4b
Yury Selivanov added the comment:
New changeset ba7e1f9a4e06c0b4ad594fd64edcaf7292515820 by Yury Selivanov in
branch 'master':
bpo-29703: asyncio: Fix creating new event loops in child processes. (#404)
https://github.com/python/cpython/commit/ba7e1f9a4e06c0b4ad594fd64edcaf
Yury Selivanov added the comment:
Yeah, we can fix this. However, I don't want to push the fix to 3.6, too much
code uses this function now. So it's going to be 3.7 only.
--
assignee: -> yselivanov
versions: +Python 3.7 -Python 3.6
_
Yury Selivanov added the comment:
> This is a specific example of the general problem reported in issue 25538.
It's a bit different code path/problem. But I agree, we should work on making
both `with` and `async with` a bit more usable.
> Would it be possible to change this so i
Changes by Yury Selivanov :
--
resolution: duplicate ->
stage: resolved -> needs patch
status: closed -> open
___
Python tracker
<http://bugs.python.or
Yury Selivanov added the comment:
> Would it maybe make sense to implement this as adding an argument to
> GET_AWAITABLE to indicate whether it was called from await, __anext__,
> __aenter__ or __aexit__?
Yes, but it will make it a tad slower (which will also affect await
performanc
Yury Selivanov added the comment:
I'm assigning this to myself to make sure I don't forget about this. If someone
wants to tackle this please feel free to reassign.
--
assignee: -> yselivanov
versions: +Python 3.7
___
Python t
Yury Selivanov added the comment:
Interesting. It doesn't work for both C and Python versions of the Task. I'll
take a look in detail when I return from vacation.
--
assignee: -> yselivanov
nosy: +inada.naoki
___
Python t
Yury Selivanov added the comment:
In Evgeny's example the 'task' is 'coro1' (not 'coro2'). It has plenty of yield
points after being cancelled.
--
___
Python tracker
Yury Selivanov added the comment:
`asyncio.run_coroutine_threadsafe` was't designed to be compatible with
`asyncio.ensure_future`. It should be used to run a coroutine in an event loop
from another thread. You shouldn't need to await on the future
Yury Selivanov added the comment:
> A verbose error like this one would have made this behavior more clear to me.
Well, it already raises a TypeError with a clear message -- this is how we tell
the user that the argument type is not supported in Python. I don't think we
need to sp
Yury Selivanov added the comment:
> This is more to my point: I found the TypeError message not clear at all.
> From my prospective, I was using a future object returned from an asyncio
> function to call another asyncio function, yet that function was telling me
> it could only
Yury Selivanov added the comment:
> - I wonder how much self-reporting will be done here.
Yeah, I don't think we see enough reporting on bugs.python.org. I hope people
will become more vocal :) I try to monitor what people say about asyncio on
SO, Twitter and /r/python to get
Yury Selivanov added the comment:
Yes, this is a very longstanding open issue. I've already discussed this with
Guido many times, and even found someone to help us. Will try to kickstart the
project this weekend.
--
___
Python tracker
Yury Selivanov added the comment:
> The problem is that Python stdlib is quite limited: no HTTP, no SQL client,
etc. An external tutorial can use 3rd party modules like aiohttp.
Even without aiohttp we can show how to use asyncio correctly. I agree with
Mariatta that we should have a tutor
Yury Selivanov added the comment:
New changeset 2e624690bd74071358566300b7ef0bc45f444a30 by Yury Selivanov (Jelle
Zijlstra) in branch 'master':
bpo-29679: Implement @contextlib.asynccontextmanager (#360)
https://github.com/python/cpython/commit/2e624690bd74071358566300b7ef0b
Yury Selivanov added the comment:
> Is there any reason that the second case Terry provide still will failed with
> ValueError?
> class C:
>def meth2(**kwds): pass
> ip.signature(C().meth2)
Yes, the reason is that `C().meth2` is an invalid method that can't be cal
Changes by Yury Selivanov :
--
nosy: -yselivanov
___
Python tracker
<http://bugs.python.org/issue19903>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
Overall, the approach looks fine. Alexander, do you want to make a PR to start
working on adding this to 3.7?
--
versions: -Python 3.6
___
Python tracker
<http://bugs.python.org/issue29
Yury Selivanov added the comment:
New changeset 378d70642aa1c8de2a53ecb811927faf0388db2d by Yury Selivanov
(Dong-hee Na) in branch 'master':
bpo-30149: Fix partialmethod without explicit self parameter (#1308)
https://github.com/python/cpython/commit/378d70642aa1c8de2a53ecb811927f
Yury Selivanov added the comment:
New changeset ab4413a7e9bda95b6fcd517073e2a51dafaa1624 by Yury Selivanov
(Nathaniel J. Smith) in branch 'master':
bpo-30039: Don't run signal handlers while resuming a yield from stack (#1081)
https://github.com/python
Yury Selivanov added the comment:
Yes, I'll do the backport.
--
___
Python tracker
<http://bugs.python.org/issue30039>
___
___
Python-bugs-list mailing list
Changes by Yury Selivanov :
--
pull_requests: +1735
___
Python tracker
<http://bugs.python.org/issue30039>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
> Since the limit is arbitrary anyway, sys.getrecursionlimit() seems like a
> reasonable choice.
The recursion limit can be changed for whatever purposes and I'm not sure that
it's a good idea that it will affect unwrap behaviour in such cas
Yury Selivanov added the comment:
> I'd be fine with replacing the sys.getrecursionlimit() call with a module
> level constant like "_UNWRAP_LIMIT = 500".
TBH I'm OK either way.
`sys.getrecursionlimit()` is 1000 (at least on my machine), which might be a
bit too
Yury Selivanov added the comment:
> I don't see a better way to handle my (admittedly a bit weird) control-C case
> within the interpreter
I'm not sure I understand how `f_func` would help to better handle Control-C in
Trio. Nathaniel, could you please e
Yury Selivanov added the comment:
> Sure. The issue is that I need to mark certain frames as "protected" from
> KeyboardInterrupt, in a way that my signal handler can see when walking the
> frame stack, so it can decide whether to raise a KeyboardInterrupt
> immediat
Yury Selivanov added the comment:
A while ago, Eric Appelt stepped forward to help with the asyncio
documentation. Here's my response to his email in which we discuss
the direction for the new docs.
On May 24, 2017 at 1:04:56 PM, Eric Appelt (eric.app...@gmail.com) wrote:
> Hi Yury
Yury Selivanov added the comment:
I'm not sure we want this to be in asyncio: it's a very high-level object
somewhere in between the low-level and the application level. Some things off
the top of my head that users will want from this API:
- detailed logging or hooks to implement
Yury Selivanov added the comment:
Yes, this is a known problem to me, thank you for creating the issue. Will work
on a fix soon.
--
___
Python tracker
<http://bugs.python.org/issue30
Yury Selivanov added the comment:
> STINNER Victor added the comment:
>
> Barry: would you be ok to start by adding Controller to asyncio.test_utils,
> and wait later to expose it in the public API?
Sorry, but we are going to deprecate and remove test_utils soon. It's a bunch
Yury Selivanov added the comment:
> There's also value in doing one simple thing that adds convenience for users.
> I don't personally have any interest in building something as elaborate as the
> above, but I've used the simple idea here several times in different proje
Yury Selivanov added the comment:
> I appreciate that you want to be careful not to saddle asyncio with too much
> baggage, or that you don't feel Controller is significant enough to generalize
> and put in the package. Perhaps a middle ground would be to label parts of
>
Yury Selivanov added the comment:
I've created a repo for discussing and making next version of asyncio docs:
https://github.com/asyncio-docs/cpython-aiodocs. Feel free to join!
--
___
Python tracker
<http://bugs.python.org/is
Yury Selivanov added the comment:
I propose to start using the issues [1] as there are so many topics we'll have
to discuss. Feel free to create new issue for whatever idea you have!
[1] https://github.com/asyncio-docs/cpython-aiodocs/i
Yury Selivanov added the comment:
> I can experiment with memcached as well but I think this proposal is a good
> idea and would work well with Redis.
I like it! Let's use Redis as an example. Please open an issue at asyncio-docs
to discuss
Changes by Yury Selivanov :
--
pull_requests: +2101
___
Python tracker
<http://bugs.python.org/issue27585>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
New changeset 7be651c7aad8e4d46012205811b58ef127b08e0e by Yury Selivanov in
branch 'master':
bpo-27585: Add a NEWS entry for #1031 (#2036)
https://github.com/python/cpython/commit/7be651c7aad8e4d46012205811b58e
Changes by Yury Selivanov :
--
pull_requests: +2102
___
Python tracker
<http://bugs.python.org/issue27585>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2103
___
Python tracker
<http://bugs.python.org/issue27585>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
New changeset e89f95bfd0881a9b80c3b1430d154a77bdf5a824 by Yury Selivanov in
branch '3.6':
[3.6] bpo-30039: Don't run signal handlers while resuming a yield from stack
(GH-1081) (#1640)
https://github.com/python
Changes by Yury Selivanov :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> behavior
___
Python tracker
<http://bugs.python
Changes by Yury Selivanov :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
versions: +Python 3.5, Python 3.7
___
Python tracker
<http://bugs.python.or
Yury Selivanov added the comment:
I don't think we need to. Isn't 3.5 is in security/important bug fix mode? I
don't view this change as an important one (it's just a nice thing to have).
--
___
Python tracker
<http://bug
Changes by Yury Selivanov :
--
pull_requests: +2106
___
Python tracker
<http://bugs.python.org/issue29743>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2107
___
Python tracker
<http://bugs.python.org/issue29743>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
> There are two PRs for this issue. Is one depending on the other?
No, they all address slightly different bugs. All need to be merged though.
> PR 409 has merge conflict that needs to be resolved.
Yes, it seems that it's based on 3.6 branch.
Changes by Yury Selivanov :
--
pull_requests: +2109
___
Python tracker
<http://bugs.python.org/issue29870>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
> It sounds like a bug to me, and thus suitable to backport, but it certainly
> would be worth getting other opinions since this is a tricky and critical
> area.
I think it's safe to mer
Yury Selivanov added the comment:
Merged. Thank you Nikolay!
--
nosy: +yselivanov
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Yury Selivanov :
--
pull_requests: +2110
___
Python tracker
<http://bugs.python.org/issue29870>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2111
___
Python tracker
<http://bugs.python.org/issue29870>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2112
___
Python tracker
<http://bugs.python.org/issue30508>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2121
___
Python tracker
<http://bugs.python.org/issue29905>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2122
___
Python tracker
<http://bugs.python.org/issue29905>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
New changeset a608d2d5a7f1aabe9bcbfc220135c5e126189390 by Yury Selivanov
(Nikolay Kim) in branch 'master':
bpo-29406: asyncio SSL contexts leak sockets after calling close with certain
servers (#409)
https://github.com/python/cpyt
Changes by Yury Selivanov :
--
pull_requests: +2124
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2125
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
New changeset 6e14fd2a14cef6ea0709ad234ab41198c2195591 by Yury Selivanov in
branch '3.6':
[3.6] bpo-29406: asyncio SSL contexts leak sockets after calling close with
certain servers (GH-409) (#2062)
https://github.com/python/cpyt
Yury Selivanov added the comment:
New changeset 1395c58ef7b98f087d1d5d50962fe7a8c032f34d by Yury Selivanov in
branch '3.5':
[3.5] bpo-29406: asyncio SSL contexts leak sockets after calling close with
certain servers (GH-409) (#2063)
https://github.com/python/cpyt
Yury Selivanov added the comment:
Nikolay, can you please take a look?
--
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailin
Yury Selivanov added the comment:
> yes, i am on it
Nick, have you been able to find what the problem is? If not, we'll need to
pull this change out of 3.6.2.
--
___
Python tracker
<http://bugs.python.org
Yury Selivanov added the comment:
> > yes, i am on it
> Nick, have you been able to find what the problem is? If not, we'll need to
> pull this change out of 3.6.2.
It's interesting to see how `_process_write_backlog` gets called after
`_finalize`. One option wo
Yury Selivanov added the comment:
> It's interesting to see how `_process_write_backlog` gets called after
> `_finalize`. One option would be to simply guard `transport.write` with `if
> transport is not None`, but I'm afraid that we'll only mask the bug then.
OTO
Changes by Yury Selivanov :
--
pull_requests: +2162
___
Python tracker
<http://bugs.python.org/issue30508>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2163
___
Python tracker
<http://bugs.python.org/issue30508>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
New changeset 7ce1c6fb579a01bb184224a10019039fde9c8eaf by Yury Selivanov in
branch 'master':
bpo-30508: Don't log exceptions if Task/Future "cancel()" method called (#2050)
https://github.com/python/cpython/commit/7ce1c6fb579a01b
Yury Selivanov added the comment:
New changeset 176f2ebdad93f20876c08efabd364a0e6c86de14 by Yury Selivanov in
branch '3.6':
bpo-30508: Don't log exceptions if Task/Future "cancel()" method was called.
(#2109)
https://github.com/python/cpython/commit/176f2ebdad93f20
Yury Selivanov added the comment:
New changeset d24c8287e226ac9983caf6bb826a7b53142ee31f by Yury Selivanov in
branch '3.5':
bpo-30508: Don't log exceptions if Task/Future "cancel()" method was called.
(#2110)
https://github.com/python/cpython/commit/d24c8287e226ac9
Yury Selivanov added the comment:
Fixed. Ned, this will be included in 3.6.2, right?
--
nosy: +ned.deily
resolution: -> fixed
stage: -> resolved
status: open -> closed
versions: +Python 3.7
___
Python tracker
<http://bugs.python.or
Changes by Yury Selivanov :
--
pull_requests: +2164
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2165
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yury Selivanov :
--
pull_requests: +2166
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yury Selivanov added the comment:
Alright, let's play it safe. I'm going to be reverting the change from all
branches. Nick, if you are able to figure this out please create a new PR.
--
___
Python tracker
<http://bugs.python.o
Yury Selivanov added the comment:
New changeset 09663de203396b28483a570bb268c130b59639cf by Yury Selivanov in
branch 'master':
Revert "bpo-29406: asyncio SSL contexts leak sockets after calling close with
certain servers (#409)" (#2111)
https://github.com/p
Yury Selivanov added the comment:
New changeset 4e9dfe214dff000c5b5ad0d8bd8a393feed1d3cf by Yury Selivanov in
branch '3.5':
Revert "[3.5] bpo-29406: asyncio SSL contexts leak sockets after calling close
with certain servers (GH-409) (#2063)" (#2113)
https://github.com/p
Yury Selivanov added the comment:
New changeset 83d30bd667924549bacf1428ac3e475cdf9792ae by Yury Selivanov in
branch '3.6':
Revert "[3.6] bpo-29406: asyncio SSL contexts leak sockets after calling close
with certain servers (GH-409) (#2062)" (#2112)
https://github.com/p
Changes by Yury Selivanov :
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> enhancement
___
Python tracker
<http://bugs.python
Yury Selivanov added the comment:
See also issue 29970.
--
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsub
Yury Selivanov added the comment:
Well, it's not just rolling back async/await from being keywords. Since 3.7
it's possible to create async generator expressions in non-async functions.
This wasn't possible to do with old hacks on the lexer. So if you want to
revert the
Yury Selivanov added the comment:
Actually, I think we could revert to old lexer hacks in 3.8 if we modify them
to treat 'async for' tocken sequence as one meta-tocken.
--
___
Python tracker
<https://bugs.python.o
Yury Selivanov added the comment:
> But why would we? I already have a working solution.
I've heard some complaints that it's hard to migrate to Python 3.7 because
async and await are keywords (although I think by now all popular libraries
have migrated already), so in
Yury Selivanov added the comment:
> And the same tokenizer trick that detects 'async def' could detect 'async
> for' easily.
Exactly. I just never thought that we could support async generator
expressions with the kind of hacks in tokenizer we had in 3.5-3.6.
Yury Selivanov added the comment:
Yes, I have exactly the same thoughts as Nathaniel about this. The bug should
be fixed, and the algorithm should be as follows (quoting Nathaniel):
> So, I would expect the rule to be, precisely: if an async list/dict/set
> comprehension occurs
401 - 500 of 3129 matches
Mail list logo
