Erwin Mayer added the comment:
Regarding the issues mentioned in
https://github.com/simplejson/simplejson/issues/77, they already apply with the
current implementation anyway (true is serialized as 'true'), so users must
already be careful.
The JSONEncoder with default parame
Erwin Mayer added the comment:
Will this be merged? I also believe it is an unexpected behavior to not
serialize dictionary keys when the default option is used.
--
nosy: +Erwin Mayer
___
Python tracker
<http://bugs.python.org/issue18
Erwin Mayer added the comment:
Thank you Guido; I am now trying to always close a loop explicitly and see if
it fixes the issue (so far so good in the last 24h).
I could not locate this requirement in the EventLoop documentation page
(https://docs.python.org/3/library/asyncio-eventloop.html
Erwin Mayer added the comment:
I understand that asyncio is not .NET and did my best to implement "by the
book" according to the asyncio documentation I read extensively.
My await_async function has in fact nothing in common with what I would do in
.NET but is hopefully as close as p
Erwin Mayer added the comment:
I simply need to run a coroutine synchronously (which may or may not have a
loop parameter), so I tried to do it by the book. With .NET it is easy to call
.Wait() on a Task (but .NET by default uses a threadpool, not a single-threaded
event loop).
I am
Erwin Mayer added the comment:
This cannot be a firewall issue as a loop can be successfully created thousands
of time, for hours, before a creation attempt will hang (with no change from
the firewall). The rest of the program (other threads) continues to run and
there is memory issue.
If I
New submission from Erwin Mayer:
I am using the following function to force a coroutine to run synchronously:
def await_sync(coro: types.CoroutineType, timeout_s: int=None):
"""
:param coro: a coroutine or lambda loop: coroutine(loop)
:param timeout_s:
:return:
