[ 
https://issues.apache.org/jira/browse/PROTON-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiri Daněk reassigned PROTON-2286:
----------------------------------

    Assignee:     (was: Jiri Daněk)

> Container.selectable(EventInjector) in python on Windows causes "OSError: 
> [WinError 10038] An operation was attempted on something that is not a 
> socket", eliminating use of custom events
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-2286
>                 URL: https://issues.apache.org/jira/browse/PROTON-2286
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: python-binding
>    Affects Versions: proton-c-0.32.0
>         Environment: Windows 10, python 3.7-3.8
>            Reporter: alexey
>            Priority: Major
>
> First, this hinders examples (db_recv.py and others using EventInjector) from 
> running.
> Second, most important, this doesn't let one have user-defined events in the 
> built-in event loop, which limits its interactivity. Is there another 
> straightforward asynchronous way to send messages on demand?
> Something similar occurred in python asyncio before 3.8, when they made the 
> [{{ProactorEventLoop}}|https://docs.python.org/3/library/asyncio-platforms.html#windows]
>  default on Windows instead of SelectorEventLoop, as select() on windows 
> works only with sockets.
> Also, could someone please integrate proton with python asyncio which is 
> standard convenient way of asynchronous execution in python? Or at least 
> provide an example of using asyncio event loop like with tornado 
> (proton_tornado.py).
> Thank you.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to