Mailman 3 October 2009 - Python-announce-list

The Python: Rag November issue available
by Bernie Oct. 31, 2009

Oct. 31, 2009

The November issue of The Python: Rag is available at: http://www.pythonrag.org A monthly, free, community run, Python magazine - issues are in pdf format, intended for anyone interested in Python.

1 0

ANN: python-ldap-2.3.10
by Michael Ströder Oct. 31, 2009

Oct. 31, 2009

Find a new release of python-ldap: http://www.python-ldap.org/ python-ldap provides an object-oriented API to access LDAP directory servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for that purpose. Additionally it contains modules for other LDAP-related stuff (e.g. processing LDIF, LDAPURLs and LDAPv3 schema). Ciao, Michael. -- Michael Ströder E-Mail: michael(a)stroeder.com http://www.stroeder.com

1 0

CodeInvestigator 0.18.0
by hans moleman Oct. 29, 2009

Oct. 29, 2009

CodeInvestigator 0.18.0 was released on October 29. It mainly deals with bug fixes: - Simple statements all on the one line separated by a semicolon. - Generators and yield. It has one enhancement: - An Entry Point filter was added. It allows you the leave out the entry points you're not interested in. You need Python 2.6 and Firefox for CodeInvestigator. CodeInvestigator is a tracing tool for Python programs. Running a program through CodeInvestigator creates a recording. Program flow, function calls, variable values and conditions are all stored for every line the program executes. The recording is then viewed with an interface consisting of the code. The code can be clicked: A clicked variable displays its value, a clicked loop displays its iterations. You read code, and have at your disposal all the run time details of that code. A computerized desk check tool and another way to learn about your program. http://sourceforge.net/project/showfiles.php?group_id=183942

1 0

Bazaar 2.0.1 and 2.1.0b1 released
by John Arbash Meinel Oct. 28, 2009

Oct. 28, 2009

