Guido van Rossum <guido@python.org> writes: > > I tend to use an incremental approach, with lots of edit-compile-run > > cycles. I still haven't found a way to get the damn thing to just build > > my extension and copy it to the current directory, so I can run the > > test scripts. > > Funny, I use an edit-compile-run cycle too, but I don't have the need > to copy anything to the current directory. That's because Python treats its own build directory special: it adds build/something to sys.path when it finds that it is started from the build directory. If you are developing a separate package, all your code ends up in ./build/lib.platform, which is not on sys.path. Regards, Martin
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