[Python-Dev] stat module in C -- what to do with stat.py? (original) (raw)
Victor Stinner victor.stinner at gmail.com
Fri Jun 21 09:25:35 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 ]
2013/6/21 Nick Coghlan <ncoghlan at gmail.com>:
Because practicality beats purity. This "wrong" Python code has been good enough for all Python version up until 3.4, it makes sense to keep it as a fallback instead of throwing it away.
How do you plan to handle the following case in Python?
"Looking in more detail: for the S_IFMT flags, OSX/Darwin/FreeBSD defines 0xe000 as S_IFWHT (whiteout), but Solaris defines it as S_IFPORT (event port)."
We may keep the Python module if it is kept unchanged, but the Python and C modules should have the same public API (the C module should not have more features).
Or should play with "if sys.platform == ..."?
Victor
- 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 ]