On Sat, Oct 6, 2012 at 1:27 AM, wrote:
> Using Python on Windows is a dream.
>
> Python uses and needs the system, but the system does
> not use Python.
>
> Every Python version is installed in its own isolated
> space, site-packages included and without any defined
> environment variable. Every
Using Python on Windows is a dream.
Python uses and needs the system, but the system does
not use Python.
Every Python version is installed in its own isolated
space, site-packages included and without any defined
environment variable. Every Python can be seen as a
different application.
Knowing
On 10/5/2012 5:32 PM, Dennis Lee Bieber wrote:
On Fri, 05 Oct 2012 08:15:30 -0400, Edward Diener
declaimed the following in
gmane.comp.python.general:
Windows installs of Python do not distinguish releases by Pythonx(.x)
but just install different versions of Python in different directories.
On 05/10/2012 13:15, Edward Diener wrote:
On 10/1/2012 12:02 PM, Alister wrote:
On Sun, 30 Sep 2012 15:14:17 -0400, Edward Diener wrote:
Has there been any official software that allows both the Python 2.x and
3.x releases to coexist on the same OS so that the end-user can easily
switch betwee
On 9/30/2012 3:38 PM, Andrew Berg wrote:
On 2012.09.30 14:14, Edward Diener wrote:
The situation is so confusing on Windows, where the file associations,
registry entries, and other internal software which allows a given
Python release to work properly when invoking Python is so complicated,
tha
On 10/1/2012 12:02 PM, Alister wrote:
On Sun, 30 Sep 2012 15:14:17 -0400, Edward Diener wrote:
Has there been any official software that allows both the Python 2.x and
3.x releases to coexist on the same OS so that the end-user can easily
switch between them when invoking Python scripts after e
On 10/1/2012 1:32 PM, Dennis Lee Bieber wrote:
On Sun, 30 Sep 2012 23:06:04 -0400, Edward Diener
declaimed the following in
gmane.comp.python.general:
My thought is a program distributed by Python which finds the versions
of Python on an OS, lets the end-user choose which version should be
in
On 01/10/2012 20:36, David Robinow wrote:
On Sun, Sep 30, 2012 at 11:55 PM, Dave Angel wrote:
The problem with that is that one has to already being using 3.3 to
use this facility. I was hoping for a solution which was backwards
compatible with Python 2.x.
...
That does not solve the problem fo
On Sun, Sep 30, 2012 at 11:55 PM, Dave Angel wrote:
>> The problem with that is that one has to already being using 3.3 to
>> use this facility. I was hoping for a solution which was backwards
>> compatible with Python 2.x.
>>...
>> That does not solve the problem for Python 2.x distributions.
> I
On Sun, 30 Sep 2012 15:14:17 -0400, Edward Diener wrote:
> Has there been any official software that allows both the Python 2.x and
> 3.x releases to coexist on the same OS so that the end-user can easily
> switch between them when invoking Python scripts after each has been
> installed to their o
On 01/10/2012 04:06, Edward Diener wrote:
On 9/30/2012 3:38 PM, Andrew Berg wrote:
Unix-based OSes should already obey the shebang line, and on Windows,
there's py.exe in 3.3 that will launch the intended version based on
that shebang line.
The problem with that is that one has to already bein
On 09/30/2012 11:06 PM, Edward Diener wrote:
> On 9/30/2012 3:38 PM, Andrew Berg wrote:
>> On 2012.09.30 14:14, Edward Diener wrote:
>>> The situation is so confusing on Windows, where the file associations,
>>> registry entries, and other internal software which allows a given
>>> Python release t
On 2012.09.30 22:06, Edward Diener wrote:
> The problem with that is that one has to already being using 3.3 to use
> this facility. I was hoping for a solution which was backwards
> compatible with Python 2.x.
It's a separate tool that comes with 3.3. You can install 3.3 and never
use the actual
On 9/30/2012 3:38 PM, Andrew Berg wrote:
On 2012.09.30 14:14, Edward Diener wrote:
The situation is so confusing on Windows, where the file associations,
registry entries, and other internal software which allows a given
Python release to work properly when invoking Python is so complicated,
tha
On 2012.09.30 14:14, Edward Diener wrote:
> The situation is so confusing on Windows, where the file associations,
> registry entries, and other internal software which allows a given
> Python release to work properly when invoking Python is so complicated,
> that I have given up on trying to in
15 matches
Mail list logo