Our first post-2.0 releases of Bazaar have finally become official. Now that we are at 2.0, we decided to split a stable releases series and a development series. As such, 2.0.1 has only bugfixes relative to the 2.0 release, while new features and potential compatibility changes are contained only within 2.1.0b1. All of the changes in 2.0.1 are available in 2.1.0b1. Thanks to everyone who has helped polish the 2.0.1 release, and ensure that our next 2.1 stable release will have lots of interesting changes to come. To get your own copy, please visit http://bazaar-vcs.org/Download. Packages for many popular platforms are available. The short summaries of changes are: bzr 2.0.1 ######### :Codename: Stability First :2.0.1: 2009-10-14 The first of our new ongoing bugfix-only stable releases has arrived. It includes a collection of 12 bugfixes applied to bzr 2.0.0, but does not include any of the feature development in the 2.1.0 series. bzr 2.1.0b1 ########### :Codename: While the cat is away :2.1.0b1: 2009-10-14 This is the first development release in the new split "stable" and "development" series. As such, the release is a snapshot of bzr.dev without creating a release candidate first. This release includes a fair amount of internal changes, with deprecated code being removed, and several new feature developments. People looking for a stable code base with only bugfixes should focus on the 2.0.1 release. All bugfixes present in 2.0.1 are present in 2.1.0b1. Highlights include support for ``bzr+ssh://host/~/homedir`` style urls, finer control over the plugin search path via extended BZR_PLUGIN_PATH syntax, visible warnings when extension modules fail to load, and improved error handling during unlocking. John =:-> This is the full NEWS entry about all bugs/features fixed and released relative to 2.0.0: bzr 2.1.0b1 ########### :Codename: While the cat is away :2.1.0b1: 2009-10-14 This is the first development release in the new split "stable" and "development" series. As such, the release is a snapshot of bzr.dev without creating a release candidate first. This release includes a fair amount of internal changes, with deprecated code being removed, and several new feature developments. People looking for a stable code base with only bugfixes should focus on the 2.0.1 release. All bugfixes present in 2.0.1 are present in 2.1.0b1. Highlights include support for ``bzr+ssh://host/~/homedir`` style urls, finer control over the plugin search path via extended BZR_PLUGIN_PATH syntax, visible warnings when extension modules fail to load, and improved error handling during unlocking. New Features ************ * Bazaar can now send mail through Apple OS X Mail.app. (Brian de Alwis) * ``bzr+ssh`` and ``bzr`` paths can now be relative to home directories specified in the URL. Paths starting with a path segment of ``~`` are relative to the home directory of the user running the server, and paths starting with ``~user`` are relative to the home directory of the named user. For example, for a user "bob" with a home directory of ``/home/bob``, these URLs are all equivalent: * ``bzr+ssh://bob@host/~/repo`` * ``bzr+ssh://bob@host/~bob/repo`` * ``bzr+ssh://bob@host/home/bob/repo`` If ``bzr serve`` was invoked with a ``--directory`` argument, then no home directories outside that directory will be accessible via this method. This is a feature of ``bzr serve``, so pre-2.1 clients will automatically benefit from this feature when ``bzr`` on the server is upgraded. (Andrew Bennetts, #109143) * Extensions can now be compiled if either Cython or Pyrex is available. Currently Pyrex is preferred, but that may change in the future. (Arkanes) * Give more control on BZR_PLUGIN_PATH by providing a way to refer to or disable the user, site and core plugin directories. (Vincent Ladeuil, #412930, #316192, #145612) Bug Fixes ********* * Bazaar's native protocol code now correctly handles EINTR, which most noticeably occurs if you break in to the debugger while connected to a bzr+ssh server. You can now can continue from the debugger (by typing 'c') and the process continues. However, note that pressing C-\ in the shell may still kill the SSH process, which is bug 162509, so you must sent a signal to the bzr process specifically, for example by typing ``kill -QUIT PID`` in another shell. (Martin Pool, #341535) * ``bzr add`` in a tree that has files with ``\r`` or ``\n`` in the filename will issue a warning and skip over those files. (Robert Collins, #3918) * ``bzr dpush`` now aborts if uncommitted changes (including pending merges) are present in the working tree. The configuration option ``dpush_strict`` can be used to set the default for this behavior. (Vincent Ladeuil, #438158) * ``bzr merge`` and ``bzr remove-tree`` now requires --force if pending merges are present in the working tree. (Vincent Ladeuil, #426344) * Clearer message when Bazaar runs out of memory, instead of a ``MemoryError`` traceback. (Martin Pool, #109115) * Don't give a warning on Windows when failing to import ``_readdir_pyx`` as it is never built. (John Arbash Meinel, #430645) * Don't restrict the command name used to run the test suite. (Vincent Ladeuil, #419950) * ftp transports were built differently when the kerberos python module was present leading to obscure failures related to ASCII/BINARY modes. (Vincent Ladeuil, #443041) * Network streams now decode adjacent records of the same type into a single stream, reducing layering churn. (Robert Collins) * PreviewTree behaves correctly when get_file_mtime is invoked on an unmodified file. (Aaron Bentley, #251532) * Registry objects should not use iteritems() when asked to use items(). (Vincent Ladeuil, #430510) * Weave based repositories couldn't be cloned when committers were using domains or user ids embedding '.sig'. Now they can. (Matthew Fuller, Vincent Ladeuil, #430868) Improvements ************ * Bazaar gives a warning before exiting, and writes into ``.bzr.log``, if compiled extensions can't be loaded. This typically indicates a packaging or installation problem. In this case Bazaar will keep running using pure-Python versions, but this may be substantially slower. The warning can be disabled by setting ``ignore_missing_extensions = True`` in ``bazaar.conf``. See also <https://answers.launchpad.net/bzr/+faq/703>. (Martin Pool, #406113, #430529) * Secondary errors that occur during Branch.unlock and Repository.unlock no longer obscure the original error. These methods now use a new decorator, ``only_raises``. This fixes many causes of ``TooManyConcurrentRequests`` and similar errors. (Andrew Bennetts, #429747) Documentation ************* * Describe the new shell-like test feature. (Vincent Ladeuil) * Help on hooks no longer says 'Not deprecated' for hooks that are currently supported. (Ian Clatworthy, #422415) API Changes *********** * ``bzrlib.user_encoding`` has been removed; use ``bzrlib.osutils.get_user_encoding`` instead. (Martin Pool) * ``bzrlib.tests`` now uses ``stopTestRun`` for its ``TestResult`` subclasses - the same as python's unittest module. (Robert Collins) * ``diff._get_trees_to_diff`` has been renamed to ``diff.get_trees_and_branches_to_diff``. It is now a public API, and it returns the old and new branches. (Gary van der Merwe) * ``bzrlib.trace.log_error``, ``error`` and ``info`` have been deprecated. (Martin Pool) * ``MutableTree.has_changes()`` does not require a tree parameter anymore. It now defaults to comparing to the basis tree. It now checks for pending merges too. ``Merger.check_basis`` has been deprecated and replaced by the corresponding has_changes() calls. ``Merge.compare_basis``, ``Merger.file_revisions`` and ``Merger.ensure_revision_trees`` have also been deprecated. (Vincent Ladeuil, #440631) * ``ProgressTask.note`` is deprecated. (Martin Pool) Internals ********* * Added ``-Drelock`` debug flag. It will ``note`` a message every time a repository or branch object is unlocked then relocked the same way. (Andrew Bennetts) * ``BTreeLeafParser.extract_key`` has been tweaked slightly to reduce mallocs while parsing the index (approx 3=>1 mallocs per key read). This results in a 10% speedup while reading an index. (John Arbash Meinel) * The ``bzrlib.lsprof`` module has a new class ``BzrProfiler`` which makes profiling in some situations like callbacks and generators easier. (Robert Collins) Testing ******* * Passing ``--lsprof-tests -v`` to bzr selftest will cause lsprof output to be output for every test. Note that this is very verbose! (Robert Collins) * Setting ``BZR_TEST_PDB=1`` when running selftest will cause a pdb post_mortem to be triggered when a test failure occurs. (Robert Collins) * Shell-like tests can now be written. Code in ``bzrlib/tests/script.py`` , documentation in ``developers/testing.txt`` for details. (Vincent Ladeuil) * Some tests could end up with the same id, that was dormant for a long time. (Vincent Ladeuil, #442980) * Stop showing the number of tests due to missing features in the test progress bar. (Martin Pool) * Test parameterisation now does a shallow copy, not a deep copy of the test to be parameterised. This is not expected to break external use of test parameterisation, and is substantially faster. (Robert Collins) * Tests that try to open a bzr dir on an arbitrary transport will now fail unless they have explicitly permitted the transport via ``self.permit_url``. The standard test factories such as ``self.get_url`` will permit the urls they provide automatically, so only exceptional tests should need to do this. (Robert Collins) * The break-in test no longer cares about clean shutdown of the child, instead it is happy if the debugger starts up. (Robert Collins) * The full test suite is expected to pass when the C extensions are not present. (Vincent Ladeuil, #430749) bzr 2.0.1 ######### :Codename: Stability First :2.0.1: 2009-10-14 The first of our new ongoing bugfix-only stable releases has arrived. It includes a collection of 12 bugfixes applied to bzr 2.0.0, but does not include any of the feature development in the 2.1.0 series. Bug Fixes ********* * ``bzr add`` in a tree that has files with ``\r`` or ``\n`` in the filename will issue a warning and skip over those files. (Robert Collins, #3918) * bzr will attempt to authenticate with SSH servers that support ``keyboard-interactive`` auth but not ``password`` auth when using Paramiko. (Andrew Bennetts, #433846) * Fixed fetches from a stacked branch on a smart server that were failing with some combinations of remote and local formats. This was causing "unknown object type identifier 60" errors. (Andrew Bennetts, #427736) * Fixed ``ObjectNotLocked`` errors when doing some log and diff operations on branches via a smart server. (Andrew Bennetts, #389413) * Handle things like ``bzr add foo`` and ``bzr rm foo`` when the tree is at the root of a drive. ``osutils._cicp_canonical_relpath`` always assumed that ``abspath()`` returned a path that did not have a trailing ``/``, but that is not true when working at the root of the filesystem. (John Arbash Meinel, Jason Spashett, #322807) * Hide deprecation warnings for 'final' releases for python2.6. (John Arbash Meinel, #440062) * Improve the time for ``bzr log DIR`` for 2a format repositories. We had been using the same code path as for <2a formats, which required iterating over all objects in all revisions. (John Arbash Meinel, #374730) * Make sure that we unlock the tree if we fail to create a TreeTransform object when doing a merge, and there is limbo, or pending-deletions directory. (Gary van der Merwe, #427773) * Occasional IndexError on renamed files have been fixed. Operations that set a full inventory in the working tree will now go via the apply_inventory_delta code path which is simpler and easier to understand than dirstates set_state_from_inventory method. This may have a small performance impact on operations built on _write_inventory, but such operations are already doing full tree scans, so no radical performance change should be observed. (Robert Collins, #403322) * Retrieving file text or mtime from a _PreviewTree has good performance when there are many changes. (Aaron Bentley) * The CHK index pages now use an unlimited cache size. With a limited cache and a large project, the random access of chk pages could cause us to download the entire cix file many times. (John Arbash Meinel, #402623) * When a file kind becomes unversionable after being added, a sensible error will be shown instead of a traceback. (Robert Collins, #438569) Documentation ************* * Improved README. (Ian Clatworthy) * Improved upgrade documentation for Launchpad branches. (Barry Warsaw)

