Re: multiple versions of python

On 8 May 2013 01:03, "Roy Smith" wrote: > > In article <72f93710-9812-441e-8d3d-f221d5698...@googlegroups.com>, > sokovic.anamar...@gmail.com wrote: > > > Hi, > > > > what is the generally recommended structure when we have into play this type &

Re: multiple versions of python

On 08/05/2013 02:35, Colin J. Williams wrote: On 07/05/2013 6:26 PM, sokovic.anamar...@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

Re: multiple versions of python

In article , "Colin J. Williams" 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. -- http://mail.python.org/mailman/listinfo/python-li

Re: multiple versions of python

On 07/05/2013 6:26 PM, sokovic.anamar...@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

Re: multiple versions of python

In article <72f93710-9812-441e-8d3d-f221d5698...@googlegroups.com>, sokovic.anamar...@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

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

Re: Testing against multiple versions of Python

ShiningPanda looks really really cool. I need to investigate it. -- http://mail.python.org/mailman/listinfo/python-list

Re: Testing against multiple versions of Python

Michele Simionato wrote: > Yesterday I released a new version of the decorator module. It should > run under Python 2.4, 2.5, 2.6, 2.7, 3.0, 3.1, 3.2, 3.3. I did not > have the will to install on my machine 8 different versions of Python, > so I just tested it with Python 2.7 and 3.3. But I do no

Re: Testing against multiple versions of Python

Did you take a look at https://www.shiningpanda-ci.com/? 2012/10/19 andrea crotti : > 2012/10/19 Michele Simionato : >> Yesterday I released a new version of the decorator module. It should run >> under Python 2.4, 2.5, 2.6, 2.7, 3.0, 3.1, 3.2, 3.3. I did not have the will >> to install on my ma

Re: Testing against multiple versions of Python

2012/10/19 Michele Simionato : > Yesterday I released a new version of the decorator module. It should run > under Python 2.4, 2.5, 2.6, 2.7, 3.0, 3.1, 3.2, 3.3. I did not have the will > to install on my machine 8 different versions of Python, so I just tested it > with Python 2.7 and 3.3. But

Testing against multiple versions of Python

Yesterday I released a new version of the decorator module. It should run under Python 2.4, 2.5, 2.6, 2.7, 3.0, 3.1, 3.2, 3.3. I did not have the will to install on my machine 8 different versions of Python, so I just tested it with Python 2.7 and 3.3. But I do not feel happy with that. Is there

Re: ActivePython: multiple versions on OSX?

On Mon, Jul 25, 2011 at 5:18 PM, Robert wrote: > Is it possible to install the 2 and 3 series side by side? > Yup. Moreover, ActivePython includes a tool called `pythonselect` that can be used to set the "current" version of Python, https://github.com/ActiveState/pythonselect#readme For OSX, th

Re: ActivePython: multiple versions on OSX?

Why not use Virtualenv ? http://pypi.python.org/pypi/virtualenv On Mon, Jul 25, 2011 at 5:18 PM, Robert wrote: > Is it possible to install the 2 and 3 series side by side? > > -- > Robert > > > -- > http://mail.python.org/**mailman/listinfo/python-list

Re: ActivePython: multiple versions on OSX?

In article , Melton Low wrote: [...] > On Mac OS X, a link is automatically installed in /usr/local/bin for each > version of the Python executables, ie python2.7 for the 2.7.x and python3.2 > for 3.2.x. Just invoke your script with the appropriate Python version. > eg. python3.2 yourscript t

Re: ActivePython: multiple versions on OSX?

It's definitely possible. I've done it myself. On Jul 25, 2011 8:21 PM, "Robert" wrote: > Is it possible to install the 2 and 3 series side by side? > > -- > Robert > > > -- > http://mail.python.org/mailman/listinfo/python-list -- http://mail.python.org/mailman/listinfo/python-list

Re: ActivePython: multiple versions on OSX?

On Wed, Jul 27, 2011 at 2:33 AM, Melton Low wrote: > It's probably impractical.  You would need a pair for each version of Python > installed, ie. (PYTHON26PATH,PYTHON26HOME) for 2.6.x, > (PYTHON27PATH,PYTHON27HOME) for 2.7.x, for 3.1.x, for 3.2.x, etc). You could set up a script for each ve

