[Python-Dev] stat module in C -- what to do with stat.py? (original) (raw)
Gustavo Carneiro gjcarneiro at gmail.com
Fri Jun 21 23:02:44 CEST 2013
- Previous message: [Python-Dev] stat module in C -- what to do with stat.py?
- Next message: [Python-Dev] stat module in C -- what to do with stat.py?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jun 21, 2013 at 8:20 PM, Steven D'Aprano <steve at pearwood.info>wrote:
On 21/06/13 01:35, Benjamin Peterson wrote:
2013/6/20 Charles-François Natali <cf.natali at gmail.com>:
2013/6/20 Thomas Wouters <thomas at python.org>:
If the .py file is going to be wrong or incomplete, why would we want to keep it -- or use it as fallback -- at all? If we're dead set on having a .py file instead of requiring it to be part of the interpreter (whichever that is, however it was built), it should be generated as part of the build process. Personally, I don't see the value in it; other implementations will need to do something special to use it anyway.
That's not correct. Other implementations can do exactly what CPython 3.3 does, namely just use stat.py as given. Not all implementations necessarily care about multiple platforms where stat constants are likely to change. That's exactly my rationale for pushing for removal. +1 to nixing it. -1 Reading the Python source code is a very good way for beginner programmers to learn about things like this.
On the other hand, it is counter-productive to learn about code that is conceptually wrong. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130621/1202a356/attachment.html>
- Previous message: [Python-Dev] stat module in C -- what to do with stat.py?
- Next message: [Python-Dev] stat module in C -- what to do with stat.py?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]