1 0

Wing IDE 3.2.2 released
by Wingware Oct. 28, 2009

Oct. 28, 2009

Hi, Wingware has released version 3.2.2 of Wing IDE, our integrated development environment for the Python programming language. This bug fix release includes the following: * Added Toggle Bookmark for unnamed bookmarks, visual indicator of bookmarks, and bookmark traversal menu in editor * Improved syntax highlighting for Mako templates (*.mako) * Show number of replacements for Replace All operations * Several performance improvements for large projects and for editor responsiveness * Added toolbar to OS Commands tool and option to auto-save before executing a command * Fix for hanging up the editor on certain Python files * Several other bug fixes and minor features. See the change log for details: http://wingware.com/pub/wingide/3.2.2/CHANGELOG.txt *Wing 3.2 Highlights* Version 3.2 of Wing IDE includes the following new features not present in Wing IDE 3.1: * Support for Python 3.0 and 3.1 * Rewritten version control integration with support for Subversion, CVS, Bazaar, git, Mercurial, and Perforce (*) * Added 64-bit Debian, RPM, and tar file installers for Linux * File management in Project view (**) * Auto-completion in the editor obtains completion data from live runtime when the debugger is active (**) * Perspectives: Create and save named GUI layouts and optionally automatically transition when debugging is started (*) * Improved support for Cython and Pyrex (*.pyx files) * Added key binding documentation to the manual * Added Restart Debugging item in Debug menu and tool bar (**) * Improved OS Commands and Bookmarks tools (*) (*)'d items are available in Wing IDE Professional only. (**)'d items are available in Wing IDE Personal and Professional only. The release also contains many other minor features and bug fixes; see the change log for details: http://wingware.com/pub/wingide/3.2.2/CHANGELOG.txt *Downloads* Wing IDE Professional and Wing IDE Personal are commercial software and require a license to run. A free trial license can be obtained directly from the product when launched. Wing IDE 101 can be used free of charge. Wing IDE Pro 3.2.2 http://wingware.com/downloads/wingide/3.2 Wing IDE Personal 3.2.2 http://wingware.com/downloads/wingide-personal/3.2 Wing IDE 101 3.2.2 http://wingware.com/downloads/wingide-101/3.2 *About Wing IDE* Wing IDE is an integrated development environment for the Python programming language. It provides powerful debugging, editing, code intelligence, testing, version control, and search capabilities that reduce development and debugging time, cut down on coding errors, and make it easier to understand and navigate Python code. Wing IDE is available in three product levels: Wing IDE Professional is the full-featured Python IDE, Wing IDE Personal offers a reduced feature set at a low price, and Wing IDE 101 is a free simplified version designed for teaching entry level programming courses with Python. System requirements are Windows 2000 or later, OS X 10.3.9 or later for PPC or Intel (requires X11 Server), or a recent Linux system (either 32 or 64 bit). Wing IDE 3.2 supports Python versions 2.0.x through 3.1.x. *Purchasing and Upgrading* Wing 3.2 is a free upgrade for all Wing IDE 3.0 and 3.1 users. Any 2.x license sold after May 2nd 2006 is free to upgrade; others cost 1/2 the normal price to upgrade. Upgrade a 2.x license: https://wingware.com/store/upgrade Purchase a 3.x license: https://wingware.com/store/purchase -- The Wingware Team Wingware | Python IDE Advancing Software Development www.wingware.com

