> Would it be OK to move the existing modules if a forward was used, > or would it still be bad because it would encourage writing new > code that couldn't run under older python versions? I think it would be a bad idea. The profusion (batteries included!) of modules in Python is already confusing enough; creating a significant number of new modules which were all duplicates of existing modules would just create mass confusion. And the only thing it would "fix" would be a convention on capitalization - it's just not worth it! On the other hand, the idea has been floated before that we should reorganize the standard libraries into some sort of a hierarchy. If someone were to come up with a useful plan for doing so (and that's a BIG if), then renaming the modules to follow standard naming conventions at the same time would be a good idea. But only because we would be renaming them ANYWAY to create the hierarchy. -- Michael Chermside
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