"Fredrik Lundh" <fredrik@pythonware.com> 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. > > does anyone here know how to do that, without having to resort to > ugly wrapper batch files/shell scripts? I usually make a symlink into the build directory. Then, whenever it is rebuild, the symlink will still be there. > (distutils is also a pain to use with a version management system > that marks files in the repository as read-only; distutils copy function > happily copies all the status bits. but the remove function refuses to > remove files that are read-only, even if the files have been created > by distutils itself...) That's a bug, IMO. 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