Re: ActivePython: multiple versions on OSX?

On Tue, Jul 26, 2011 at 9:53 AM, Web Dreamer wrote: > John Roth a écrit ce mardi 26 juillet 2011 14:00 dans <75342033- > abbb-4d59-9654-96d5031dc...@r28g2000prb.googlegroups.com> : > > > On Jul 25, 8:18 pm, Ned Deily wrote: > >> In article , Robert > >> wrote: > >> > >> > Is it possible to inst

Re: ActivePython: multiple versions on OSX?

On Jul 25, 8:18 pm, Ned Deily wrote: > In article , Robert > wrote: > > > Is it possible to install the 2 and 3 series side by side? > > Probably.  On Mac OS X, t's certainly possible to install any python.org > versions side by side, even multiple versions of

Re: ActivePython: multiple versions on OSX?

In article , Robert wrote: > Is it possible to install the 2 and 3 series side by side? Probably. On Mac OS X, t's certainly possible to install any python.org versions side by side, even multiple versions of 2 and 3. That's one of the advantages of the Python framework build

ActivePython: multiple versions on OSX?

Is it possible to install the 2 and 3 series side by side? -- Robert -- http://mail.python.org/mailman/listinfo/python-list

Re: Multiple versions of Python coexisting in the same OS

On 07/26/2010 06:36 AM, Edward Diener wrote: > On 7/25/2010 10:42 PM, David Robinow wrote: >> On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener >> wrote: >>> On 7/25/2010 5:57 PM, Thomas Jollans wrote: >>> So if a standard library module ( or distributed library ) executes a >>> call >>> internally

Re: Multiple versions of Python coexisting in the same OS

On 07/26/2010 06:36 AM, Edward Diener wrote: > > I start a Python script for version X by going to X's root directory and > invoking 'python someScript.py' from the command line. Does that not > sound reasonable ? Do you have an example of two (not self written) applications requiring to change t

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 10:39 PM, MRAB wrote: > News123 wrote: >> Thus my idea of having a pystarter with a config file >> mentioning which directories (tools) should use which python executable >> > I think that's the wrong way round. A pystarter should ask the _tool_ > which version of Python it needs.

Re: Multiple versions of Python coexisting in the same OS

>> >> Thus my idea of having a pystarter with a config file >> mentioning which directories (tools) should use which python executable > > Well, good luck ! I don;t know how this is resolved for you when some > scripts executes 'python xxx yyy' or 'someScript.py yyy'. both could be resolved with

Re: Multiple versions of Python coexisting in the same OS

Python script for version X by going to X's root directory and > invoking 'python someScript.py' from the command line. Does that not > sound reasonable ? No it doesn't, it's a very unreasonable thing to do. If you have multiple versions of Python, you should n

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 10:42 PM, David Robinow wrote: On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener wrote: On 7/25/2010 5:57 PM, Thomas Jollans wrote: So if a standard library module ( or distributed library ) executes a call internally to 'python xxx yyy' or executes a call internally to 'someScript.p

Re: Multiple versions of Python coexisting in the same OS

Whether it is badly written or not in your opinion it is legal and happens all the time. Yes, people write poorly written, buggy scripts all the time. Just because code is legal syntax doesn't mean it does what is intended, or that what is intended is sensible. If you have multiple ver

Re: Multiple versions of Python coexisting in the same OS

On Sun, Jul 25, 2010 at 8:40 PM, Edward Diener wrote: > On 7/25/2010 5:57 PM, Thomas Jollans wrote: > So if a standard library module ( or distributed library ) executes a call > internally to 'python xxx yyy' or executes a call internally to > 'someScript.py yyy', you're fine with multiple co-exi

Re: Multiple versions of Python coexisting in the same OS

t have multiple >> Python versions. > > Whether it is badly written or not in your opinion it is legal and > happens all the time. Yes, people write poorly written, buggy scripts all the time. Just because code is legal syntax doesn't mean it does what is intended, or that w

Re: Multiple versions of Python coexisting in the same OS

