Mailman 3 April 2010 - Python-announce-list

Announcing IronPython 2.6.1
by David DiCato 12 Apr '10

12 Apr '10

Hello Python Community, We're pleased to announce the final release of IronPython 2.6.1. This version of IronPython makes great strides in stability and compatibility, including a considerable number of targeted bugfixes. This is our largest servicing release to date, and with your help both before and during the RC phase, along with the simultaneous release of .NET 4.0, this has become a very exciting release for all of us. IronPython 2.6.1 comes in two flavors - one that runs on top of .NET 4.0, and one that runs on any earlier framework starting with .NET 2.0 SP1. They can both be downloaded at http://ironpython.codeplex.com/releases/view/36280. We'd like to place a particular emphasis on the .NET 4.0 flavor of IronPython 2.6.1 and encourage all of you to try it out. It has a number of advantages over the 2.0 version, some of which Dave discusses on his blog at http://knowbody.livejournal.com/20751.html. These include faster startup time, compatibility with C#'s new dynamic keyword, and access to the numerous new features present in the updated Framework. The final release of Microsoft .NET Framework 4.0 is publically available as of today, and is required for this flavor of IronPython 2.6.1. Download it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=9cfb2d51-5ff4-4491… The IronPython 2.6.1 RC included fixes for well over 50 bugs, large and small. Ctypes has had a number of significant updates, including union support, variant_bool, and wintypes. Another focus has been on sys.settrace, making debugging more reliable. For example, sys.settrace now returns the correct frame, supports tracing through modules, and no longer interferes with "import os". Other notable fixes include thread-safe importing, and the missing error code in _winreg exception. In addition, we've made a substantial improvement in import time. Not only does this reduce startup time, but it can speed up the importing of large, definition-heavy modules by up to 50%. As you might imagine, the .NET 4.0 flavor of IronPython 2.6.1 RC has a few of its own changes designed for better interoperability with the framework. These include fixing some errors with Func<> and better runtime isolation when similarly-named assemblies in different locations are loaded in multiple engines. In addition, both the .NET 2.0 and .NET 4.0 builds support the new .NET 4.0 IStructuralEquatable and IStructuralComparable interfaces and maps them to the appropriate operations (__eq__, __hash__, __gt__, etc.). In the case of .NET 4.0, this replaces IValueEquality as the gold standard for defining equality in an interop-friendly manner. In the .NET 2.0 build, these interfaces are copied so that their use can be phased in while retaining IValueEquality for backwards compatibility. Since the RC, we have fixed numerous other issues, as well as adding CPython's ssl.py to our distribution. We've also made some major unicode-related changes in response to your feedback on the mailing list, changes that improve compatibility with certain third-party applications including Django. In particular, invoking unicode() or using unicode string formatting will now call __unicode__() first if it is present on the object. Finally, we've included a new code sample that shows how to use __clrtype__ to create custom CLR classes from IronPython. This sample is a sneak preview of what we expect will become a fully supported IronPython module, so we encourage anyone who is so inclined to try it out and let us know how it goes. Special thanks to Albert Szilvasy, amajorek, cendalc, clovery, egonw_, Eloff, essey, fabiofz, gjones, gpgemini, Haibo Luo, igalse, jazzcat, jdhardy, jlunder, JustinCle, klrohe, László de Almásy, laughingboy, lbaker, Lukas Cenovsky, marten_range, olav, paulfelix, pl6306, razam, roinet, russomf, sanxiyn, see_toronto <at> web <dot> de, Thomas Heller, variant77, vernondcole, William Reade, and Wolfram for reporting issues and making this a great release. Happy scripting! - The IronPython Team

1 0

OpenHatch: Find ways to contribute to open source (including Python itself)
by Asheesh Laroia 12 Apr '10

12 Apr '10

Hi all! I'm happy to announce the new version of the OpenHatch volunteer opportunity finder. Volunteer opportunity finder ---------------------------- Looking for a way to get involved in open source, but don't know where to start? Try browsing bugs in the OpenHatch volunteer opportunity finder: https//openhatch.org/search/ At PyCon, I led an open space where some of us tried finding things to work on. We found "easy" documentation bugs in Python, and wrote up patches. Within a few weeks, our patches were comitted to the Python core. Contributors to hundreds of projects (including Python itself) label bugs as good for new contributors. Those bugs are an opportunity for you to find a new project to contribute to in open source, so try browsing them at https://openhatch.org/search/?q=&toughness=bitesize Do you run an open source project? You can add your project to our index by clicking "Add a bug tracker." If you want to get new contributors more easily, try tagging bugs in your bug tracker as "bitesize."We're always looking for more projects to include in our crawls. About OpenHatch --------------- We're a website for helping people find ways to get involved in free, open source software. We also run a profile engine where you can tell your story in open source, emphasizing all the ways you've been involved in projects. (Successful open source projects take more than just code!) For more info ------------- Keep in touch by: * Joining #openhatch on irc.freenode.net * Replying to me and getting on our announcements list * Subscribing to @openhatchery on Twitter/Identi.ca * Reading our blog at https://openhatch.org/blog/ Or grab our source code: https://openhatch.org/source-code-etc/ -- Asheesh. -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, "The Omega Glory", stardate unknown

