Vinay Sajip added the comment: I'd use runpy.run_path if I could, but it's not available on Python 2.6 - that's why I'm using run_module.
A lot of setup.py files out there use __file__ to compute additional package names, package data locations etc. - this can lead to bogus package names computed blindly from paths assumed to be relative, when the setup.py file is run using run_module. I'm not sure what you mean when you say "looks consistent" - ISTM there is a difference, i.e. inconsistency, between a direct run and a run via run_module. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16737> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
