On Jun 23, 2015, at 06:27, Christian Tismer wrote:
> On 23.06.15 06:42, Zachary Ware wrote:
>> Christian, what say you? Would having the project files from 3.5
>> backported to 2.7 (but still using MSVC 9) be positive, negative, or
>> indifferent for Stackless?
>
> I am very positive about your e
Arc Riley schrieb am 25.06.2015 um 04:36:
> A type slot for tp_as_async has already been added (which is good!) but we
> do not currently seem to have protocol functions for awaitable types.
>
> I would expect to find an Awaitable Protocol listed under Abstract Objects
> Layer, with functions like
On Thu, Jun 25, 2015 at 6:45 AM, Stephen J. Turnbull wrote:
>
> Rustom Mody writes:
>
> > Can submit a bug-report if it looks ok
>
> Thanks for the post. IMO this should have gone directly to the
> tracker
Done http://bugs.python.org/issue24507#msg245793
> because (1) you have some support for
A type slot for tp_as_async has already been added (which is good!) but we
do not currently seem to have protocol functions for awaitable types.
I would expect to find an Awaitable Protocol listed under Abstract Objects
Layer, with functions like PyAwait_Check, PyAwaitIter_Check, and
PyAwaitIter_N
On Wed, Jun 24, 2015 at 11:21:54PM +0200, Sven R. Kunze wrote:
> Thanks, Yury, for you quick response.
>
> On 24.06.2015 22:16, Yury Selivanov wrote:
> >Sven, if we don't have 'async def', and instead say that "a function
> >is a *coroutine function* when it has at least one 'await'
> >expressio
Rustom Mody writes:
> Can submit a bug-report if it looks ok
Thanks for the post. IMO this should have gone directly to the
tracker because (1) you have some support for the idea that at least
some of these are unintentional, and therefore candidates for
alignment with the rest of the code, (2)
Thanks, Yury, for you quick response.
On 24.06.2015 22:16, Yury Selivanov wrote:
Sven, if we don't have 'async def', and instead say that "a function
is a *coroutine function* when it has at least one 'await'
expression", then when you refactor "useful()" by removing the "await"
from it, it st
> On Jun 22, 2015, at 6:58 PM, Zachary Ware
> wrote:
>
> On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote:
>> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray
>> wrote:
>>> OK, so what you are saying is that speed.python.org will run a buildbot
>>> slave so that when a change is commi
Hi Sven,
On 2015-06-24 2:14 PM, Sven R. Kunze wrote:
Hi everybody,
recently, I stumbled over the new 3.5 release and in doing so over PEP
0492.
After careful consideration and after reading many blog posts of
various coders, I first would like to thank Yury Selivanov and
everybody else who
Hi everybody,
recently, I stumbled over the new 3.5 release and in doing so over PEP 0492.
After careful consideration and after reading many blog posts of various
coders, I first would like to thank Yury Selivanov and everybody else
who brought PEP 0492 to its final state. I therefore conside
Hello folks
Along with a few students we were preparing to poke around inside the
CPython sources.
Of course it would be neat if we submitted useful patches... but since I
dont expect to get there so fast I thought I'd start by setting up with git
which I am more familiar with than mercurial.
Tha
11 matches
Mail list logo
