ANN: New WinPython with Python 2.7.4 and 3.3.1 (32/64bit)

209 views
Skip to first unread message

Pierre Raybaut

unread,
May 3, 2013, 3:48:25 PM5/3/13
to numpy-discussion, scipy-user, spyd...@googlegroups.com, winp...@googlegroups.com, python-announce-list
Hi all,

I am pleased to announce that four new versions of WinPython have been released yesterday with Python 2.7.4 and 3.3.1, 32 and 64 bits. Many packages have been added or upgraded (see the automatically-generated changelogs). 

Special thanks to Christoph Gohlke for building most of the binary packages bundled in WinPython. 

WinPython is a free open-source portable distribution of Python for Windows, designed for scientists.

It is a full-featured (see http://code.google.com/p/winpython/wiki/PackageIndex) Python-based scientific environment:
  * Designed for scientists (thanks to the integrated libraries NumPy, SciPy, Matplotlib, guiqwt, etc.:
    * Regular *scientific users*: interactive data processing and visualization using Python with Spyder
    * *Advanced scientific users and software developers*: Python applications development with Spyder, version control with Mercurial and other development tools (like gettext)
  * *Portable*: preconfigured, it should run out of the box on any machine under Windows (without any installation requirements) and the folder containing WinPython can be moved to any location (local, network or removable drive)
  * *Flexible*: one can install (or should I write "use" as it's portable) as many WinPython versions as necessary (like isolated and self-consistent environments), even if those versions are running different versions of Python (2.7, 3.3) or different architectures (32bit or 64bit) on the same machine
  * *Customizable*: using the integrated package manager (wppm, as WinPython Package Manager), it's possible to install, uninstall or upgrade Python packages (see http://code.google.com/p/winpython/wiki/WPPM for more details on supported package formats).

*WinPython is not an attempt to replace Python(x,y)*, this is just something different (see http://code.google.com/p/winpython/wiki/Roadmap): more flexible, easier to maintain, movable and less invasive for the OS, but certainly less user-friendly, with less packages/contents and without any integration to Windows explorer [*].

[*] Actually there is an optional integration into Windows explorer, providing the same features as the official Python installer regarding file associations and context menu entry (this option may be activated through the WinPython Control Panel), and adding shortcuts to Windows Start menu.

Enjoy!


Pierre Raybaut

unread,
May 4, 2013, 8:14:23 AM5/4/13
to winp...@googlegroups.com
There is no particular reason for not including SQLAlchemy in WinPython other than the fact that such a distribution can't contain all packages. I already think it contains too much as it is...

-Pierre

Le 4 mai 2013 à 13:29, stonebig <stone...@gmail.com> a écrit :

Hello Pierre,

Thank you very much for this wonderfull tool.

A small question :
- SQLAlchemy is not in winpython3.3.1.0, but seems compatible with Python 3.3,
- is there a special known problem if I do a "pip install SQLAlchemy"  ?

Sheers.
--
You received this message because you are subscribed to the Google Groups "WinPython" group.
To unsubscribe from this group and stop receiving emails from it, send an email to winpython+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Jim Passmore

unread,
May 4, 2013, 10:18:36 AM5/4/13
to winp...@googlegroups.com

On Saturday, May 4, 2013 8:14:23 AM UTC-4, Pierre Raybaut wrote:
There is no particular reason for not including SQLAlchemy in WinPython other than the fact that such a distribution can't contain all packages. I already think it contains too much as it is...

 

Ha, ha!  I assume you would rather put together a smaller base package, and let people install the extras they want.  May be opening a can of worms, but how would you trim it down?  

Jim

Pierre Raybaut

unread,
May 4, 2013, 11:06:34 AM5/4/13
to winp...@googlegroups.com
That's already (more or less) a base package and it's made to be easily customizable: WPPM (and its GUI front end, the "WinPython Control Panel") is all you should need to install/upgrade packages. And if there is a blocking issue with WPPM (it happened before and it will again: it's very very simple but it may not support some packages... That's the price of its simplicity), there are other possibilities from the WinPython command line: easy_install or pip. 

The only reason I would be tempted to remove some packages from the list is a selfish one (I don't use them :-)). And of course, the overall size has to be limited for the installation to be a relatively quick process. 

-Pierre
Message has been deleted
Message has been deleted
Message has been deleted

stonebig

unread,
May 5, 2013, 4:13:07 AM5/5/13
to winp...@googlegroups.com
Hello again,

"Pip install SQLAlchemy" apparently worked, at my second try.

At first try, it failed because :
- I had installed my winpython in a path where a sub-directory was starting per a '$',
     C:\...\$winpython\...\WinPython-32bit-3.3.1.0
- and so the 'distutils' tool, which replaces everything in its command line orders looking like '$*' per the dos variable '*', failed on searching the 'winpython' variable.

You may add a limitation warning on the "portability" section :
Portable: ..... the folder containing WinPython can be moved to any location, PROVIDING there is no directory starting per "$" in the path.
Reply all
Reply to author
Forward
0 new messages