1 0

ffnet-0.6.2 released
by Marek Wojciechowski Oct. 28, 2009

Oct. 28, 2009

ffnet version 0.6.2 is released and is available for download at: http://ffnet.sourceforge.net This release contains minor enhancements and compatibility improvements: - ffnet works now with >=networkx-0.99; - neural network can be called now with 2D array of inputs, it also returns numpy array instead of python list; - readdata function is now alias to numpy.loadtxt; - docstrings are improved. What is ffnet? -------------- ffnet is a fast and easy-to-use feed-forward neural network training solution for python. Unique features --------------- 1. Any network connectivity without cycles is allowed. 2. Training can be performed with use of several optimization schemes including: standard backpropagation with momentum, rprop, conjugate gradient, bfgs, tnc, genetic alorithm based optimization. 3. There is access to exact partial derivatives of network outputs vs. its inputs. 4. Automatic normalization of data. Basic assumptions and limitations: ---------------------------------- 1. Network has feed-forward architecture. 2. Input units have identity activation function, all other units have sigmoid activation function. 3. Provided data are automatically normalized, both input and output, with a linear mapping to the range (0.15, 0.85). Each input and output is treated separately (i.e. linear map is unique for each input and output). 4. Function minimized during training is a sum of squared errors of each output for each training pattern. Performance ----------- Excellent computational performance is achieved implementing core functions in fortran 77 and wrapping them with f2py. ffnet outstands in performance pure python training packages and is competitive to 'compiled language' software. Moreover, a trained network can be exported to fortran sources, compiled and called in many programming languages. Usage ----- Basic usage of the package is outlined below: >>> from ffnet import ffnet, mlgraph, savenet, loadnet, exportnet >>> conec = mlgraph( (2,2,1) ) >>> net = ffnet(conec) >>> input = [ [0.,0.], [0.,1.], [1.,0.], [1.,1.] ] >>> target = [ [1.], [0.], [0.], [1.] ] >>> net.train_tnc(input, target, maxfun = 1000) >>> net.test(input, target, iprint = 2) >>> savenet(net, "xor.net") >>> exportnet(net, "xor.f") >>> net = loadnet("xor.net") >>> answer = net( [ 0., 0. ] ) >>> partial_derivatives = net.derivative( [ 0., 0. ] ) Usage examples with full description can be found in examples directory of the source distribution or browsed at http://ffnet.sourceforge.net. -- Marek Wojciechowski

