On 26/10/2021 07:53, Stefan Behnel wrote:
Am 26. Oktober 2021 07:54:10 MESZ schrieb Lisandro Dalcin:
In any case, if you know how and can implement the __future__ import,
that
would be great. Otherwise, valid Python3 code using that import
currently fails to compile in Cython.
Probably just an
Am 26. Oktober 2021 07:54:10 MESZ schrieb Lisandro Dalcin:
>In any case, if you know how and can implement the __future__ import,
>that
>would be great. Otherwise, valid Python3 code using that import
>currently fails to compile in Cython.
Probably just an oversight. A no-op future import is trivi
On Mon, 25 Oct 2021 at 21:57, da-woods wrote:
> One further option would be to revert to Cython 0.29 behaviour, but
> support the PEP-563 version as a "from __future__" import (essentially
> following the current behaviour of Python).
In any case, if you know how and can implement the __future_
I suspect the answer to this is still "wait and see" but: do we have an
opinion on what we want to do about annotations in Cython 3.
Currently we're targetting PEP-563 behaviour. To me it looks fairly
likely that this won't be what Python decides on. I guess the likely
outcomes are "status quo
One further option would be to revert to Cython 0.29 behaviour, but
support the PEP-563 version as a "from __future__" import (essentially
following the current behaviour of Python). When I wrong the original
patch for the PEP-563 I tried to do that, but then removed the code in
favour of keepi
