djrobstep / autovenv Goto Github PK

Autovenv fails silently instead of working as expected, most commands fail too. This is due to changes made in the argparse library after 2.7.6.

I prefer creating and activating virtualenvs only when there is a setup.py file at the top.

Going through the source code, I found I could do that by editing the ~/.local/share/autovenv/config file to have:

file_names:
- requirements.txt
- setup.py

Question is: is this OK and do we want to document this ?

Thanks for writing this tool by the way :)

Nice project, thanks for making and sharing it!

Is it possible to manually invoke autovenv to create a venv? In the spirit of the unix philosophy of "do one thing and do it well", I think autovenv is trying to do too much with the automatic activation upon directory entry, and persistence of config information.

I would use this project if it worked something like this

> autovenv -r requirements.txt
# creates venv in ./venv, runs pip install -U pip, pipi install -r requirements.txt
venv has been created in venv
type `activate venv/bin/activate` to active it

or

> autovenv --python pythonX
# defaults to using requirements.txt, creates venv with pythonX rather than default python

As you can see, nothing persists between calls and all relevant settings are passed through the CLI.

When sourcing autovenv.sh I get the following error:

$ source /usr/local/bin/autovenv.sh                                                                   
Unsupported use of '&&'. In fish, please use 'COMMAND; and COMMAND'.
/usr/local/bin/autovenv.sh (line 8):     builtin cd "$@" && do_autovenv
                                                          ^
from sourcing file /usr/local/bin/autovenv.sh
	called on standard input

source: Error while reading file '/usr/local/bin/autovenv.sh'

Will attempt some more debugging.