On Fri, Apr 27, 2012 at 7:30 AM, Christian Tismer <tismer at stackless.com> wrote: > No big deal and easy to work around, I just would like to understand why. I don't like it either and want to change it, but I'm also not going to mess with it until the importlib bootstrapping is fully integrated and stable. For the moment, there's a workaround in runpy to ensure at least __main__.__file__ is always absolute (even when using the -m switch). Longer term, I'd like to see __file__ and __path__ entries to be guaranteed to be *always* absolutely, even when they're imported relative to the current working directory. 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