sys.executable is the best way if you have to start a new Python interpreter. However sys.executable may not be set for NT services. So there may be a problem after all. Once you start instrusively changing scripts to find a solution to multiple versions of Python co-existing in one system,

Re: Multiple versions of Python coexisting in the same OS

rue that sys.executable is the best way if you have to start a new >> Python interpreter. However sys.executable may not be set for NT >> services. So there may be a problem after all. >> > > Once you start instrusively changing scripts to find a solution to > multip

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 4:26 PM, News123 wrote: On 07/25/2010 10:18 PM, Thomas Jollans wrote: On 07/25/2010 10:04 PM, News123 wrote: sOn 07/25/2010 09:39 PM, Christian Heimes wrote: Am 25.07.2010 21:32, schrieb Thomas Jollans: If a script uses sys.executable instead of "python", there is no problem, at

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 4:22 PM, News123 wrote: On 07/25/2010 09:33 PM, Edward Diener wrote: On 7/25/2010 10:31 AM, News123 wrote: On 07/25/2010 02:46 PM, Edward Diener wrote: On 7/25/2010 6:07 AM, Gelonida wrote: How does a 'pystarter' program know where the file's location is which is being invoked

Re: Multiple versions of Python coexisting in the same OS

.executable may not be set for NT services. So there may be a problem after all. Once you start instrusively changing scripts to find a solution to multiple versions of Python co-existing in one system, you are heading down a path of endless problems. -- http://mail.python.org/mailman/listinfo/python-list

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 3:32 PM, Thomas Jollans wrote: On 07/25/2010 09:19 PM, Edward Diener wrote: On 7/25/2010 10:03 AM, Thomas Jollans wrote: On 07/25/2010 02:46 PM, Edward Diener wrote: The problem with this is that you forget that a script can invoke Python internally. So whether one uses the consol

Re: Multiple versions of Python coexisting in the same OS

News123 wrote: On 07/25/2010 09:33 PM, Edward Diener wrote: On 7/25/2010 10:31 AM, News123 wrote: On 07/25/2010 02:46 PM, Edward Diener wrote: On 7/25/2010 6:07 AM, Gelonida wrote: How does a 'pystarter' program know where the file's location is which is being invoked ? the file's locatio

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 10:18 PM, Thomas Jollans wrote: > On 07/25/2010 10:04 PM, News123 wrote: >> sOn 07/25/2010 09:39 PM, Christian Heimes wrote: >>> Am 25.07.2010 21:32, schrieb Thomas Jollans: If a script uses sys.executable instead of "python", there is no problem, at all. >> >> >> sys.execut

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 09:33 PM, Edward Diener wrote: > On 7/25/2010 10:31 AM, News123 wrote: >> On 07/25/2010 02:46 PM, Edward Diener wrote: >>> On 7/25/2010 6:07 AM, Gelonida wrote: > > How does a 'pystarter' program know where the file's location is which > is being invoked ? the file's location would

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 10:04 PM, News123 wrote: > sOn 07/25/2010 09:39 PM, Christian Heimes wrote: >> Am 25.07.2010 21:32, schrieb Thomas Jollans: >>> If a script uses sys.executable instead of "python", there is no >>> problem, at all. > > > sys.executable will not work with scripts converted with py2e

Re: Multiple versions of Python coexisting in the same OS

sOn 07/25/2010 09:39 PM, Christian Heimes wrote: > Am 25.07.2010 21:32, schrieb Thomas Jollans: >> If a script uses sys.executable instead of "python", there is no >> problem, at all. sys.executable will not work with scripts converted with py2exe, as sys.executable will not be the executable o

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 09:39 PM, Christian Heimes wrote: > Am 25.07.2010 21:32, schrieb Thomas Jollans: >> If a script uses sys.executable instead of "python", there is no >> problem, at all. > > It's true that sys.executable is the best way if you have to start a new > Python interpreter. However sys.exec

Re: Multiple versions of Python coexisting in the same OS

