Hi,
Le 22/06/2020 à 11:21, Stefan Behnel a écrit :
> [...]
>
> Basically, for maintained packages, I consider shipping the generated C
> code the right way. Less hassle, easier debugging, better user experience.
> For unmaintained packages, regenerating the C code at build time *can*
> extend the
Victor Stinner schrieb am 17.06.20 um 13:25:
> Le mer. 17 juin 2020 à 12:38, Petr Viktorin a écrit :
>>> There is an ongoing discussion about always requiring to run Cython
>>> when installing a C extension which uses Cython.
>>
>> Do you have a link to that discussion?
Yeah, I was wondering, too.
On Wed, 17 Jun 2020 at 12:27, Victor Stinner wrote:
> > If PEP 387 (Backwards Compatibility Policy) is accepted, all the
> > incompatible changes changes will require a two-year deprecation period.
> > Right?
>
[...]
>
> So far, it doesn't seem to be a giant disaster :-) Only a few C
> extensions
Le mer. 17 juin 2020 à 12:38, Petr Viktorin a écrit :
> > Py_TYPE(), Py_REFCNT() and Py_SIZE() can no longer be used as l-value.
> > These changes also broke numpy. I helped to fix Cython and numpy (and
> > they are already fixed).
>
> Those are not all the projects that were broken by the change
On 2020-06-17 12:03, Victor Stinner wrote:
re: [Python-Dev] When can we remove wchar_t* cache from string?
Le mar. 16 juin 2020 à 21:19, Steve Dower a écrit :
On 16Jun2020 1641, Inada Naoki wrote:
* This change doesn't affect to pure Python packages.
* Most of the rest uses Cython. Since I
