alex wrote: > > 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. >=20 > I haven't even looked for such a way, since going to site-packages is > no problem for me. If I was developing on a Python installation = shared > by several users I'd no doubt feel differently about it. you only work on a single project too, I assume. I tend to prefer not to install a broken extension in my machine's default install, in case I have to switch to another project... (and switching between projects is all I seem to do these days ;-) (and I maintain too many modules to afford to install a separate python interpreter for each one of them...) </F>
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