Am 25.07.2010 21:32, schrieb Thomas Jollans: > If a script uses sys.executable instead of "python", there is no > problem, at all. It's true that sys.executable is the best way if you have to start a new Python interpreter. However sys.executable may not be set for NT services. So there may be a p

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 10:31 AM, News123 wrote: On 07/25/2010 02:46 PM, Edward Diener wrote: On 7/25/2010 6:07 AM, Gelonida wrote: There the windows solution could be something like a small 'pystarter' program, which would decide depending on the file's location / the file's first line which python sho

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 09:19 PM, Edward Diener wrote: > On 7/25/2010 10:03 AM, Thomas Jollans wrote: >> On 07/25/2010 02:46 PM, Edward Diener wrote: >>> The problem with this is that you forget that a script can invoke Python >>> internally. So whether one uses the console or file association method >>> of

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 09:12 PM, Edward Diener wrote: > On 7/25/2010 1:51 PM, Joel Goldstick wrote: >> There is this: >> http://pypi.python.org/pypi/virtualenv > > It appears to be only for Linux. I don't know where you get that impression from. I don't know how well it works on which platforms, but the f

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 10:03 AM, Thomas Jollans wrote: On 07/25/2010 02:46 PM, Edward Diener wrote: The problem with this is that you forget that a script can invoke Python internally. So whether one uses the console or file association method of invoking Python externally, any already written script can

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 1:51 PM, Joel Goldstick wrote: Edward Diener wrote: Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and 3.1.2 into completel

Re: Multiple versions of Python coexisting in the same OS

Edward Diener wrote: Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and 3.1.2 into completely folders, but immediately ran into serious

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 02:46 PM, Edward Diener wrote: > On 7/25/2010 6:07 AM, Gelonida wrote: >> Hi Edward, >> >> There the windows solution could be something like a small 'pystarter' >> program, which would decide depending on the file's location / the >> file's first line which python should be started.

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 02:46 PM, Edward Diener wrote: > On 7/25/2010 6:07 AM, Gelonida wrote: >> There the windows solution could be something like a small 'pystarter' >> program, which would decide depending on the file's location / the >> file's first line which python should be started. > > This does n

Re: Multiple versions of Python coexisting in the same OS

On 07/25/2010 02:46 PM, Edward Diener wrote: > The problem with this is that you forget that a script can invoke Python > internally. So whether one uses the console or file association method > of invoking Python externally, any already written script can use either > internally. Maybe it's just

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 2:20 AM, Steven D'Aprano wrote: On Sat, 24 Jul 2010 22:03:48 -0700, Chris Rebert wrote: Are the .py and .pyc extensions the only ones which are associated with Python or are there others, for a normal Python installation in Windows ? There's also .pyw Also .pyo .py = Python so

Re: Multiple versions of Python coexisting in the same OS

On 7/25/2010 6:07 AM, Gelonida wrote: Hi Edward, On 07/25/2010 04:40 AM, Edward Diener wrote: I found the solutions too exotic for actual use, and completely ineffectual for the cases I originally cited. The people in that thread seem to have completely forgotten that Python can be invoked ext

Re: Multiple versions of Python coexisting in the same OS

Hi Edward, On 07/25/2010 04:40 AM, Edward Diener wrote: > I found the solutions too exotic for actual use, and completely > ineffectual for the cases I originally cited. The people in that thread > seem to have completely forgotten that Python can be invoked externally > and internally both throu

Re: Multiple versions of Python coexisting in the same OS

On Sat, 24 Jul 2010 22:03:48 -0700, Chris Rebert wrote: >> Are the .py and .pyc extensions the only ones which are associated with >> Python or are there others, for a normal Python installation in Windows >> ? > > There's also .pyw Also .pyo .py = Python source code, usually associated with c

Re: Multiple versions of Python coexisting in the same OS

On Sat, Jul 24, 2010 at 7:40 PM, Edward Diener wrote: > On 7/24/2010 6:25 AM, Mark Lawrence wrote: >> On 24/07/2010 04:17, Edward Diener wrote: >>> Are there any documents about multiple versionsof Python coexisting in >>> the same OS ( Windows in my case ) and what pitfalls to look out for ? I >>

Re: Multiple versions of Python coexisting in the same OS

On 7/24/2010 6:25 AM, Mark Lawrence wrote: On 24/07/2010 04:17, Edward Diener wrote: Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and

