On Nov 28, 2012, at 12:04 PM, Guido van Rossum wrote:
>> Anyway, as for concrete requirements: The issue I have always seen with
>> various asynchronous libraries is their lack of composability. Everyone
>> writes their own application loop and event queue. Merely having a standard
>> spec
On Wed, Nov 28, 2012 at 4:13 AM, Kristján Valur Jónsson
wrote:
> I'm sorry, I thought it was something that people did more often, to create
> different implementations of of the "socket" api, for which cPython provided
> a mere reference implementation. I know of at least three different
> al
Le Wed, 28 Nov 2012 12:13:15 +,
Kristján Valur Jónsson a écrit :
> I'm sorry, I thought it was something that people did more often, to
> create different implementations of of the "socket" api, for which
> cPython provided a mere reference implementation. I know of at least
> three different
I'm sorry, I thought it was something that people did more often, to create
different implementations of of the "socket" api, for which cPython provided a
mere reference implementation. I know of at least three different alternative
implementations, so I thought that the question were clear eno
On Wed, Nov 28, 2012 at 2:46 PM, Eric Snow wrote:
> I knew there was one more: http://bugs.python.org/issue16499 ("CLI
> option for isolated mode").
>
Along with another PYIOENCODING related one that the Blender folks reported
(Christian Heimes pointed it out to me earlier today).
Anyway, I crea
