[Python-Dev] Should standard library modules optimize for CPython? (original) (raw)
Raymond Hettinger raymond.hettinger at gmail.com
Mon Jun 2 02:19:06 CEST 2014
- Previous message: [Python-Dev] Should standard library modules optimize for CPython?
- Next message: [Python-Dev] Should standard library modules optimize for CPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jun 1, 2014, at 9:17 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
Le 01/06/2014 10:11, Steven D'Aprano a écrit :
My feeling is that the CPython standard library should be written for CPython, that is, it should stick to the current naive implementation of median, and if PyPy wants to speed the function up, they can provide their own version of the module. I should not complicate the implementation by trying to detect which Python the code is running under and changing algorithms accordingly. However, I should put a comment in the module pointing at the tracker issue. Does this sound right to others? It sounds ok to me.
That makes sense.
Raymond -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140601/bb02d8b1/attachment.html>
- Previous message: [Python-Dev] Should standard library modules optimize for CPython?
- Next message: [Python-Dev] Should standard library modules optimize for CPython?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]