Hi.
On 25.11.2013. 14:42, Jurko Gospodnetić wrote:
So far all tests seem to indicate that things work out fine if we
install to some dummy target folder, copy the target folder to some
version specific location & uninstall. That leaves us with a working
Python folder sans the start menu and
Hi.
On 25.11.2013. 17:38, Terry Reedy wrote:
So far all tests seem to indicate that things work out fine if we
install to some dummy target folder, copy the target folder to some
version specific location & uninstall.
If the dummy folder had 3.3.0, you should not need to uninstall to
inst
On 11/25/2013 8:42 AM, Jurko Gospodnetić wrote:
So far all tests seem to indicate that things work out fine if we
install to some dummy target folder, copy the target folder to some
version specific location & uninstall.
If the dummy folder had 3.3.0, you should not need to uninstall to
in
Hi.
On 25.11.2013. 15:15, Albert-Jan Roskam wrote:
> Are you sure?
http://stackoverflow.com/questions/1534210/use-different-python-version-with-virtualenv
Yup, I'm pretty sure by now (based on reading the docs, not trying it
out though).
Virtualenv allows you to set up differen
On Tue, Nov 26, 2013 at 1:15 AM, Albert-Jan Roskam wrote:
> Below is a little terminal session. I often switch between python 3.3 and
> python 2.7. My virtualenv for python 3.3 is called "python33". "workon" is a
> virtualenv wrapper command. And check out the envlist in tox.ini on
> http://to
On Mon, 11/25/13, Jurko Gospodnetić wrote:
Subject: Re: Parallel Python x.y.A and x.y.B installations on a single Windows
machine
To: python-list@python.org
Date: Monday, November 25, 2013, 2:57 PM
Hi.
On 25.11.2013. 14:20, Albert-Jan
Hi.
On 25.11.2013. 14:20, Albert-Jan Roskam wrote:
Check out the following packages: virtualenv, virtualenvwrapper, tox
virtualenv + wrapper make it very easy to switch from one python
version to another. Stricly speaking you don't need
virtualenvwrapper, but it makes working with virtualenv a
Hi.
On 25.11.2013. 13:46, Ned Batchelder wrote:
IIRC, Python itself doesn't read those registry entries, except when installing
pre-compiled .msi or .exe kits. Once you have Python installed, you can move
the directory someplace else, then install another version of Python.
If you need to
On Tue, Nov 26, 2013 at 12:42 AM, Jurko Gospodnetić
wrote:
> Yup, we could do that, but at first glance it really smells like an
> overkill. Not to mention the potential licensing issues with Windows and an
> unlimited number of Windows installations. :-)
Ah, heh... didn't think of that. When I
Hi.
On 25.11.2013. 14:04, Chris Angelico wrote:
Is it possible to set up virtualization to help you out? Create a
virtual machine in something like VirtualBox, then clone it for every
Python patch you want to support (you could have one VM that handles
all the .0 releases and another that hand
On Mon, 11/25/13, Jurko Gospodnetić wrote:
Subject: Parallel Python x.y.A and x.y.B installations on a single Windows
machine
To: python-list@python.org
Date: Monday, November 25, 2013, 1:32 PM
Hi all.
I was wondering what is the best way
On Mon, Nov 25, 2013 at 11:32 PM, Jurko Gospodnetić
wrote:
> Most of the advice seems to boil down to 'do not use such versions together,
> use only the latest'.
>
> We would like to run automated tests on one of our projects (packaged as a
> Python library) with different Python versions, and s
On Monday, November 25, 2013 7:32:30 AM UTC-5, Jurko Gospodnetić wrote:
> Hi all.
>
>I was wondering what is the best way to install multiple Python
> installations on a single Windows machine.
>
>Regular Windows installer works great as long as all your
> installations have a separate
13 matches
Mail list logo
