Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <18c0a8bb-9295-493b-b0aa-1593b7d05c2f@googlegroups.com>
References: <18c0a8bb-9295-493b-b0aa-1593b7d05c2f@googlegroups.com>
Date: Thu, 15 Aug 2013 13:30:18 -0300
Subject: Re: "Nested" virtual environments
From: Marcel Rodrigues <marcelgmr@gmail.com>
To: Luca Cerone <luca.cerone@gmail.com>
Content-Type: multipart/alternative; boundary=001a11330e2258b02504e3fefdcd
Cc: python-list <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.603.1376584227.1251.python-list@python.org>
Lines: 146
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:52558

--001a11330e2258b02504e3fefdcd
Content-Type: text/plain; charset=UTF-8

I don't know how to completely solve this problem, but here is something
that can alleviate it considerably.

If you have a recent version of pip, you can use wheels [1] to save built
packages locally. First create a new virtualenv and install the common
packages. Then put these packages in a wheel directory. Then, for any other
virtualenv that need the common packages, you can easily install then from
the wheel directory (this is fast even for numpy & friends, because nothing
will be compiled again) [2].

# Create a new virtualenv
virtualenv myenv
source myenv/bin/activate
# Install the wheel package
pip install wheel
# Install your common packages
pip install numpy scipy matplotlib
# Create a requirements file
pip freeze > /local/requirements.txt
# Create wheel for the common packages
pip wheel --wheel-dir=/local/wheels -r /local/requirements.txt

Now you have all the built packages saved to /local/wheels, ready to
install on any other environment. You can safely delete myenv. Test it with
the following:

# Create a virtualenv for a new project
virtualenv myproj
source myproj/bin/activate
# Install common packages from wheel
pip install --use-wheel --no-index --find-links=/local/wheels -r
/local/requirements.txt

[1] https://wheel.readthedocs.org
[2]
http://www.pip-installer.org/en/latest/cookbook.html#building-and-installing-wheels



2013/8/9 Luca Cerone <luca.cerone@gmail.com>

> Dear all, is there a way to "nest" virtual environments?
>
> I work on several different projects that involve Python programming.
>
> For a lot of this projects I have to use the same packages (e.g. numpy,
> scipy, matplotlib and so on), while having to install packages that are
> specific
> for each project.
>
> For each of this project I created a virtual environment (using virtualenv
> --no-site-packages) and I had to reinstall the shared packages in each of
> them.
>
> I was wondering if there is a way to nest a virtual environment into
> another,
> so that I can create a "common" virtual environment  that contains all the
> shared packages and then "specialize" the virtual environments installing
> the packages specific for each project.
>
> In a way this is not conceptually different to using virtualenv
> --system-site-packages, just instead of getting access to the system
> packages a virtual environment should be able to access the packages of an
> other one.
>
> Thanks a lot in advance for the help,
> Luca
> --
> http://mail.python.org/mailman/listinfo/python-list
>

--001a11330e2258b02504e3fefdcd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div><div>I d=
on&#39;t know how to completely solve this problem, but here is something t=
hat can alleviate it considerably.<br></div><div><br>If you have a recent v=
ersion of pip, you can use wheels [1] to save built packages locally. First=
 create a new virtualenv and install the common packages. Then put these pa=
ckages in a wheel directory. Then, for any other virtualenv that need the c=
ommon packages, you can easily install then from the wheel directory (this =
is fast even for numpy &amp; friends, because nothing will be compiled agai=
n) [2].<br>
<br></div><div># Create a new virtualenv<br></div><div>virtualenv myenv<br>=
</div><div>source myenv/bin/activate<br></div># Install the wheel package<b=
r></div>pip install wheel<br></div># Install your common packages<br></div>
pip install numpy scipy matplotlib<br></div># Create a requirements file<br=
></div>pip freeze &gt; /local/requirements.txt<br></div># Create wheel for =
the common packages<br>pip wheel --wheel-dir=3D/local/wheels -r /local/requ=
irements.txt<br>
<br></div>Now you have all the built packages saved to /local/wheels, ready=
 to install on any other environment. You can safely delete myenv. Test it =
with the following:<br><br></div># Create a virtualenv for a new project<br=
>
</div>virtualenv myproj<br>source myproj/bin/activate<br></div># Install co=
mmon packages from wheel<br>pip install --use-wheel --no-index --find-links=
=3D/local/wheels -r /local/requirements.txt<br><div><div><div><div><div><di=
v>
<div><div><div><div><div><br>[1] <a href=3D"https://wheel.readthedocs.org">=
https://wheel.readthedocs.org</a><br>[2] <a href=3D"http://www.pip-installe=
r.org/en/latest/cookbook.html#building-and-installing-wheels">http://www.pi=
p-installer.org/en/latest/cookbook.html#building-and-installing-wheels</a><=
br>
</div></div></div></div></div></div></div><br></div></div></div></div></div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/8/9 Luc=
a Cerone <span dir=3D"ltr">&lt;<a href=3D"mailto:luca.cerone@gmail.com" tar=
get=3D"_blank">luca.cerone@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear all, is there a way to &quot;nest&quot;=
 virtual environments?<br>
<br>
I work on several different projects that involve Python programming.<br>
<br>
For a lot of this projects I have to use the same packages (e.g. numpy, sci=
py, matplotlib and so on), while having to install packages that are specif=
ic<br>
for each project.<br>
<br>
For each of this project I created a virtual environment (using virtualenv =
--no-site-packages) and I had to reinstall the shared packages in each of t=
hem.<br>
<br>
I was wondering if there is a way to nest a virtual environment into anothe=
r,<br>
so that I can create a &quot;common&quot; virtual environment =C2=A0that co=
ntains all the<br>
shared packages and then &quot;specialize&quot; the virtual environments in=
stalling the packages specific for each project.<br>
<br>
In a way this is not conceptually different to using virtualenv --system-si=
te-packages, just instead of getting access to the system packages a virtua=
l environment should be able to access the packages of an other one.<br>

<br>
Thanks a lot in advance for the help,<br>
Luca<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
<a href=3D"http://mail.python.org/mailman/listinfo/python-list" target=3D"_=
blank">http://mail.python.org/mailman/listinfo/python-list</a><br>
</font></span></blockquote></div><br></div>

--001a11330e2258b02504e3fefdcd--