[I wrote] > My only objection is that this is a PITA. It becomes a ... > However, to do this properly, we must do _every_ exported ... > Im really not convinced it is worth it to save one, well-named DLL > in the system directory. ie, lots of good reasons _not_ to do this. However, it is worth pointing out that there is one good - possibly compelling - reason to consider this. Not only would we drop the dependency from the system directory, we could also drop the dependency to the Python version. That is, any C extension compiled for 1.6 would be able to automatically and without recompilation work with Python 1.7, so long as we kept all the same public names. It is too late for Python 1.5, but it would be a nice feature if an upgrade to Python 1.7 did not require waiting for every extension author to catch up. OTOH, if Python 1.7 is really the final in the 1.x family, is it worth it for a single version? Just-musing-ly, Mark.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4