Chris Meyer added the comment:
Is there a way to reproduce this issue? I run the following code in Python 3.9
and it works as expected (prints "xyz" twice).
import asyncio
import gc
async def xyz():
print("xyz")
event_loop = asyncio.get_event_loop()
event_loop.c
Chris Meyer added the comment:
This looks like it a regression specific to Python 3.9.7 and has been fixed.
https://bugs.python.org/issue45081
https://github.com/python/cpython/pull/28132.
--
resolution: -> duplicate
stage: -> resolved
status: open -&g
New submission from Chris Meyer :
If I make a explicit subclass of a protocol that also inherits from a mixin and
calls super() in order to initialize the mixin, I get the "Protocols cannot be
instantiated" exception.
This case arises when having a hierarchy of both protocols an
Chris Meyer added the comment:
>> I would like to request that this ability to dynamically load Python DLLs
>> remains even with any new initialization mechanism.
> I don't plan to remove any feature :-)
I am glad to hear that. I'm somewhat nervous about it nevertheless.
Chris Meyer added the comment:
> How do you configure sys.path currently? Do you parse a configuration file?
> Do you use a registry key on Windows?
We have several launch scenarios - but for the currently most common one, which
is to launch using a separate, existing Python environme
Chris Meyer added the comment:
Responding to your request for feedback on Python-Dev:
We embed Python dynamically by finding the libPython DLL, loading it, and
looking up the required symbols. We make appropriate define's so that the
Python headers (and NumPy headers) point to our functions
Change by Chris Meyer :
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue38856>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Chris Meyer :
--
keywords: +patch
pull_requests: +19769
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/20525
___
Python tracker
<https://bugs.python.org/issu
Chris Meyer added the comment:
Here is another way to reproduce this (or an extremely similar) error without a
loop. Since may be a race condition, I'm not sure this works 100% of the time
on all machines - but it did on several machines I tried.
```
import asyncio
loop
Change by Chris Meyer :
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue39232>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Chris Meyer :
Is the new asyncio.loop.shutdown_default_executor() suitable for event loops
that are run in single-step mode?
event_loop.create_task(event_loop.shutdown_default_executor())
event_loop.stop()
event_loop.run_forever()
I don't see how it will work since
Change by Chris Meyer :
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue34037>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Chris Meyer :
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue39010>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Chris Meyer :
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue37373>
___
___
Python-bugs-list mailing list
Unsubscribe:
Chris Meyer added the comment:
Is this related to bpo-39010 too?
--
nosy: +cmeyer
___
Python tracker
<https://bugs.python.org/issue39651>
___
___
Python-bug
New submission from Chris Meyer:
BaseEventLoop.close shuts down the executor associated with the event loop.
It should do that BEFORE it sets self._closed = True, otherwise any pending
executor futures will attempt to 'call_soon' on the event loop when they
finish, resulting in a confusing
16 matches
Mail list logo
