Movatterモバイル変換

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

• Previous message:[Python-Dev] [numpy wishlist] Interpreter support for temporary elision in third-party classes
• Next message:[Python-Dev] [numpy wishlist] Interpreter support for temporary elision in third-party classes
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

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 anoptimization, but it won't actually be wrong code? It should bepossible to say "After upgrading to Cython version x.y, regenerate allyour .c files to take advantage of this new optimization".ChrisA

• Previous message:[Python-Dev] [numpy wishlist] Interpreter support for temporary elision in third-party classes
• Next message:[Python-Dev] [numpy wishlist] Interpreter support for temporary elision in third-party classes
• Messages sorted by:[ date ][ thread ][ subject ][ author ]