2013/6/21 Nick Coghlan <ncogh...@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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