Re: Multiple versions of Python coexisting in the same OS

On 7/24/2010 6:25 AM, Mark Lawrence wrote: On 24/07/2010 04:17, Edward Diener wrote: Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and

Re: Multiple versions of Python coexisting in the same OS

On 24/07/2010 04:17, Edward Diener wrote: Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and 3.1.2 into completely folders, but immediate

Multiple versions of Python coexisting in the same OS

Are there any documents about multiple versionsof Python coexisting in the same OS ( Windows in my case ) and what pitfalls to look out for ? I have already run into a number of them. I installed Python 2.7 and 3.1.2 into completely folders, but immediately ran into serious problems executing a

Re: use of multiple versions of python

On Thu, Mar 11, 2010 at 12:40 AM, Bujji wrote: > hi all, > I have installed python 2.6 in addition to python 2.5 in my system > Now for some modules(while installing ) it needs to use python 2.6 > how can i do that > in case of easy_install what should i do to it to use python 2.6 You should have

use of multiple versions of python

hi all, I have installed python 2.6 in addition to python 2.5 in my system Now for some modules(while installing ) it needs to use python 2.6 how can i do that in case of easy_install what should i do to it to use python 2.6 from my understanding /usr/bin/python is the one which will be taking car

Re: coding for multiple versions of python

"Tim Arnold" wrote in message news:h61gld$it...@foggy.unx.sas.com... > Hi, > I've got a python based system that has to run on hp unix and red hat > linux. The Python version on the HP is 2.4 and the version on the Linux > box is 2.6. There's nothing I can do about that. > > I think that means

Re: coding for multiple versions of python

> He's assuming: >1) an OS that supports symlinks >2) two versions of Python on same system >3) one set of pure-python sources that want to stay in synch for both > versions. Actually, the OP said he has HP(-UX, I assume), and Linux, so it would be two versions of Python on different

Re: coding for multiple versions of python