1 0

ANN: Pyrex 0.9.9
by Gregory Ewing 11 Apr '10

11 Apr '10

Pyrex 0.9.9 is now available: http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/ Highlights of this release: * Some facilities for interfacing with C++ code have been added. * Changes have been made to the semantics of exception catching to improve efficiency. * Preparation is being made for making 'not None' the default for extension type parameters to Python functions. A more detailed discussion of these changes can be found in the release notes here: http://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/version/Doc/Releas… What is Pyrex? -------------- Pyrex is a language for writing Python extension modules. It lets you freely mix operations on Python and C data, with all Python reference counting and error checking handled automatically.

1 0

SQLObject 0.12.3
by Oleg Broytman 11 Apr '10

11 Apr '10

Hello! I'm pleased to announce version 0.12.3, a minor bugfix release of branch 0.12 of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.12.3 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.12.2 ----------------- * Fixed a bug in replacing _connection in a case when no previous _connection has been set. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ phd(a)phd.pp.ru Programmers don't die, they just GOSUB without RETURN.

1 0

SQLObject 0.11.5
by Oleg Broytman 11 Apr '10

11 Apr '10

Hello! I'm pleased to announce version 0.11.5, a minor bugfix release of 0.11 branch of SQLObject. What is SQLObject ================= SQLObject is an object-relational mapper. Your database tables are described as classes, and rows are instances of those classes. SQLObject is meant to be easy to use and quick to get started with. SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite, Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB). Where is SQLObject ================== Site: http://sqlobject.org Development: http://sqlobject.org/devel/ Mailing list: https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss Archives: http://news.gmane.org/gmane.comp.python.sqlobject Download: http://cheeseshop.python.org/pypi/SQLObject/0.11.5 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.11.4 ----------------- * Fixed a bug in replacing _connection in a case when no previous _connection has been set. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ phd(a)phd.pp.ru Programmers don't die, they just GOSUB without RETURN.

1 0

[ANN] Next Meeting of pyCologne, April, 14th
by Thomas Lenarz 11 Apr '10

11 Apr '10

Hello, The next meeting of pyCologne will take place: Wednesday, April, 14th starting about 6.30 pm - 6.45 pm at Room 0.14, Benutzerrechenzentrum (RRZK-B) University of Cologne, Berrenrather Str. 136, 50937 Köln, Germany Agenda: -Organization of the Cologne PythonBarCamp taking place on April, 17th. Please refer to http://wiki.python-forum.de/PythonBarCamp At about 8.30 pm we will as usual enjoy the rest of the evening in a nearby restaurant. Further information including directions how to get to the location can be found at: http://www.pycologne.de (Sorry, the web-links are in German only.) Best Wishes Thomas P.S.: Due to spare-time issues on my side the regular announcements for our meetings will be taken over by another pyCologne-member. All the Best, Thomas

1 0

[RELEASED] 2.7 beta 1
by Benjamin Peterson 10 Apr '10

10 Apr '10

On behalf of the Python development team, I'm merry to announce the first beta release of Python 2.7. Python 2.7 is scheduled (by Guido and Python-dev) to be the last major version in the 2.x series. Though more major releases have not been absolutely ruled out, it's likely that the 2.7 release will an extended period of maintenance for the 2.x series. 2.7 includes many features that were first released in Python 3.1. The faster io module, the new nested with statement syntax, improved float repr, set literals, dictionary views, and the memoryview object have been backported from 3.1. Other features include an ordered dictionary implementation, unittests improvements, a new sysconfig module, and support for ttk Tile in Tkinter. For a more extensive list of changes in 2.7, see http://doc.python.org/dev/whatsnew/2.7.html or Misc/NEWS in the Python distribution. To download Python 2.7 visit: http://www.python.org/download/releases/2.7/ While this is a development release and is thus not suitable for production use, we encourage Python application and library developers to test the release with their code and report any bugs they encounter. The 2.7 documentation can be found at: http://docs.python.org/2.7 Please consider trying Python 2.7 with your code and reporting any bugs you may notice to: http://bugs.python.org Enjoy! -- Benjamin Peterson 2.7 Release Manager benjamin at python.org (on behalf of the entire python-dev team and 2.7's contributors)

1 0

Event: First meeting of Karlsruhe User Group (tentatively named "KaPy"), 2010-04-16, 19:00:00 CEST
by Jürgen Erhard 09 Apr '10

