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
> > of problem:
> > multiple versions of python (both
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 :
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
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 <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.
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
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
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.
>>
>> 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
On Mon, 26 Jul 2010 00:36:47 -0400, Edward Diener wrote:
> On 7/25/2010 10:42 PM, David Robinow wrote:
[...]
>> Edward, I'm having a really hard time understanding your problem. Could
>> you give an example of some real code that is causing you difficulty?
>
> I start a Python script for version
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
On 7/25/2010 8:41 PM, Steven D'Aprano wrote:
On Sun, 25 Jul 2010 15:19:53 -0400, 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 u
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
On Sun, 25 Jul 2010 15:19:53 -0400, 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
>
On 7/25/2010 5:57 PM, Thomas Jollans wrote:
On 07/25/2010 11:10 PM, Edward Diener wrote:
On 7/25/2010 3: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
On 07/25/2010 11:10 PM, Edward Diener wrote:
> On 7/25/2010 3: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 s
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
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
On 7/25/2010 3: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 may n
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
>>
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 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
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
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
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
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
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
> 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:
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
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
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
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
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/
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
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
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
> 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
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
>>> 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.
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
> 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;
>
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
> 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
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 th
> 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
[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 machi
[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
This will work fine for me Tim, thank you for your time!
"Tim Golden" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
(Just to keep things readable, I've reordered the
posts top-to-bottom chronologically. And "Me" is the
cognomen of the original poster, not simply a redundant personal
(Just to keep things readable, I've reordered the
posts top-to-bottom chronologically. And "Me" is the
cognomen of the original poster, not simply a redundant personal
pronoun!)
[Me]
> I need to install both 2.3 and 2.4 on my Win2000 system.
> Can someone please
> give me a pointer as to how to d
Thank you for your reply! Is there a simple way to change the .py/.pyw
associations? Like a registry setting I can "toggle"? Or are there lots of
other things involved, system directory libraries etcetera?
"Tim Golden" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
[Me]
> I need to i
[Me]
> I need to install both 2.3 and 2.4 on my Win2000 system. Can someone
please
> give me a pointer as to how to do this? Thanks!
It depends on your other requirements. The simple answer is: just
install
them (in different directories, eg c:\python23, c:\python24), installing
last the one whi
74 matches
Mail list logo
