On Wed, Jan 27, 2010 at 9:46 AM, Brad Allen
<bal...@zeomega.com> wrote:
Jason,
Supposing I wanted to add some additional tools to the
envbuilder-created virtualenv, such as sqlpython and/or ipython. Would
those need to be in setup.py, or could they be handled in the .env
config file?
There are a number of ways to do it. The project section has a requires option that takes a list of requirements to add to the virtualenv (the string is passed literally to easy_install, so adding a requirement "foo" translates into "easy_install foo".
Also bear in mind that the virtual env
is an actual python installation with its own site-packages directory. That means that you can use its easy_install to install packages to it just like any other python installation (ie to install storm you can "bin/easy_install storm"). Pip also has virtualenv support. For instance, you can do "pip install -E . storm" and that will install storm to the virtualenv in the current directory.
(Also, hope you don't mind me copying this to the envbuilder mailing list in case anyone else is confused about this!)
--
ZeOmega
Open Minds' Open Solutions
3010 Gaylord Parkway, Ste. 210
Frisco TX, 75034
http://www.zeomega.comJason Baker
214-618-9880 (ext. 8024)
"Program testing can be a very effective way to show the presence of bugs, but it is hopelessly inadequate for showing their absence." (Dijkstra)