t I think: no possible way to
understand it for something else that what it means.
Arthur
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.py
ator have to implement the Future interface, and then you're
> resumed either by sending back None when the Future completes, or else
> by having an exception thrown in.
>
> -n
>
> On Wed, Nov 7, 2018 at 8:24 PM, Justin Turner Arthur
> wrote:
> > I'm trying to fi
I'm trying to figure out if our documentation on the new awaitable concept
in Python 3.6+ is correct. It seems to imply that if an object's __await__
method returns an iterator, the object is awaitable. However, just
returning an iterator doesn't seem to work with await in a coroutine or
with the a
On 11 May 2016 at 22:51, Ethan Furman wrote:
> On 05/11/2016 01:44 PM, Serhiy Storchaka wrote:
>
> os.path
>>> '''
>>>
>>> The various path-manipulation functions of ``os.path`` [#os-path]_
>>> will be updated to accept path objects. For polymorphic functions that
>>> accept both bytes and st
On 8 April 2016 at 16:18, Jon Ribbens
wrote:
> I've made another attempt at Python sandboxing, which does something
> which I've not seen tried before - using the 'ast' module to do static
> analysis of the untrusted code before it's executed, to prevent most
> of the sneaky tricks that have been
Moam writes -
>Hello,
>More than a year and a half ago, I posted a big patch to IDLE which
>adds support for completion and much better calltips, along with some
>other improvements.
I had also tried to have a little input to the IDLE development process.
Suggesting on the idle-dev list it seem
>* and because Guido believes beginners tend to copy too much
> (that is one reason why copy.copy is not a builtin) and that
> the language should encourage correct behavior.
OTOH, beginners tend to copy not enough - when for example iterating over a
list being acting upon.
Though my real arg
