Message140205
> 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?
That sounds reasonable to me. I'm not worried about that making sys.path
too long: whatever we do we aren't going to challenge buildout in that
department ;-) |
|
Date |
User |
Action |
Args |
2011-07-12 19:04:59 | carljm | set | recipients:
+ carljm, tarek, eric.araujo, meatballhat, Peter.Waller, alexis, michael.mulich, higery |
2011-07-12 19:04:59 | carljm | link | issue8668 messages |
2011-07-12 19:04:59 | carljm | create | |
|