[This announcement is in German since it targets a local user group
meeting in Düsseldorf, Germany]
________________________________________________________________________
ANKÜNDIGUNG
Python Meeting Düsseldorf
http://pyddf.de/
Ein Treffen von Python Enthusiasten und Interessierten
in ungezwungener Atmosphäre.
Dienstag, 22.01.2013, 18:00 Uhr
Clara Schumann Raum
DJH Düsseldorf
Diese Nachricht können Sie auch online lesen:
http://www.egenix.com/company/news/Python-Meeting-Duesseldorf-2013-01-22
________________________________________________________________________
EINLEITUNG
Das Python Meeting Düsseldorf (http://pyddf.de/) ist eine neue
lokale Veranstaltung in Düsseldorf, die sich an Python Begeisterte
in der Region wendet.
Wir starten bei den Treffen mit einer kurzen Einleitung und gehen
dann zu einer Reihe Kurzvorträgen (Lightning Talks) über, bei denen
die Anwesenden über neue Projekte, interessante Probleme und
sonstige Aktivitäten rund um Python berichten können.
Anschließend geht es in eine Gaststätte, um die Gespräche zu
vertiefen.
Einen guten Überblick über die Vorträge bietet unser YouTube-Kanal,
auf dem wir die Vorträge nach den Meetings veröffentlichen:
http://www.youtube.com/pyddf/
Veranstaltet wird das Meeting von der eGenix.com GmbH, Langenfeld,
in Zusammenarbeit mit Clark Consulting & Research, Düsseldorf:
* http://www.egenix.com/
* http://www.clark-consulting.eu/
________________________________________________________________________
ORT
Für das Python Meeting Düsseldorf haben wir den Clara Schumann
Raum in der modernen Jugendherberge Düsseldorf angemietet:
Jugendherberge Düsseldorf
Düsseldorfer Str. 1
40545 Düsseldorf
Telefon: +49 211 557310
http://www.duesseldorf.jugendherberge.de
Die Jugendherberge verfügt über eine kostenpflichtige Tiefgarage (EUR
2,50 pro Stunde, maximal EUR 10,00). Es ist aber auch möglich per
Bus und Bahn anzureisen. Der Raum befindet sich im 1.OG links.
________________________________________________________________________
PROGRAMM
Das Python Meeting Düsseldorf nutzt eine Mischung aus Open Space
und Lightning Talks:
Die Treffen starten mit einer kurzen Einleitung. Danach geht es
weiter mit einer Lightning Talk Session, in der die Anwesenden
Kurzvorträge von fünf Minuten halten können.
Hieraus ergeben sich dann meisten viele Ansatzpunkte für
Diskussionen, die dann den Rest der verfügbaren Zeit in Anspruch
nehmen können.
Für 19:45 Uhr haben wir in einem nahegelegenen Restaurant Plätze
reserviert, damit auch das leibliche Wohl nicht zu kurz kommt.
Lightning Talks können vorher angemeldet werden, oder auch
spontan während des Treffens eingebracht werden. Ein Beamer mit
XGA Auflösung steht zur Verfügung. Folien bitte als PDF auf USB
Stick mitbringen.
Lightning Talk Anmeldung bitte formlos per EMail an info(a)pyddf.de
________________________________________________________________________
KOSTENBETEILIGUNG
Das Python Meeting Düsseldorf wird von Python Nutzern für Python
Nutzer veranstaltet.
Da Tagungsraum, Beamer, Internet und Getränke Kosten produzieren,
bitten wir die Teilnehmer um einen Beitrag in Höhe von EUR 10,00
inkl. 19% Mwst.
Wir möchten alle Teilnehmer bitten, den Betrag in bar mitzubringen.
________________________________________________________________________
ANMELDUNG
Da wir nur für ca. 20 Personen Sitzplätze haben, möchten wir
bitten, sich per EMail anzumelden. Damit wird keine Verpflichtung
eingegangen. Es erleichtert uns allerdings die Planung.
Meeting Anmeldung bitte formlos per EMail an info(a)pyddf.de
________________________________________________________________________
WEITERE INFORMATIONEN
Weitere Informationen finden Sie auf der Webseite des Meetings:
http://pyddf.de/
Mit freundlichen Grüßen,
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1, Dec 28 2012)
>>> Python Projects, Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope/Plone.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
________________________________________________________________________
2013-01-22: Python Meeting Duesseldorf ... 25 days to go
::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
http://www.egenix.com/company/contact/
Good news everyone! Eventlet 0.10 is officially released.
http://pypi.python.org/pypi/eventlet/0.10.0
What is it? Eventlet is a concurrent networking library for Python that allows you to change how you run your code, not how you write it. Same robust, simple threaded code with powerful epoll/kqueue mechanisms underneath to serve thousands of concurrent connections.
Project is no longer orphaned. We have:
* releases going
* roadmap for next year
* official Github mirror https://github.com/eventlet/eventlet
* Google+ community https://plus.google.com/communities/102444398246193806164
Now this and few next releases are bug fixes only, meaning Eventlet gets more and more robust.
Changes:
* greenio: Fix relative seek() (thanks to AlanP)
* db_pool: Fix pool.put() TypeError with min_size > 1 (thanks to Jessica Qi)
* greenthread: Prevent infinite recursion with linking to current
greenthread (thanks to Edward George)
* zmq: getsockopt(EVENTS) wakes correct threads (thanks to Eric Windisch)
* wsgi: Handle client disconnect while sending response (thanks to Clay Gerrard)
* hubs: Ensure that new hub greenlet is parent of old one (thanks to
Edward George)
* os: Fix waitpid() returning (0, 0) (thanks to Vishvananda Ishaya)
* tpool: Add set_num_threads() method to set the number of tpool
threads (thanks to David Ibarra)
* threading, zmq: Fix Python 2.5 support (thanks to Floris Bruynooghe)
* tests: tox configuration for all supported Python versions (thanks
to Floris Bruynooghe)
* tests: Fix zmq._QueueLock test in Python2.6
* tests: Fix patcher_test on Darwin (/bin/true issue) (thanks to Edward George)
* tests: Skip SSL tests when not available (thanks to Floris Bruynooghe)
* greenio: Remove deprecated GreenPipe.xreadlines() method, was broken anyway
A new RedNotebook version has been released.
You can get the tarball, Windows installer and links to distribution
packages at http://rednotebook.sourceforge.net/downloads.html
What is RedNotebook?
--------------------
RedNotebook is a **graphical journal** and diary helping you keep track
of notes and thoughts. It includes a calendar navigation, customizable
templates, export functionality and word clouds. You can also format,
tag and search your entries. RedNotebook is available in the
repositories of most common Linux distributions and a Windows installer
is available. It is written in Python and uses GTK+ for its interface.
What's new in this version?
---------------------------
* Add menu item for clearing the text format.
* Add toolbar menus "Insert" and "Format" to main menu for better accessibility and HUD integration.
* Only show keyboard shortcuts in main menu, not in toolbar menus.
* Use selected text as link name when a new link is inserted.
* When an image or file is inserted, use selected text as the name of the link.
* Format selected text as header when a header is inserted.
* Convert selected text to a list when a list is inserted.
* Select title after it has been inserted to allow for easy editing.
* Change file permissions so that journal files are only readable by the user.
* Windows: Restore slider positions after opening RedNotebook from the tray.
* Windows: Support non-ascii installation paths.
Cheers, Jendrik
On behalf of Twisted Matrix Laboratories, I am pleased to announce, in
extremis, the release of Twisted 12.3.
161 tickets are closed by this release, with the following highlights:
* Support for local parallel testing in trial
* A new "react" function to easily run a single asynchronous function
in a script with the reactor.
* Partial support for Python 3.3.
Note that only Python 2.7 is supported on Windows now. We also require
zope.interface 3.6.0 or newer.
For more information, see the NEWS file here:
http://twistedmatrix.com/Releases/Twisted/12.3/NEWS.txt
Download it now from:
http://pypi.python.org/packages/source/T/Twisted/Twisted-12.3.0.tar.bz2 or
http://pypi.python.org/packages/2.7/T/Twisted/Twisted-12.3.0.win32-py2.7.msi
Thanks to the supporters of Twisted via the Software Freedom Conservancy
and to the many contributors for this release.
--
Thomas
A new RedNotebook version has been released.
You can get the tarball, Windows installer and links to distribution
packages at http://rednotebook.sourceforge.net/downloads.html
What is RedNotebook?
--------------------
RedNotebook is a **graphical journal** and diary helping you keep track
of notes and thoughts. It includes a calendar navigation, customizable
templates, export functionality and word clouds. You can also format,
tag and search your entries. RedNotebook is available in the
repositories of most common Linux distributions and a Windows installer
is available. It is written in Python and uses GTK+ for its interface.
What's new in this version?
---------------------------
* Never include previous RedNotebook backups in new backups.
* Add strikethrough shortcut Ctrl+K.
* By default don't switch between edit and preview mode automatically.
* Add experimental support for irc protocol.
Cheers, Jendrik
Pigeon Computer 0.1 Initial (BETA) release
Summary
============
The Pigeon Computer is a simple but sophisticated system for learning
and exploring the fundamentals of computers and programming.
It is written to support a course or class (as yet pending) to learn
programming from the bit to the compiler.
There is a DRAFT manual and a Pigeon User Interface that includes:
* An assembler for the ATmega328P micro-controller.
* A polymorphic meta-compiler.
* Forth-like firmware in assembly.
* Simple high-level language for assembly control structures.
* A virtual computer that illustrates Functional Programming.
Source code is released under the GPL (v3) and is hosted on Github:
https://github.com/PhoenixBureau/PigeonComputer
The manual is online in HTML form here:
http://phoenixbureau.github.com/PigeonComputer/
Mailing list:
https://groups.google.com/d/forum/pigeoncomputer
It has been tested on Linux with Python 2.7, YMMV.
I'm releasing it now because it's basically done even though it needs
polish and I'm just too excited about it. Happy End of the World Day!
Details
============
The class starts with "the bit" and develops the core concepts
underlying computers with a hands-on exploration of bits and bytes as
embodied in physical "bits" on a table: coins or other binary
"tokens".
Using this "RAM-abacus" we explore different coding schemes (binary
numbers, ASCII codes, Grey codes, etc.) and then play with simple
operations to show how the bits can be used to perform math and logic
as well as simple "text processing". We number the operations, lay in
simple "programs" in the "RAM", and manually act out the actions of a
(hypothetical) CPU.
Once the students have the idea we introduce a concrete example: the
ATmega328P, a simple but powerful 8-bit RISC micro-controller with
Harvard Architecture and a 16-bit program RAM that is used in many
popular devices such as the Arduino Uno.
Using this chip and the Pigeon User Interface students will be able to
develop simple robots and other devices and program them themselves.
- - -
The Pigeon User Interface (PUI) is a simple and elegant IDE that
presents the user with a very simple but powerful stack-based virtual
computer that includes commands for assembling object code for the
ATmega328P and compiling high-level languages to assembly.
To get the students into assembly language the Pigeon Computer system
includes a tiny Forth-like firmware that implements a command
interpreter on the serial port (on-chip USART peripheral) in less than
a kilobyte of object code.
The firmware is a stub. It is meant to be understood and extended by
the students rather than used as-is. I have written some commands for
it that give it the ability to use the TWI (I2C) subsystem of the
ATmega328P to communicate with other devices, and used that to talk to
an Inertial Motion Unit and get gyro and accelerometer readings, so
there's that.
Once students are comfortable with assembly, the PUI includes a tiny,
powerful, and extremely flexible meta-compiler: Val Shorre's Meta-II
(implemented in Python.) This amazing bit of software is polymorphic
in the sense that you can feed it different compiler descriptions and
it becomes different compilers.
The underlying Meta-II virtual machine works just like an assembler to
read and "become" a compiler description, then it operates as a
syntax-driven compiler for the language described in the compiler
description.
It is simple enough to be understood by someone willing to take the
time, yet powerful enough to be used in earnest to develop "little
languages" for use in real projects. The PUI includes a simple
compiler (a description in Meta-II) that generates control-flow
constructs for the firmware commands, illustrating the path from
hand-coded assembly to high-level languages.
(Those interested in further information regarding these issues are
urged to examine the work of the Viewpoints Research Institute.)
- - -
Last but not least, the virtual computer in the PUI is a stack-based
Forth-like fully Functional Programming not-quite-language. It mimics
the operation of the firmware but goes far beyond what that code is
capable of as it has the whole of Python and the host machine to work
with.
When you start the PUI it creates a "roost" directory (I apologize for
the pun) where it writes a Git repository (using a pure-Python Git
implementation called Dulwich) and two files: 'log' and
'system.pickle'.
Then the GUI starts and the user sees a window with two panes. On the
left is a listbox that shows the contents of the stack and on the
right is a text editor.
The 'log' file is kept in sync with the contents of the text
(auto-saved two seconds after the last edit) and the 'system.pickle'
file keeps a copy of the serialized state of the PUI and is updated
after every change to the virtual computer's state. When either of
these files change a commit is made to the git repository.
This ensures that you never have to save (ever!) and you can never
lose your work (ever!). When you re-open the PUI it reads the last
state and log from the "roost" directory and loads them, seamlessly
putting you in the exact spot where you left off.
You can use standard Git tools to examine and check out previous
history. (Still to do: I want to add means for examining and
replaying histories as well as "cherry picking" objects and data from
previous states into the current one.)
In addition to the above automatic save mechanism, the text widget
includes undo/redo commands.
The stack-based virtual computer has a "dictionary" of command words
(like Forth) each of which operates solely on the stack and has no
side effects. The virtual computer uses only those Python types that
are immutable (string/unicode, numbers, tuples) and this together with
the purely Functional command words means that the entire virtual
machine is pure Functional-Programming-style.
(One effect of this is that the whole machine state forms one
"persistent" data structure that captures the whole previous history
of every computation the machine performs as the user uses it to e.g.
write code for their chip(s). This history is kept, serialized in the
'system.pickle' file, and could be made available to the user,
although at the moment it is discarded from the running PUI. This
whole persistence mechanism is separate and orthogonal to the
git-based history store mentioned above.)
- - -
The PUI has no menus, no buttons.
You execute commands by right-clicking on their names in the text editor.
Numbers can be put on the stack by right-clicking on them.
Strings can be put on the stack by selecting text and then, BEFORE
LETTING GO, clicking the right mouse button.
For example, start the PUI and type in two numbers. Right click on
each of the numbers and you'll see they appear on the stack. Right
click "add" (type it in if it's not there) and you will see that the
two numbers have been replaced by their sum.
This is a summary of the mouse "chords" that you can use to control
the PUI (inspired by the Oberon OS and UI):
PUI Mouse Click Chord Commands:
left - point and select
* followed by right: copy selection to stack
* followed by middle: cut selection to stack
middle - paste, scroll
* followed by left: paste stack to text
* followed by right: pop stack to text
right - command (execute word)
* followed by left or middle: lookup word (put the named
command onto the stack)
(Note: you use one mouse button and then, without letting go of the
first mouse button, use the second one to complete a mouse "chord".)
The default config.py includes key bindings as well:
Selection-to-Stack:
<F4>: Copy from selection to stack and system clipboard.
<Shift-F4> or <F6>: Cut selection to stack and system clipboard.
Stack-to-Insertion-Cursor:
<F5>: Paste from stack to cursor leave stack undisturbed.
<Shift-F5> or <F7>: Paste from stack to cursor and pop stack.
(You can edit these and add your own in the config file.)
The currently implemented command words are documented here:
http://phoenixbureau.github.com/PigeonComputer/user_interface.html#library-…
- - -
Fibonacci: Try putting 1 on the stack (type it in and right-click on
it) then right-click "dup" to duplicate it and have two ints on the
stack. Now repeatedly execute (right-click on) "tuck" and "add"...
Neat, eh?
And it works (thanks to Python's underlying implementation of "foo +
bar") whether you use string "1" numerals or integer digits.
- - -
Command words can be put onto the stack and combined into new commands
using three primitives: Sequence, Branch, Loop.
See http://phoenixbureau.github.com/PigeonComputer/user_interface.html#xerblin-…
for more information.
Once a new command has been made it can be included in other commands
or given a name and inscribed in the dictionary and used like the
other commands.
- - -
Whew! If you are still reading, thank you. There is a lot more to be
done and I am hoping to form classes in early January 2013. If you
are interested please email me at forman.simon(a)gmail.com
You can also participate on Github and join the mailing list.
* https://github.com/PhoenixBureau/PigeonComputer
* https://groups.google.com/d/forum/pigeoncomputer
Warm regards,
~Simon P. Forman
I'm proud to release version 1.4.21 of Roundup which has been possible
due to the help of several contributors. This release introduces some
minor features and, as usual, fixes some bugs:
Features:
- issue2550782: Added a new irker detector to send notifications on IRC
when an issue is created or messages are added. (Ezio Melotti)
- Beta version of responsive templates using devel schema
and Twitter Bootstrap for styling (Pradip Caulagi)
- pywin32 is not longer required to run on Windows (anatoly techtonik)
- Rewritten portalocker.py logic in ctypes for Windows (anatoly techtonik)
- Add an interface to register clearCache callbacks in roundupdb.
Sometimes complicated computations may require an application cache.
This application can now register a callback to clear the application
cache, because roundup knows better when to clear it (usually when a
transaction ends, either with rollback or with commit). The interface
for this is currently considered experimental. The current interface
is registerClearCacheCallback(self, method, param) where method is
called with param as the only parameter. (Ralf Schlatterbeck)
- Add a script to remove file-spam from a tracker, see
scripts/spam-remover. (Ralf Schlatterbeck)
Fixed:
- issue2550765: Don't show links in calendar that will fail.
Found and fixed by Cedric Krier. (Bernhard)
- issue2550765: use <meta name="robots" content="noindex, nofollow"> in the
_generic.calendar.html to prevent robots to follow all the links in the
calendar. (Ezio Melotti)
- "BaseException.with_traceback" is not available on Python 2, so use
"raise E, V, T" instead of "raise E(V).with_traceback(T)". This change was
originally introduced in 74476eaac38a. (Ezio Melotti)
- issue2550759: Trailing punctuation is no longer included when URLs are
converted to links. (Ezio Melotti)
- issue2550574: Restore sample detectors removed in roundup 1.4.9
(Thomas Arendsen Hein)
- Prevent AttributeError when removing all roles of a user
(Thomas Arendsen Hein)
- issue2550762 Minor Documentation fix in doc/developers.txt, thanks
to W. Trevor King. (Bernhard Reiter)
- issue2550766: Minor formatting issues in the docs for date properties,
thanks John Kristensen. (Bernhard Reiter)
- issue2550738: Fixes for various documentation typoes,
thanks Nathan Russell. (John Kristensen)
- issue2550756: Fix `oder' typo in mailer.Mailer.bounce_message docstring,
thanks W. Trevor King (John Kristensen)
- Fix basic authentication: instatiating the login action would fail if
the user is not set. We now first set the user to anonymous and then
try basic authentication if enabled. (Ralf Schlatterbeck)
- Fix xmlrpc permissions for lookup method: Allow if the key attribute
is either searchable or viewable, don't check id attribute (Ralf
Schlatterbeck)
- Fix installation documentation (section Prerequisites) to require at
least python 2.5, thanks to John P. Rouillard for discovering this.
(committed by Ralf Schlatterbeck)
- Fix version_check.py to require at least python 2.5 (anatoly techtonik)
- Fixing the download button re-activating the cheeseshop plugin in the
sphinx config. Thanks to Richard for the hint. (Bernhard Reiter)
- issue2550783 devel template's schema.py permissions referenced the
organization property for the user, but the property is called
organisation. Thanks to Pradip Caulagi. (committed by John Rouillard)
- issue2550749 - the xmlrpc interface is invoked on content type
and not url path. Sending any text/xml data to roundup results in
invoking the xml-rpc interface, but a REST or other interface could
also consume xml data and do something different. So require the use
of 'http(s)://.../xmlrpc' uri to trigger the xmlrpc interface.
(John Rouillard)
- issue2550774: Remove generating documentation with rst2html, and update the
README.txt with how to create the html docs using sphinx, thanks Kai Storbeck
(John Kristensen)
- issue2550774: Include doc/conf.py in the release tarball, so people can build
their own documentation in html, thanks Kai Storbeck (John Kristensen)
- issue2550774: Update website/www/Makefile to symlink COPYING.txt so "make"
works again, thanks Kai Storbeck (John Kristensen)
- issue2550760: Several improvements to the manpages
thanks Kai Storbeck & Bastian Kleineidam (John Kristensen)
If you're upgrading from an older version of Roundup you *must* follow
the "Software Upgrade" guidelines given in the maintenance documentation.
Roundup requires python 2.5 or later (but not 3+) for correct operation.
To give Roundup a try, just download (see below), unpack and run::
python demo.py
Release info and download page:
http://pypi.python.org/pypi/roundup
Source and documentation is available at the website:
http://roundup-tracker.org/
Mailing lists - the place to ask questions:
http://sourceforge.net/mail/?group_id=31577
About Roundup
=============
Roundup is a simple-to-use and -install issue-tracking system with
command-line, web and e-mail interfaces. It is based on the winning design
from Ka-Ping Yee in the Software Carpentry "Track" design competition.
Note: Ping is not responsible for this project. The contact for this
project is richard(a)users.sourceforge.net.
Roundup manages a number of issues (with flexible properties such as
"description", "priority", and so on) and provides the ability to:
(a) submit new issues,
(b) find and edit existing issues, and
(c) discuss issues with other participants.
The system will facilitate communication among the participants by managing
discussions and notifying interested parties when issues are edited. One of
the major design goals for Roundup that it be simple to get going. Roundup
is therefore usable "out of the box" with any python 2.5+ (but not 3+)
installation. It doesn't even need to be "installed" to be operational,
though an install script is provided.
It comes with two issue tracker templates (a classic bug/feature tracker and
a minimal skeleton) and four database back-ends (anydbm, sqlite, mysql
and postgresql).
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting www: http://www.runtux.com
Reichergasse 131, A-3411 Weidling email: office(a)runtux.com
osAlliance member email: rsc(a)osalliance.com
*** Attention Cygwin Python module package maintainers ***
*** Cygwin is migrating from Python 2.6 to 2.7... ***
New News:
=== ====
I have released Cygwin Python 2.7.3-1 as experimental. The tarballs
should be available on a Cygwin mirror near you shortly.
The main purpose of this release is to begin the transition to make
Python 2.7 the official Cygwin version. If you are one of the Cygwin
Python module package maintainers, then please take this opportunity to
build, test, and change (if necessary) your package to support Python
2.7.
Note the following:
1. 2.7.3-1 is experimental and 2.6.8-2 remains current. I will update
Cygwin to make 2.7.3-1 (or later) current on or about February 1, 2013.
2. You need to select the "Exp" radio button when running Cygwin's
setup.exe to install 2.7.3-1.
3. If you install 2.7.3-1, then 2.6 modules will no longer work.
Old News:
=== ====
Python is an interpreted, interactive, object-oriented programming
language. If interested, see the Python web site for more details:
http://www.python.org/
Please read the README file:
/usr/share/doc/Cygwin/python.README
since it covers requirements, installation, known issues, etc.
Standard News:
======== ====
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This downloads setup.exe to your
system. Then, run setup and answer all of the questions.
If you have questions or comments, please send them to the Cygwin
mailing list.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:
http://cygwin.com/lists.html#subscribe-unsubscribe
If you need more information on unsubscribing, start reading here:
http://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
Jason
Hi all,
I'm pleased to announce that WinPython v2.7.3.2 has been released for
32-bit and 64-bit Windows platforms:
http://code.google.com/p/winpython/
This is mainly a maintenance release (many packages have been updated
since v2.7.3.1).
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.x in the near future) 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).
Enjoy!
-Pierre