>> Specifically, put the source code into /net/source/python/foo/*.py. >> Then, on each system, put symlinks to all .py files into >> lib/site-packages/foo. Then Python will place the .pyc files next >> to the symlinks, not next to the actual .py files. > > Why would he need two sets of .py files?

Re: coding for multiple versions of python

es doesn't change too often, you can use symlinks. That's how Debian currently installs Python packages for multiple versions on a single system. Specifically, put the source code into /net/source/python/foo/*.py. Then, on each system, put symlinks to all .py files into lib/site-packages/f

Re: coding for multiple versions of python

#x27;t change too often, you can use symlinks. > That's how Debian currently installs Python packages for multiple > versions on a single system. > > Specifically, put the source code into /net/source/python/foo/*.py. > Then, on each system, put symlinks to all .py files into

Re: coding for multiple versions of python

> I'm guessing I need to configure cvs to copy files to both locations > whenever I commit. Does that sound right? Is there a better way I'm not > thinking of? If the set of files doesn't change too often, you can use symlinks. That's how Debian currently installs

Re: coding for multiple versions of python

On Thu, Aug 13, 2009 at 12:57 PM, Tim Arnold wrote: > Hi, > I've got a python based system that has to run on hp unix and red hat linux. > The Python version on the HP is 2.4 and the version on the Linux box is 2.6. > There's nothing I can do about that. > > I think that means I must have two diffe

Re: coding for multiple versions of python

On Aug 13, 12:57 pm, "Tim Arnold" wrote: > Hi, > I've got a python based system that has to run on hp unix and red hat linux. > The Python version on the HP is 2.4 and the version on the Linux box is 2.6. > There's nothing I can do about that. > > I think that means I must have two different libra

coding for multiple versions of python

Hi, I've got a python based system that has to run on hp unix and red hat linux. The Python version on the HP is 2.4 and the version on the Linux box is 2.6. There's nothing I can do about that. I think that means I must have two different libraries since the pyc files are not cross-version com

Re: Multiple versions of python

On Tue, 21 Jul 2009 10:19:42 -0400, Dave Angel wrote: > The other thing you may want to do in a batch file is to change the file > associations so that you can run the .py file directly, without typing > "python" or "pythonw" in front of it. > > The relevant Windows commands are: assoc and

Re: Multiple versions of python

CCW wrote: On 21 July, 15:19, Dave Angel wrote: The other thing you may want to do in a batch file is to change the file associations so that you can run the .py file directly, without typing "python" or "pythonw" in front of it. The relevant Windows commands are: assoc and ftype And

Re: Multiple versions of python

CCW wrote: On 21 July, 15:19, Dave Angel wrote: ChrisW wrote: Hi, I have installed 2 versions of python on my Windows XP computer - I originally had 3.0.1, but then found that the MySQL module only supported 2.*, so I've now installed that. I have found that if I change the Wi

Re: Multiple versions of python

On 21 July, 15:19, Dave Angel wrote: > ChrisW wrote: > > Hi, > > > I have installed 2 versions of python on my Windows XP computer - I > > originally had 3.0.1, but then found that the MySQL module only > > supported 2.*, so I've now installed that.  I have found that if I > > change the Windows E

Re: Multiple versions of python

ChrisW wrote: Hi, I have installed 2 versions of python on my Windows XP computer - I originally had 3.0.1, but then found that the MySQL module only supported 2.*, so I've now installed that. I have found that if I change the Windows Environment Variable path, then I can change the version of

Re: Multiple versions of python

ChrisW wrote: Hi, I have installed 2 versions of python on my Windows XP computer - I originally had 3.0.1, but then found that the MySQL module only supported 2.*, so I've now installed that. I have found that if I change the Windows Environment Variable path, then I can change the version of

Multiple versions of python

Hi, I have installed 2 versions of python on my Windows XP computer - I originally had 3.0.1, but then found that the MySQL module only supported 2.*, so I've now installed that. I have found that if I change the Windows Environment Variable path, then I can change the version of python called wh

Re: [MacOS] Multiple versions of a module

Pierre-Alain Dorange schrieb: How to manage a module with several versions on MacOS X ? All modules are installed in : "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-pa ckages/" This is the default path for Mac. But for some modules i need several version (stable 1.8.1 an

[MacOS] Multiple versions of a module

How to manage a module with several versions on MacOS X ? All modules are installed in : "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-pa ckages/" This is the default path for Mac. But for some modules i need several version (stable 1.8.1 and test 1.9.0 for example : for p

Re: Multiple Versions of Python on Windows XP

> SciTE doesn't do that, in the default configuration it just uses > whatever is called "pythonw" on the path, for running files having a .py > or .pyw suffix. I see. By default, Python does not put itself onto PATH. Does that mean that SciTE cannot run Python scripts in the default installation?

Re: Multiple Versions of Python on Windows XP

and only if the ftype and assoc have the same content as was created by the corresponding version installation. Here's another approach to handling multiple versions of Python, thanks to the PyScripter List. It does not address the need to access different versions of the Python Interp

Re: Multiple Versions of Python on Windows XP

Glenn Linderman wrote: > I'm unaware of it needing to handle multiple extensions > from the command line or via double clicking in Explorer, so was > exploiting the extra level of indirection to save typing, and make the > command simpler to remember. Python *does* provide multiple useful extensio

Re: Multiple Versions of Python on Windows XP

On approximately 12/4/2008 5:29 AM, came the following characters from the keyboard of Colin J. Williams: Glenn Linderman wrote: The equivalent of those commands is available via Windows Explorer, Tools / Folder Options, File Types, scroll-scroll-scroll your way to .py, Click Advanced, fidd

Re: Multiple Versions of Python on Windows XP

Glenn Linderman wrote: The equivalent of those commands is available via Windows Explorer, Tools / Folder Options, File Types, scroll-scroll-scroll your way to .py, Click Advanced, fiddle, copy paste apply, and other twaddle. Yes, but what's needed is a further level of indirection. Curre

Re: Multiple Versions of Python on Windows XP

On approximately 12/3/2008 8:51 AM, came the following characters from the keyboard of Colin J. Williams: Martin v. Löwis wrote: What changes are made to the registry? For a complete list, see Tools/msi/msi.py in the source tree. I have scanned the file: http://svn.python.org/projects/python/

Re: Multiple Versions of Python on Windows XP

Martin v. Löwis wrote: What changes are made to the registry? For a complete list, see Tools/msi/msi.py in the source tree. I have scanned the file: http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py I don't find anything that addresses this issue. Read the add_registry fu

Re: Multiple Versions of Python on Windows XP

On Dec 1, 4:49 pm, "Colin J. Williams" <[EMAIL PROTECTED]> wrote: > Could anyone please point me to > documentation on the way the msi > installer handles multiple versions eg. > Python 2.5, 2.6 and 3.0? > > What changes are made to the registry? > >

Re: Multiple Versions of Python on Windows XP

Hi! Multiple versions of Python is possible (example: Python standard + Python by OOo). But, multiple versions of Python+PyWin32 is not possible. Suggestion: use VirtualBox or Virtual-PC. @-salutations -- Michel Claveau -- http://mail.python.org/mailman/listinfo/python-list

Re: Multiple Versions of Python on Windows XP

> Using a right click, one can open any .py file with say SciTe. Within > SciTe, one can Run the current file. > > It would be good to have the appropriate version (my use of "default") > preselected. I don't know how SciTe choses the version of Python to run. In the sense in why you use the wor

Re: Multiple Versions of Python on Windows XP

Martin v. Löwis wrote: What changes are made to the registry? For a complete list, see Tools/msi/msi.py in the source tree. I have scanned the file: http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py I don't find anything that addresses this issue. Read the add_registry fun

Re: Multiple Versions of Python on Windows XP

>>> What changes are made to the registry? >> >> For a complete list, see Tools/msi/msi.py in the source tree. > > I have scanned the file: > http://svn.python.org/projects/python/branches/py3k/Tools/msi/msi.py > > I don't find anything that addresses this issue. Read the add_registry function.

Re: Multiple Versions of Python on Windows XP

Martin v. Löwis wrote: Could anyone please point me to documentation on the way the msi installer handles multiple versions eg. Python 2.5, 2.6 and 3.0? I don't think that is documented anywhere. What changes are made to the registry? For a complete list, see Tools/msi/msi.py in the s

Re: Multiple Versions of Python on Windows XP

> OK, Issue 4485 created. My first one, so let me know if I goofed. I > elaborated a bit from the original email, upon reflection. Seemed > useful, but also seemed complex by the time I got done. Looks about right to me. > I don't really have a clue what the uninstaller should do with these; >

Re: Multiple Versions of Python on Windows XP

On approximately 12/1/2008 11:29 PM, came the following characters from the keyboard of Martin v. Löwis: It would be nice if the ftypes were version specific as created by the installer; IIRC, I created the above three from the ftype Python.File as I installed each version. That's a good i

Re: Multiple Versions of Python on Windows XP

> It would be nice if the ftypes were version specific as created by the > installer; IIRC, I created the above three from the ftype Python.File as > I installed each version. That's a good idea; please submit a wish list item to bugs.python.org. There may be issues (such as people relying on this

Re: Multiple Versions of Python on Windows XP

he command line to change the ftype and assoc a bit. Here's how I set up my computer, for multiple versions. Now to change the "default", I just use the assoc command to change the association for .py to one of the three listed ftypes. Simple and quick. c:\>ftype Py

Re: Multiple Versions of Python on Windows XP

> Could anyone please point me to documentation on the way the msi > installer handles multiple versions eg. Python 2.5, 2.6 and 3.0? I don't think that is documented anywhere. > What changes are made to the registry? For a complete list, see Tools/msi/msi.py in the source tre

Multiple Versions of Python on Windows XP

Could anyone please point me to documentation on the way the msi installer handles multiple versions eg. Python 2.5, 2.6 and 3.0? What changes are made to the registry? Is there some way to specify a default version in such a way that it can be changed as necessary? PyScripter uses an

Re: Loading multiple versions of the same package at the same time

della wrote: > On 27 Nov, 21:34, Terry Reedy <[EMAIL PROTECTED]> wrote: > >> > But in the interpreters module dict, foo it is, and stays. >> >> But giving the modules different names on the disk should work, no? > > Yes, but -- for what I've understood -- that wouldn't solve my > original proble

  1   2   >