virtualenv

[Bastian]

Hello,

the apps provided by PortablePython are working great. Thanks for all
your work! Can you please also integrate virtualenv?

I managed to install virtualenv. But to run scripts installed via
easy_install I always have to cd to the App folder of PortablePython
and then run
PATH_TO_MY_VIRTUAL_ENV\Scripts\theScriptInstalledByEasyInstall
which is annoying. It also prevents me from installing TurboGears2. At
some point a script installed seems to directly invoke the python.exe
in my virtualenv folder after changing the directory to another place
than PortablePythons App folder. When doing this I get a message
window telling me that python25.dll couldn't get find.

I'm asking for two things:
1. Can you please help me around this problem within the current
PortablePython version
2. Can you please integrate virtualenv in a way that after activating
the virtualenv all the scripts installed in PATH_TO_MY_VIRTUAL_ENV
\Scripts work from any directory?

Regards

Bastian

[Perica Zivkovic]

Hi there,

maybe a stupid question but why do you need virtualenv? As I
understand it it is an tool to create isolated python environments. If
it is only that you can install PP 1.1 twice on your USB drive and
have two PP's (isolated) running side by side with different
configurations.

kind regards,

Perica

[Bastian]

Hello,

the most important point I see is that with virtual env I'm able to
seperate my projects and the dependencies of the projects from either
PP or my Python installation on my machine or on any production, test
or whatever server. I want to be able to deploy my app in different
environments without worriing to much of about which dependencies I
have to extract from PP or whatever environment.

The media I'm using PP on is a network drive with limited space. Using
a separate PP for every isolated environment would multiply the
required (and not so small) disk space used by PP. The proposed
behaviour would allow me to call python.exe or whatever script I want
without having to supply the full path as virtualenv takes care (or
should be able to take care) of that. Furtheron I'm used to use
virtualenv on my own machine and have set up emacs to be able to
switch between different virtalenvs.

Some people also check in their virtual env along with their source
code into vcs. They probably won't do the same thing with their whole
python distribution, including all the IDE stuff other (very cool)
libraries supplied by PP.

Regards

Bastian

> > Bastian- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

[Perica Zivkovic]

Bastian,

thanks for your explanation. I personally never used virtualenv so I
don't know how it is wired with the rest of the python engine.

However I will install it and see can I have some answers to your
first question.
The second question will be added to the list of things to investigate
for the next release. No time indication on that one so far so stay
tuned.

kind regards,

Perica

p.s. be careful when using easy install, it can install things in the
system (and other folders) outside of your PP distribution so you will
loose first P in the PP :) It will work only on the machine you
installed it on.