which windows python to use?
Hello, Are there any recommendations for which Windows python version to use? I'd like to see a pros-and-cons description of each, given that different uses might dictate different versions. The versions I know (and there are surely more) are: 1) download from www.python.org 2) enthought 3) activepython Are there advantages/disadvantages? I have used enthought before, but it seems as if they are not at 2.4, and may lag behind in versions (which may not be a bad thing). Any other recommendations? thanks, Brian Blais -- - [EMAIL PROTECTED] http://web.bryant.edu/~bblais -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Brian Blais wrote: > Hello, > > Are there any recommendations for which Windows python version to use? > I'd like to see a pros-and-cons description of each, given that > different uses might dictate different versions. The versions I know > (and there are surely more) are: > > 1) download from www.python.org > 2) enthought > 3) activepython FWIW, I would stick to the 'authentic' version of Python (i.e. the first choice). Not that the others are much different, I don't think, but like you said you'll have the newest version from python.org. Also, as a newcomer to Python, I find it more helpful to have to do some things manually, such as installing extra packages/modules that might already come with the other distributions. This way, you learn how to do these things, and you also get a better idea of what really comes with Python and what is bundled on by the other companies. ActivePython is also touted because it comes with an IDE for Windows, but again, it's better to write your code by hand at first and really learn what you're doing. -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Brian Blais wrote: > Hello, > > Are there any recommendations for which Windows python version to use? I'd > like to > see a pros-and-cons description of each, given that different uses might > dictate > different versions. The versions I know (and there are surely more) are: > > 1) download from www.python.org > 2) enthought > 3) activepython > > Are there advantages/disadvantages? I have used enthought before, but it > seems as if > they are not at 2.4, and may lag behind in versions (which may not be a bad > thing). It depends on what you want to do. If you're going to use SciPy (a library for scientific computing), I'd suggest using enthought, as installing SciPy on windows can be a real nightmare for a newbie... Anyway, the enthought edition comes with lots of interesting libraries installed (listed on their homepage), you might want to look at them even if you don't use their distribution. Note that you can have more than one Python installation on the same PC, so you can also work with Python 2.4 (from www.python.org) and switch to enthought for certain projectes if you need it. I haven't looked into ActivePython too much, from what I read it seemed more or less standard python + mark hammonds Win32 utils, but you can install those manually on a plain www.python.org-distribution. -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Brian Blais wrote: > Are there any recommendations for which Windows python version to use? Only if you have criteria. --Scott David Daniels [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Brian Blais wrote: > Are there advantages/disadvantages? I have used enthought before, but it > seems as if > they are not at 2.4, and may lag behind in versions (which may not be a bad > thing). We will be releasing a 2.4 version "shortly" although I'm sure if you search the archives of this list, you will probably see me saying that several times. I will try to get us to push out a public beta release next week. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
On Thursday 11 May 2006 13:38, Brian Blais wrote: > Hello, > > Are there any recommendations for which Windows python version to use? I'd > like to see a pros-and-cons description of each, given that different uses > might dictate different versions. The versions I know (and there are > surely more) are: > > 1) download from www.python.org > 2) enthought > 3) activepython > > Are there advantages/disadvantages? I have used enthought before, but it > seems as if they are not at 2.4, and may lag behind in versions (which may > not be a bad thing). > > Any other recommendations? > As mentioned elsewhere, it depends what your criteria are. Will it be deployed to end users? Your servers? Is python itself being bundled with the program? Is the target a cross-platform or single-platform app? Etc.? If you want "general" advice, here it is: I'd stick with python python and install what extras you need yourself. I've always used the python from python.org and added stuff I need, and I have to be honest, I haven't come across a single comparative disadvantage of doing so yet. Besides, I think installing modules yourself and knowing what's *extra* for an average python-enabled machine is a Good Thing. -- There are 10 types of people in this world, those who understand binary, and those who don't. -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Brian Blais wrote: > Hello, > > Are there any recommendations for which Windows python version to use? > I'd like to see a pros-and-cons description of each, given that > different uses might dictate different versions. The versions I know > (and there are surely more) are: > > 1) download from www.python.org > 2) enthought > 3) activepython > > Are there advantages/disadvantages? I have used enthought before, but > it seems as if they are not at 2.4, and may lag behind in versions > (which may not be a bad thing). > > Any other recommendations? > > > thanks, > > Brian Blais > > Enthought does not play well with cygwin, I've noticed. James -- James Stroud UCLA-DOE Institute for Genomics and Proteomics Box 951570 Los Angeles, CA 90095 http://www.jamesstroud.com/ -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
James Stroud wrote: > Enthought does not play well with cygwin, I've noticed. In what way? Does the mingw gcc that we distribute interfere with Cygwin's gcc? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
hi, if mathematical and numerical algorithm are all you need, then just go for Enthought distribution + Matplotlib. The Enthought distribution provides all packages you need and handy for insatllation! My combo: 1. Enthought Distribution 2. Matplotlib 3. EmEditor Brian Blais wrote: > Hello, > > Are there any recommendations for which Windows python version to use? > I'd like to see a pros-and-cons description of each, given that > different uses might dictate different versions. The versions I know > (and there are surely more) are: > > 1) download from www.python.org > 2) enthought > 3) activepython > > Are there advantages/disadvantages? I have used enthought before, but > it seems as if they are not at 2.4, and may lag behind in versions > (which may not be a bad thing). > > Any other recommendations? > > > thanks, > > Brian Blais > > -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
I tend to do ActivePython because the OSX version seems to come out a bit quicker. Although that might change in the future. Robert -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Robert Kern wrote: > James Stroud wrote: > > >>Enthought does not play well with cygwin, I've noticed. > > > In what way? Does the mingw gcc that we distribute interfere with Cygwin's > gcc? > One can not run the enthought python interactive interpreter from a cygwin x-window session, it locks up. James -- James Stroud UCLA-DOE Institute for Genomics and Proteomics Box 951570 Los Angeles, CA 90095 http://www.jamesstroud.com/ -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
James Stroud wrote:
> Robert Kern wrote:
>
>>James Stroud wrote:
>>
>>>Enthought does not play well with cygwin, I've noticed.
>>
>>In what way? Does the mingw gcc that we distribute interfere with Cygwin's
>>gcc?
>
> One can not run the enthought python interactive interpreter from a
> cygwin x-window session, it locks up.
Interesting. I've seen the same thing with MSYS's rxvt ("native", not X). I
presumed it was a strange interaction between bash and (any) Python. Looks like
it may just be our Python, then. I'll enter a ticket on our Trac. Thank you!
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
--
http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Robert Kern wrote: > In what way? Does the mingw gcc that we distribute interfere with Cygwin's > gcc? Robert: Which C compiler will you be using for the Enthought 2.4 Windows release? Don. -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Robert Kern wrote:
> James Stroud wrote:
>
>>Robert Kern wrote:
>>
>>>James Stroud wrote:
>>>
Enthought does not play well with cygwin, I've noticed.
>>>
>>>In what way? Does the mingw gcc that we distribute interfere with Cygwin's
>>>gcc?
>>
>>One can not run the enthought python interactive interpreter from a
>>cygwin x-window session, it locks up.
>
> Interesting. I've seen the same thing with MSYS's rxvt ("native", not X). I
> presumed it was a strange interaction between bash and (any) Python. Looks
> like
> it may just be our Python, then. I'll enter a ticket on our Trac. Thank you!
My officemate notes that we ship readline. It is possible that readline is
expecting CMD.EXE not a decent terminal.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
--
http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Don Taylor wrote: > Robert Kern wrote: > >>In what way? Does the mingw gcc that we distribute interfere with Cygwin's >>gcc? > > Robert: > > Which C compiler will you be using for the Enthought 2.4 Windows release? Define "using". We build Python with whatever compiler the official build is compiled with. In this case, MSVC 7., I think . For this release, we will ship the latest available gcc available for mingw. Some of the extension modules will be built with this gcc. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
James Stroud wrote: > Robert Kern wrote: > >>James Stroud wrote: >> >>>Enthought does not play well with cygwin, I've noticed. >> >>In what way? Does the mingw gcc that we distribute interfere with Cygwin's >>gcc? > > One can not run the enthought python interactive interpreter from a > cygwin x-window session, it locks up. Our build person tells me that he sees the same problem with the standard build of Python. http://svn.enthought.com/enthought/ticket/715 -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Robert Kern wrote: >>Which C compiler will you be using for the Enthought 2.4 Windows release? > > > Define "using". We build Python with whatever compiler the official build is > compiled with. In this case, MSVC 7., I think . For this release, we > will ship the latest available gcc available for mingw. Some of the extension > modules will be built with this gcc. > I meant to build Python itself. I asked because I was interested in trying your Traits package but could not use it with Python 2.4. I don't have MSVC 7 and I was intimidated by the prospect of building the CTraits extension with either the free MS toolkit or mingw and munging the dlls to conform to the MSVC 7 formats. I just wondered if Enthought's distro for Windows was gcc-based. Don. -- http://mail.python.org/mailman/listinfo/python-list
Re: which windows python to use?
Don Taylor wrote: > Robert Kern wrote: > >>>Which C compiler will you be using for the Enthought 2.4 Windows release? >> >>Define "using". We build Python with whatever compiler the official build is >>compiled with. In this case, MSVC 7., I think . For this release, we >>will ship the latest available gcc available for mingw. Some of the extension >>modules will be built with this gcc. > > I meant to build Python itself. > > I asked because I was interested in trying your Traits package but could > not use it with Python 2.4. I don't have MSVC 7 and I was intimidated > by the prospect of building the CTraits extension with either the free > MS toolkit or mingw and munging the dlls to conform to the MSVC 7 formats. > > I just wondered if Enthought's distro for Windows was gcc-based. The Python interpreter is not. Most of the extension modules we build are. Building stock-2.4 extension modules using mingw works for the most part. It certainly does for Traits as we build Traits using mingw. Most extension modules compiled this way appear to work. There are still some incompatibilities with C++ modules that use iostream and possibly some C modules that use, IIRC, ischar() and friends. Until someone fully ports mingw to use msvcr71.dll as its C runtime, those incompatibilities will remain. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco -- http://mail.python.org/mailman/listinfo/python-list
