On Sat, 01 Aug 2015 15:30:34 +1000,
Ben Finney wrote:
> Seb writes:
>> With lots of debugging to do, the last thing I'd want is to worry
>> about the search path.
> Short answer: you need ‘python3 ./setup.py develop’.
> Medium-length answer: you need to add some infrastructure to get your
> pr
On 8/1/2015 12:21 AM, Seb wrote:
It seems too cumbersome to have to update `sys.path` to include the
development tree of a package (and sub-packages) that's still very
young. With lots of debugging to do, the last thing I'd want is to
worry about the search path. So I've been searching for bet
Seb writes:
> It seems too cumbersome to have to update `sys.path` to include the
> development tree of a package (and sub-packages) that's still very
> young. With lots of debugging to do, the last thing I'd want is to
> worry about the search path. So I've been searching for better ways to
>
Seb writes:
> With lots of debugging to do, the last thing I'd want is to worry
> about the search path.
Short answer: you need ‘python3 ./setup.py develop’.
Medium-length answer: you need to add some infrastructure to get your
project to the point where you can run ‘python3 ./setup.py develop’
