RetroSearch Browse

Fri Jun 6 03:51:13 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-June/134837.html

On Fri, Jun 6, 2014 at 11:47 AM, Nathaniel Smith <njs at pobox.com> wrote:
> Unfortunately we don't actually know whether Cython is the only culprit
> (such code *could* be written by hand), and even if we fixed Cython it would
> take some unknowable amount of time before all downstream users upgraded
> their Cythons. (It's pretty common for projects to check in Cython-generated
> .c files, and only regenerate when the Cython source actually gets
> modified.) Pretty risky for an optimization.

But code will still work, right? I mean, you miss out on an
optimization, but it won't actually be wrong code? It should be
possible to say "After upgrading to Cython version x.y, regenerate all
your .c files to take advantage of this new optimization".

ChrisA

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-June/134837.html below:

[Python-Dev] [numpy wishlist] Interpreter support for temporary elision in third-party classes