On 8 May 2013 01:03, Roy Smith r...@panix.com 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
of problem:
multiple versions of python (both
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
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 sub
versions, e.g.,
2.7
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
In article kmca64$pd3$1...@theodyn.ncf.ca,
Colin J. Williams c...@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.
--
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
2012/10/19 Michele Simionato michele.simion...@gmail.com:
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
Did you take a look at https://www.shiningpanda-ci.com/?
2012/10/19 andrea crotti andrea.crott...@gmail.com:
2012/10/19 Michele Simionato michele.simion...@gmail.com:
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.
Michele Simionato michele.simion...@gmail.com 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
ShiningPanda looks really really cool. I need to investigate it.
--
http://mail.python.org/mailman/listinfo/python-list
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
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 a
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.
Hm, it's
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 the
associated
with the .py extension. And it does not matter in either case what
version
of the multiple installed versions of Python which are on my system is
currently executing that script.
And please don't say that there is some sort of guarantee that no
library or
installation would
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 command
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 through
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
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
, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
If you let .py scripts specify which interpreter they'd like to be run
with in the first line, with some sort of pystarter script that you map
to the file
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 not work
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.
This
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
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
use either
internally.
Maybe it's just me, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
Whether it is badly written or not in your opinion it is legal and
happens all the time. Are you going to refuse
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 fact
Python externally, any already written script can use either
internally.
Maybe it's just me, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
Whether it is badly written or not in your opinion it is legal
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
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
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.executable
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 of the
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 py2exe,
as
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 be
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.executable will not work
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
the console or file association method
of invoking Python externally, any already written script can use either
internally.
Maybe it's just me, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
Whether it is badly
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
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
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
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, you are heading
down a path of endless problems.
What
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, you are heading
down
of invoking Python externally, any already written script can
use either internally.
Maybe it's just me, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
Whether it is badly written or not in your opinion
of the multiple installed versions of Python which are on my system is
currently executing that script.
And please don't say that there is some sort of guarantee that no library or
installation would invoke Python in such a way as opposed to the normal
'import AScript.py' method of using
uses the console or file association
method of invoking Python externally, any already written script can
use either internally.
Maybe it's just me, but I think that a script that does this is quite
simply badly written: it *will* break on systems that have multiple
Python versions.
Whether
not matter in either case what version
of the multiple installed versions of Python which are on my system is
currently executing that script.
And please don't say that there is some sort of guarantee that no library or
installation would invoke Python in such a way as opposed to the normal
'import
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 name them
appropriately so you can launch the appropriate version from
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
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
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
On Sat, Jul 24, 2010 at 7:40 PM, Edward Diener
eldie...@tropicsoft.invalid 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
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
On Thu, Mar 11, 2010 at 12:40 AM, Bujji sivait...@gmail.com 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
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
, 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/foo. Then Python will place
of files 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/foo
Tim Arnold tim.arn...@sas.com 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
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
On Aug 13, 12:57 pm, Tim Arnold tim.arn...@sas.com 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
On Thu, Aug 13, 2009 at 12:57 PM, Tim Arnoldtim.arn...@sas.com 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
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 Python packages for multiple
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 ftype
CCW wrote:
On 21 July, 15:19, Dave Angel da...@dejaviewphoto.com 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
CCW wrote:
On 21 July, 15:19, Dave Angel da...@dejaviewphoto.com 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
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
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
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
On 21 July, 15:19, Dave Angel da...@dejaviewphoto.com 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
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 Interpreter.
Here
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?
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 extensions
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.
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,
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
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:
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
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;
nor
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 source
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. You may
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
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 word,
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
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?
Is there some way to specify a default
version
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
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 tree.
Is there some
On approximately 12/1/2008 11:05 PM, came the following characters from
the keyboard of Martin v. Löwis:
Is there some way to specify a default version in such a way that it can
be changed as necessary?
What do you mean by default version?
There is the version that is associated with the
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
Glenn Linderman wrote:
When using multiple versions of Python co-installed on the same system,
what happens with local .pyc files? If the .py is loaded with a
different version of Python, is the .pyc rebuilt (even if the .py hasn't
changed)?
Or must one manually delete the .pyc files
On Wed, Oct 29, 2008 at 11:50 AM, Glenn Linderman [EMAIL PROTECTED] wrote:
When using multiple versions of Python co-installed on the same system,
what happens with local .pyc files? If the .py is loaded with a
different version of Python, is the .pyc rebuilt (even if the .py hasn't
changed
I am running OS X and have Python 2.3 installed with the system and
have installed 2.5 using the installer available at pythonmac.org. I
am running the system install of Apache 1.3 and I am not using
mod_python.
When Apache 1.3 runs Python cgi scripts, the cgitb output indicates
that the verision
I have a suse box that has by default python 2.4 running and I have a
2.5 version installed
in /reg/python2.5. How do I install new modules for only 2.5 without
disturbing the 2.4 default
installation.
If you do 'python2.5 setup.py install' on a new module supporting
distutils it will only
I have a suse box that has by default python 2.4 running and I have a
2.5 version installed
in /reg/python2.5. How do I install new modules for only 2.5 without
disturbing the 2.4 default
installation.
Thanks,
--j
--
http://mail.python.org/mailman/listinfo/python-list
In article [EMAIL PROTECTED],
Cowmix [EMAIL PROTECTED] wrote:
What is the best way to run multiple version of Python on the same
system?
You could use chroot. Ask if you want more details.
--
http://mail.python.org/mailman/listinfo/python-list
Cowmix wrote:
For my day job I am forced to run RHEL3 (and Centos3 on my desktop). I
want to be able to use a few applications that require Python 2.4.X but
RHEL3 ships with Python 2.2.3. I have tried to install and upgrade
Python 2.4.X many ways like using PyVault and doing a source based
Cowmix wrote:
For my day job I am forced to run RHEL3 (and Centos3 on my desktop). I
want to be able to use a few applications that require Python 2.4.X but
RHEL3 ships with Python 2.2.3. I have tried to install and upgrade
Python 2.4.X many ways like using PyVault and doing a source based
For my day job I am forced to run RHEL3 (and Centos3 on my desktop). I
want to be able to use a few applications that require Python 2.4.X but
RHEL3 ships with Python 2.2.3. I have tried to install and upgrade
Python 2.4.X many ways like using PyVault and doing a source based
install but each way
I have Python 2.1 / PythonWin 2.1 installed on my machine because I
need it for use with ESRI's ArcGIS Desktop software, but I want to play
with a more recent version of Python.
Is it safe to install more than one version of Python / PythonWin on
the same machine? I don't want the latest release
[EMAIL PROTECTED] a écrit :
Is it safe to install more than one version of Python / PythonWin on
the same machine?
Sure, it is, just specify a different path for the installer. You'll
probably want to create two scripts python21.bat and python24.bat and
put them in your path to launch the
[EMAIL PROTECTED] wrote:
I have Python 2.1 / PythonWin 2.1 installed on my machine because I
need it for use with ESRI's ArcGIS Desktop software, but I want to play
with a more recent version of Python.
Is it safe to install more than one version of Python / PythonWin on
the same machine? I
98 matches
Mail list logo
