search

MichaelAquilina / python-tools

:wrench: Atom plugin which uses jedi to provide numerous tools useful for developing python code in atom.
MIT License
100 stars 22 forks source link

Per-project virtualenv #16

Open qnub opened 9 years ago

qnub commented 9 years ago

In readme written «Goes along really nicely with the autocomplete-python package to provide a full Python IDE experience in Atom.» But autocomplete-python support per-project virtualenv settings in format:

$PROJECT/.env/lib/python2.7/site-packages;

Where $PROJECT is placeholder for project's folder path. Seems like python-tools not used this settings and not support same format in own settings (only full qualified path, but it's not useful when you have ~50 projects with own virtualenvs). So «Go to definition» not work me at all :(

MichaelAquilina commented 8 years ago

Hi @qnub sorry for the very late reply, but I must have missed my email with this notification for some reason. I'll look into this as soon as I can. Should not be too hard to implement.

qnub commented 8 years ago

It'll be great, thank you!

dereknex commented 8 years ago

great idea.

mmospanenko commented 8 years ago

Can I chose remote python (vagrant or Docker) for go-to-definition?

eremeevdev commented 8 years ago

Also interesting in using docker

harrislapiroff commented 8 years ago

+1