Changes by Marcin Szewczyk :
--
nosy: +wodny
___
Python tracker
<http://bugs.python.org/issue4963>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Marcin Szewczyk:
While asyncio.wrap_future is mentioned in PEP 3156 and has its docstring it is
undocumented in the reference. run_in_executor is documented but doesn't
mention wrap_future either.
$ grep -r wrap_future Doc; echo $?
1
--
assignee: docs@p
Marcin Szewczyk added the comment:
Thanks for the update.
Regarding the "plain generator" part -- am I right thinking it's simply a
generator not decorated with @asyncio.coroutine?
--
___
Python tracker
<http://bugs.pyt
New submission from Marcin Szewczyk:
Using benchmark from the section
https://www.python.org/dev/peps/pep-0492/#async-await raises:
Traceback (most recent call last):
File "./bench.py", line 28, in
timeit(abinary, 19, 30)
File "./bench.py", line 23, in timei
New submission from Marcin Szewczyk:
As stated in the subject. Example is in a remote Git repository:
https://bitbucket.org/wodny/python-dbm-experiments/
It shows how some random data gets into the database (into some gaps between
keys and values). There is also a C example which hasn't
New submission from Marcin Szewczyk:
I've done some experiments with:
1) multiprocessing.Process.join()
2) os.waitpid()
3) subprocess.Popen.wait()
These three methods behave completely different when interrupted with a signal
which I find disturbing.
Reactions are:
1) exit with no exce
