Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #44911 > unrolled thread

multiple versions of python

Back to article view | Back to comp.lang.python

Contents

  multiple versions of python sokovic.anamarija@gmail.com - 2013-05-07 15:26 -0700
    Re: multiple versions of python Roy Smith <roy@panix.com> - 2013-05-07 19:59 -0400
      Re: multiple versions of python Fábio Santos <fabiosantosart@gmail.com> - 2013-05-08 08:07 +0100
    Re: multiple versions of python "Colin J. Williams" <cjw@ncf.ca> - 2013-05-07 21:35 -0400
      Re: multiple versions of python Roy Smith <roy@panix.com> - 2013-05-07 21:38 -0400
      Re: multiple versions of python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-05-08 03:25 +0100

#44911 — multiple versions of python

Hi,

what is the generally recommended structure when we have into play this type of problem:
multiple versions of python (both in the sense of main versions and sub versions, e.g., 
2.7 :
   2.7.1
   2.7.3
3:
 3.3
   3.3.1
Different versions of gcc
different compilation strategies (-vanilla and non-vanilla)
different modules (numpy,scipy) together with the different versions of all the rest.

any help is appreciated

Ana

[toc] | [next] | [standalone]

#44917

In article <72f93710-9812-441e-8d3d-f221d5698f69@googlegroups.com>,
 sokovic.anamarija@gmail.com wrote:

> Hi,
> 
> what is the generally recommended structure when we have into play this type 
> of problem:
> multiple versions of python (both in the sense of main versions and sub 
> versions, e.g., 
> 2.7 :
>    2.7.1
>    2.7.3
> 3:
>  3.3
>    3.3.1
> Different versions of gcc
> different compilation strategies (-vanilla and non-vanilla)
> different modules (numpy,scipy) together with the different versions of all 
> the rest.
> 
> any help is appreciated
> 
> Ana

Virtualenv is your friend.

[toc] | [prev] | [next] | [standalone]

#44943

[Multipart message — attachments visible in raw view] — view raw

On 8 May 2013 01:03, "Roy Smith" <roy@panix.com> wrote:
>
> In article <72f93710-9812-441e-8d3d-f221d5698f69@googlegroups.com>,
>  sokovic.anamarija@gmail.com wrote:
>
> > Hi,
> >
> > what is the generally recommended structure when we have into play this
type
> > of problem:
> > multiple versions of python (both in the sense of main versions and sub
> > versions, e.g.,
> > 2.7 :
> >    2.7.1
> >    2.7.3
> > 3:
> >  3.3
> >    3.3.1
> > Different versions of gcc
> > different compilation strategies (-vanilla and non-vanilla)
> > different modules (numpy,scipy) together with the different versions of
all
> > the rest.
> >
> > any help is appreciated
> >
> > Ana
>
> Virtualenv is your friend.
> --
> http://mail.python.org/mailman/listinfo/python-list

Have you looked at tox? It manages a folder full of virtualenvs for you,
including your dependencies, and allows you to run your tests against every
version.

[toc] | [prev] | [next] | [standalone]

#44929

On 07/05/2013 6:26 PM, sokovic.anamarija@gmail.com wrote:
> Hi,
>
> what is the generally recommended structure when we have into play this type of problem:
> multiple versions of python (both in the sense of main versions and sub versions, e.g.,
> 2.7 :
>     2.7.1
>     2.7.3
> 3:
>   3.3
>     3.3.1
> Different versions of gcc
> different compilation strategies (-vanilla and non-vanilla)
> different modules (numpy,scipy) together with the different versions of all the rest.
>
> any help is appreciated
>
> Ana
>
Do you really need more than 2.7.3  and 3.3.1.

Typically, these go to C:\Python27 and C:\Python33 with windows.

Colin W.

[toc] | [prev] | [next] | [standalone]

#44930

In article <kmca64$pd3$1@theodyn.ncf.ca>,
 "Colin J. Williams" <cjw@ncf.ca> wrote:

> Do you really need more than 2.7.3  and 3.3.1.

It's often useful to have older versions around, so you can test your 
code against them.  Lots of projects try to stay compatible with older 
releases.

[toc] | [prev] | [next] | [standalone]

#44936

On 08/05/2013 02:35, Colin J. Williams wrote:
> On 07/05/2013 6:26 PM, sokovic.anamarija@gmail.com wrote:
>> Hi,
>>
>> what is the generally recommended structure when we have into play
>> this type of problem:
>> multiple versions of python (both in the sense of main versions and
>> sub versions, e.g.,
>> 2.7 :
>>     2.7.1
>>     2.7.3
>> 3:
>>   3.3
>>     3.3.1
>> Different versions of gcc
>> different compilation strategies (-vanilla and non-vanilla)
>> different modules (numpy,scipy) together with the different versions
>> of all the rest.
>>
>> any help is appreciated
>>
>> Ana
>>
> Do you really need more than 2.7.3  and 3.3.1.
>
> Typically, these go to C:\Python27 and C:\Python33 with windows.
>
> Colin W.

In which case you'll normally be doing a binary installation.  If you're 
compiling it's more likely to be VC++ not gcc.

-- 
If you're using GoogleCrap™ please read this 
http://wiki.python.org/moin/GoogleGroupsPython.

Mark Lawrence

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web