Announcing argparse 0.2
argparse single module download:
argparse bundled downloads at PyPI:
About this release
This release fixes a few minor bugs, modifies the 'store_true' and
'store_false' actions to have more natural defaults, and adds an
epilog= keyword argument to ArgumentParser for text to be printed
after the help messages. (The latter is in line with the `updates to
optparse`_ for Python 2.5.)
.. _updates to optparse: http://www.python.org/doc/2.5/whatsnew/modules.html
New in this release
* The 'store_true' action's default is now False (instead of None).
* The 'store_false' action's default is now True (instead of None).
* ArgumentParser objects now accept an epilog= keyword argument.
The argparse module is an optparse-inspired command line parser that
improves on optparse by:
* handling both optional and positional arguments
* supporting parsers that dispatch to sub-parsers
* producing more informative usage messages
* supporting actions that consume any number of command-line args
* allowing types and actions to be specified with simple callables
instead of hacking class attributes like STORE_ACTIONS or
as well as including a number of other more minor improvements on the
optparse API. To whet your appetite, here's a simple program that sums
its command-line arguments and writes them to a file::
parser = argparse.ArgumentParser()
parser.add_argument('integers', type=int, nargs='+')
parser.add_argument('--log', type='outfile', default=sys.stdout)
args = parser.parse_args()
args.log.write('%s\n' % sum(args.integers))
A prize of $500 prize is hereby offered to the person or persons who can
create the best slide shows (using Leo's slideshow plugin) that introduces
Leo to newbies. What is Leo, you ask?
1. Prize fund
The total prize fund is $500. Prizes will be awarded solely at the
discretion of Edward K. Ream. The prize fund may be split among
contestants, and the total prize fund will be distributed only if the number
and quality of submissions warrant it.
2. Format of entries
Entries should be a *single* Leo outline. This outline may contain multiple
slideshows. Multiple entries are allowed. Entries must be accompanied by
your name, address and email address.
3. Ownership of entries
All entries become the property of Edward K. Ream and will be distributed
under the terms of Leo's Open Source license.
4. Criteria for awards
Prizes will be awarded on how useful the slideshow is in helping newbies
understand Leo. To be considered for an award, an entry must show
substantial work. I'll also consider creativity, originality, etc. I'll
also look favorably on extensions to the slideshow plugin if such extensions
materially improve the presentation.
5. Duration of contest
The contest shall end December 11, 2006. The contest may be extended at the
sole discretion of Edward K. Ream, but in no event shall the contest
continue past February 2, 2007.
Prizes will be awarded within one week of the close of the contest. Winners
will be announced on Leo's Open Discussion Forum:
Edward K. Ream email: edreamleo(a)charter.net
The 126.96.36.199 release of wxPython is now available for download at
http://wxpython.org/download.php. This release is a quick-turnaround
bugfix release designed to solve some problems found in the 188.8.131.52
release. Source and binaries are available for both Python 2.4 and 2.5
for Windows and Mac, as well some pacakges for varous Linux
distributions. A summary of changes is listed below and also at
What is wxPython?
wxPython is a GUI toolkit for the Python programming language. It
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module that wraps the GUI components
of the popular wxWidgets cross platform library, which is written in
wxPython is a cross-platform toolkit. This means that the same program
will usually run on multiple platforms without modifications.
Currently supported platforms are 32-bit Microsoft Windows, most Linux
or other Unix-like systems using GTK2, and Mac OS X 10.3+, in most
cases the native widgets are used on each platform.
Changes in 184.108.40.206
Fixed a bug in the MaskedEdit controls caused by conflicting IsEmpty
Patch #1579280: Some mimetype optimizations on unix-like systems.
wxMac: Several wx.webkit.WebKitCtrl enhancements/fixes, including:
- new methods for increasing/decreasing text size, getting
selection, getting/setting scroll position, printing, enabling
- added new event (wx.webkit.WebKitBeforeLoadEvent) for catching, and
possibly vetoing, load events before they occur.
- wx.webkit.WebKitCtrl now fires mouse events for certain events
that it was eating before. This improves wxSplitterWindow
- refactoring of the sizing logic to move the Cocoa view. Tested
with splitter windows, panels, notebooks and all position
correctly with this.
Some improvements to the drawing code in CustomTreeCtrl.
Fixed refcount leak in wx.Window.GetChildren.
http://wxPython.org Java give you jitters? Relax with wxPython!
I am happy to announce the release of Paste 1.0. This release
includes all the major components: Paste (core), Paste Script, Paste
Deploy, and Paste WebKit.
Paste actually passed the 0.x stage a long time ago. But now it's
official: Paste is really stable. How stable? A lot stable.
What Is Paste?
Install: easy_install Paste PasteScript PasteDeploy
Paste (core) is a set of WSGI components, each of which can be used in
isolation. But used together they form an unstoppable force. Team
These components let you do things like create applications that proxy
to other websites, mount multiple applications under different
prefixes, catch exceptions and interactively inspect the environment,
and much more.
Paste Deploy is a configuration system for these components. Paste
Script is a jack of all trades that builds new project file layouts,
runs WSGI server stacks, and does application deployment.
Thanks to all the people that have helped Paste get this far: Ben
Bangert, Clark Evans, James Gardner, Philip Jenvy, and to Imaginary
Landscape for their support during my time there, and to The Open
Planning Project for their ongoing support.
Ian Bicking | ianb(a)colorstudy.com | http://blog.ianbicking.org
There is now an experimental version of **Movable IDLE** available,
this is an off-shoot of the `Movable Python
**Movable IDLE**, version 0.1.0 can be downloaded (free) from :
`Movable IDLE Download
(Same place as the trial version of Movable Python.)
**Movable IDLE** is a portable distribution of IDLE, the Python IDE,
The homepage of Movable IDLE is :
This can be run without installing, and at only fifteen megabytes
uncompressed it can be run from a USB stick or memory card.
It comes with the full Python standard library, and should be capable
of running almost any program that can be run with IDLE. Hopefully this
will be useful for educational and experimental purposes.
**Movable IDLE** does not have all the clever trickery that **Movable
Python** does. This means that the `win32
<http://sourceforge.net/projects/pywin32>`_ extensions, or any program
that uses ``imp.find_module`` are unlikely to work. It also won't work
with programs that have another event loop, like other GUI toolkits.
If you need these features, try `Movable Python`_.
On the other hand, if you do find bugs or restrictions, post them to
the `Movable Python Mailing List
<http://groups.google.com/group/movpy>`_ and it may be possible to fix
them. This is the right place to post feedback and suggestions as well.
**Movable IDLE** is copyright *Michael Foord*, 2006. It is free, but
not Open Source.
You are free to copy and distribute **Movable IDLE**, but not to charge
for it. It may not be included in any distribution which charges
directly or indirectly, without express permission.
The following sections of the `Movable Python License
<http://www.voidspace.org.uk/python/movpy/license.html>`_ also apply :
* *Restricted Uses*
Ian Ozsvald (joint founder of ShowMeDo.com) introduces all the usual
Python on-line resources that a new Python programmer should know
about. The videos cover the main Python sites, news, books, blogs,
community and some of the major projects:
Here I give a 30 minute tour of all the main Python resources that a
programmer should know about. This is the kind of introduction I'd
give to any new Python programmer when they ask me 'what's out there?'.
Resources covered include the main Python site, Tutorials, Cheeseshop,
ShowMeDo's Python videos, the Cookbook, DiveIntoPython, Daily Python,
several new-programmer blogs, comp.lang.python, books (Beginning
Python, Python in a Nutshell, Dive Into Python, Cookbook) and
five of the larger Python projects.
Free videos (we call them ShowMeDos) showing you how to do things.
The videos are made by us and our users, for everyone. 38 videos
for Python, 71 in total, and the collection is growing.
We'd love to have more contributions - would you share what you know?
Ian Ozsvald, Kyran Dale
csounds routines beta 7 is out. I would like to mention this might be
a good project for people just starting out because all you are doing
is messing with text files to set things up to do amazing things and
without the dreaded re module (so far).
Dex Tracker will not be updated until I save the .sco editor saving
get_instr(from_file, to_file, instr_num)
from_file is the .csd file that you are reading to to file is where you
wish the shortened orc file saved. Currently the plan is to save then
as svc files. instr_num is the instrument number that is to be ripped.
The purpose is part of an overall system but it can be used to rip orc
files from other csd files. There will be parts of instruments that
are not captured in some or maybe alot of .csd files. If there is
donated code to adress that it will be given a different name most
from_file is the file that is to be read from. This will return two
lists instr_number that is a list of numbers currently in the csd file
and comments wich is any comment that is included on the instr line
following the instr number
from_file is the shortened orc file to be read from. To file is the
full orc file to be written to. The routine reads a shortened orc
format and writes a header part to create a
full orc file.
get_score(from_file, to_file, instr_num)
from_file the file to get the score from. to_file is the file it is to
be saved to. instr_num the instrument number that is to be ripped from
the csd file. Del_Instr(from_file, instr) for instr will pick up i1
and i10 in test splitline is probily helpfull
Loads a file (We want it for .orc files but the editor doesn't care
what it is) and places the lines into a grid. The header string is a
string that is defined by the user that for the purposes of editing
.sco files should be placed at the end of the list of words to be used
as a header for the collums.
This brings up a .sco file picker and passes the file picked to
This gives a list of all the pins that are defined with zar and zawm.
It will return instr number, intrument input and instrument output
At the beginning of the month the PSF Infrastructure committee announced
that we had reached the decision that JIRA was our recommendation for the
next issue tracker for Python development. Realizing, though, that it was a
tough call between JIRA and Roundup we said that we would be willing to
switch our recommendation to Roundup if enough volunteers stepped forward to
help administer the tracker, thus negating Atlassian's offer of free managed
Well, the community stepped up to the challenge and we got plenty of
volunteers! In fact, the call for volunteers has led to an offer for
professional hosting for Roundup from Upfront Systems. The committee is
currently evaluating that offer and will hopefully have a decision made
soon. Once a decision has been made we will contact the volunteers as to
whom we have selected to help administer the installation (regardless of who
hosts the tracker). The administrators and python-dev can then begin
working towards deciding what we want from the tracker and its
Once again, thanks to the volunteers for stepping forward to make this
PSF Infrastructure committee chairman