Éric Araujo <mer...@netwok.org> added the comment: Ah, higery’s code already has an answer for me: it writes *two* paths in the .pth file, one to the build dir (so that .dist-info is found) and one to the modules root (for modules, built in place). Anyone sees a problem with that? (For example huge sys.path.)
In this scheme, when Python modules are edited, changes are visible instantly, when C modules are edited, a call to build_ext is required, and when the metadata is edited, build_distinfo is required. Does that sound good? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8668> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
