On Fri, Jul 22, 2011 at 10:53 AM, Glenn Linderman <v+python at g.nevcal.com> wrote: > Ah yes. It means there has to be one more rule for disambiguation, which > Nick supplied. Your case wasn't clear to me from your first description, > however. As long as there is an ordering, and it is documented, it is not > particularly confusing, however. The genuinely confusing part is that x.py still takes precedence, even if it appears on sys.path *after* x/y.py. However, we're forced into that behaviour by backwards compatibility requirements. The alternative of allowing x/y.py to take precedence has been rejected on those grounds more than once. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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