1 0

New mds-utils release (1.2.0)
by Michele De Stefano Oct. 27, 2009

Oct. 27, 2009

mds-utils 1.2.0 have been released. Release Notes: - Improved python/fileobj.hpp: now there are 3 helper file objects and they are copy-constructible. Derivation from boost::python::object has been mantained. - Added utilities for indexing support in Python extensions. - Added boost::python converters for some boost::numeric::ublas classes. ------------------- What is mds-utils ? ------------------- mds-utils is a library intended to become a collection of several C++ utilities. It makes heavy usage of the Boost C++ libraries. Release 1.2.0 contains: - a tool for detecting machine endianity. - some useful classes that allow to treat the old C FILE pointer as a C++ stream. - C++ classes that help on treating Python file objects as C++ streams. - simple utilities for indexing support in Python extensions. - new C++ to-Python and from-Python converters for some Boost uBlas objects. Project home: http://code.google.com/p/mds-utils/ -- Michele De Stefano http://www.linkedin.com/in/micdestefano http://xoomer.virgilio.it/michele_de_stefano

1 0

[ANN]: IronPython 2.6 Release Candidate 2
by Dave Fugate Oct. 27, 2009

Oct. 27, 2009

Hello Python Community, We're pleased to announce the release of IronPython 2.6 Release Candidate 2 which can be freely downloaded at http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34451. Since the public availability of Release Candidate 1, we've addressed the following: * The "json" CPython package has been included with our MSI installer * CPython's logging module can be utilized without passing the -X:Frames command-line parameter to ipy.exe * Documentation distributed with the release has been updated * A memory leak in the hosting APIs reported on the mailing list was fixed * Multi-threaded debugging using sys.settrace show now work * Fixed mapping of .NET "Compare" methods to __cmp__ when they return the wrong type * The imp.load_module function now respects the file argument * A bug related to relative module imports has been addressed * Fixed indexing on .NET types defining DefaultMemberAttribute * Several issues involving new-style string formatting have been corrected If no major issues with this release candidate are discovered, we hope to ship the final 2.6 release in a little under a month. Anyone planning on upgrading to 2.6 should try out this release candidate and let us know of any issues you find ASAP. Thanks to everyone in the IronPython Community who reported bugs and provided valuable feedback: Zachc, yamakox, vernondcole, VAks, tscottw, tonyandrewmeyer, tomwright, TomasMatousek, tkamiya, timers, srivatsn, sopeajw, saveenr, sanxiyn, rridge, ronniemaor, quirogaco, pythonfoo, py_sunil, pm100, pl6306, paulfelix, orestis, olegt, oldman, NDHUMuscle, mycall, mmaly, mmacdonaldssfcu, maplpro, luntain, llaske, lbaker, Lawouach, laurionb, laughingboy, kurhan, kuno, kowenswp, klrohe, kevgu, jmesserly, jlunder, jdhardy, jbevain, jackeyoo, hhonisch, gz, gjones, fwereade, deadalusai, daveremy, darb, CurtHagenlocher, chaghi, cgravill, cartman, bobarnso, billchi, atifaziz, ashcor, alvanet, __Helmut__, fuzzyman, fabiofz, Eloff, egonw_, dungen, dsblank, dmajnemer, dinov, and dfugate. We really do appreciate your input which helps to make every release of IronPython better than the last. The IronPython Team

