On 1 February 2014 21:08, Sayth Renshaw <flebber.crue@gmail.com> wrote:

I use the Project Plugin. Would be good if I could tie it to that to have each project assigned its own venv. Yes using workon in a build would be hard as you cannot prompt for input as to what 'workon (self)'.

Still we have the project plugin and the vc plugin both for workin on project code(as it appears to me). Pydev just asks for the venv and ties it to the project.

Which project plugin, there are two? Or do you mean built-in projects? You can set build commands specific to the (built-in) project as well, and I think one of the plugins can also use that facility.

So if you use a built-in project, its commands can be "source activate; python %f" with the working directory set to the project directory, ie "%p"

Cheers

Lex

Will post if I come to a solution that works well.

Sayth

On Sat, Feb 1, 2014 at 8:20 PM, Frank Lanitz <frank@frank.uvena.de> wrote:

Am 01.02.2014 01:18, schrieb Sayth Renshaw:

> Was thinking in django projects managing the whole projects in geany.
>

Maybe you can post your outcome at some point -> wiki maybe?

Cheers,
Frank

_______________________________________________
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.geany.org
https://lists.geany.org/cgi-bin/mailman/listinfo/users