09 Apr '10

A new user group is being set up by some interested pythoneers from (around) Karlsruhe. The first meeting will be on Friday, 2010-04-16 (April 16th, 2010) at 19:00 (7pm) in the rooms of Entropia eV (the local affiliate of the CCC). See http://entropia.de/wiki/Anfahrt on how to get there. Or reply to me if you need instructions in English; there's a map on that page, but the devil's in the details, as always. Bye, J

1 0

[ANN] Leipzig Python User Group - Meeting, April 13, 2010, 08:00pm
by Stefan Schwarzer 09 Apr '10

09 Apr '10

=== Leipzig Python User Group === We will meet on Tuesday, April 13, 8:00 pm at the training center of Python Academy in Leipzig, Germany ( http://www.python-academy.com/center/find.html ). We will evaluate the booth we had at the Chemnitzer Linuxtage and plan improvements for next year. Food and soft drinks are provided. Please send a short confirmation mail to info(a)python-academy.de, so we can prepare appropriately. Everybody who uses Python, plans to do so or is interested in learning more about the language is encouraged to participate. While the meeting language will be mainly German, we will provide English translation if needed. Current information about the meetings are at http://www.python-academy.com/user-group . Stefan == Leipzig Python User Group === Wir treffen uns am Dienstag, 13.04.2010 um 20:00 Uhr im Schulungszentrum der Python Academy in Leipzig ( http://www.python-academy.de/Schulungszentrum/anfahrt.html ). Wir wollen unsere Stand-Erfahrungen von den Chemnitzer Linuxtagen auswerten und Verbesserungen für das nächste Jahr planen. Für das leibliche Wohl wird gesorgt. Eine Anmeldung unter info(a)python-academy.de wäre nett, damit wir genug Essen besorgen können. Willkommen ist jeder, der Interesse an Python hat, die Sprache bereits nutzt oder nutzen möchte. Aktuelle Informationen zu den Treffen sind unter http://www.python-academy.de/User-Group zu finden. Viele Grüße Stefan

1 0

ANN: unittest2 0.4.0 released
by Michael Foord 08 Apr '10

08 Apr '10

Hello all, I'm pleased to announce the release of version 0.4.0 of unittest2. * unittest2 on PyPI: http://pypi.python.org/pypi/unittest2 * Article introducing unittest2: http://www.voidspace.org.uk/python/articles/unittest2.shtml * Development docs for unittest (new features documented) <http://docs.python.org/dev/library/unittest.html * Mercurial Development Repository: http://hg.python.org/unittest2 unittest2 is an enhanced version of unittest including a standard test runner (automatic test discovery), class and module level fixtures (``setUpClass`` / ``setUpModule`` etc), many powerful new assert methods, better resource management with ``addCleanups`` and a host of other new features. These new features are *all* going into the Python version of unittest in Python 2.7 and Python 3.2. The point of unittest2 is that it works with Python 2.4 - 2.6; you can use it now. The latest release is 0.4.0, which roughly equates to the feature set that will be in unittest in Python 2.7 beta 1 which is due out any minute now. The last public release of unittest2 I announced was version 0.2.0 and there have been several new and important features since then. For a good roundup of the new features, see my blog entry: * http://www.voidspace.org.uk/python/weblog/arch_d7_2010_04_03.shtml#e1171 The full changelog for versions 0.3.0 and 0.4.0: 2010/04/08 - 0.4.0 ------------------ Addition of ``removeHandler`` for removing the control-C handler. ``delta`` keyword argument for ``assertAlmostEqual`` and ``assertNotAlmostEqual``. Addition of -b command line option (and ``TestResult.buffer``) for buffering stdout / stderr during test runs. Addition of ``TestCase.assertNotRegexpMatches``. Allow test discovery using dotted module names instead of a path. All imports requiring the signal module are now optional, for compatiblity with IronPython (or other platforms without this module). Tests fixed to be compatible with nosetest. 2010/03/26 - 0.3.0 ------------------ ``assertSameElements`` removed and ``assertItemsEqual`` added; assert that sequences contain the same elements. Addition of -f/--failfast command line option, stopping test run on first failure or error. Addition of -c/--catch command line option for better control-C handling during test runs. Added ``BaseTestSuite``, for use by frameworks that don't want to support shared class and module fixtures. Skipped test methods no longer have ``setUp`` and ``tearDown`` called around them. Faulty ``load_tests`` functions no longer halt test discovery. Using non-strings for failure messages now works. Potential for ``UnicodeDecodeError`` whilst creating failure messages fixed. Split out monolithic test module into a package. BUGFIX: Correct usage message now shown for unit2 scripts. BUGFIX: ``__unittest`` in module globals trims frames from that module in reported stacktraces. All the best, Michael Foord -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog

1 0