1 0

ANN: Resolver One 1.7 released
by Giles Thomas Oct. 27, 2009

Oct. 27, 2009

We are proud to announce the release of Resolver One, version 1.7. Resolver One is a Windows-based spreadsheet that integrates Python deeply into its recalculation loop, making the models you build more reliable and more maintainable. For version 1.7, we've made the code that you add to buttons on your worksheets execute in the background. This means that you can interrupt them easily if they run for too long, and also stops the rest of the application from pausing -- so you can keep working on other spreadsheets. You can read more about Resolver One here: <http://www.resolversystems.com/products/resolver-one/> We have a 31-day free trial version, so if you would like to take a look, you can download it from our website: <http://www.resolversystems.com/download/> If you want to use Resolver One in an Open Source project, we offer free licenses for that: <http://www.resolversystems.com/opensource/> Best regards, Giles -- Giles Thomas giles.thomas(a)resolversystems.com +44 (0) 20 7253 6372 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK

1 0

ANN: Python course, San Francisco, Nov 9-11
by wesley chun Oct. 27, 2009

Oct. 27, 2009

*FINAL REMINDER* come join us for another hardcore Python training course in San Francisco coming up in a few weeks! we have a few more slots available. bring your co-workers to take advantage of our multiple registration discount. we also feature a steeper discount for those who are primary/secondary teachers, students, as well as to those who have been more severely impacted by the economy. here is my original announcement for more info: http://mail.python.org/pipermail/python-list/2009-September/196228.html hope to meet you soon! -- wesley - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall, (c)2007,2001 "Python Fundamentals", Prentice Hall, (c)2009 http://corepython.com wesley.j.chun :: wescpy-at-gmail.com python training and technical consulting cyberweb.consulting : silicon valley, ca http://cyberwebconsulting.com

1 0