Message140197
| Author |
eric.araujo |
| Recipients |
Peter.Waller, alexis, carljm, eric.araujo, higery, meatballhat, michael.mulich, tarek |
| Date |
2011年07月12日.14:31:43 |
| SpamBayes Score |
0.00056663115 |
| Marked as misclassified |
No |
| Message-id |
<1310481104.61.0.0996867751414.issue8668@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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? |
|