nose 0.10.3 released

nose version 0.10.3 fixes a serious bug found in 0.10.2's nosetests setuptools command, and updates the coverage plugin to be more friendly to other plugins that trigger imports in begin(). Thanks to Philip Jenvey and Ned Batchelder for reporting these issues. As usual, more information can be found on the nose project page.

nose 0.10.2 released

I'm pleased to announce the release of nose 0.10.2. This release features tons of bugfixes and patches, mostly contributed by users, as well as improvements to custom exception reporting, and official support for jython (svn trunk only, for now).

As usual, more information may be found on the nose project page.

Many thanks to everyone who contributed to this release. I expect it to be the last in the 0.10 series. 0.11 will bring some new builtin plugins, and begin to set the stage for big changes to reporting.

nose 0.9.2 released

Nose 0.9.2 includes quite a few bug fixes and new features. The most significant are the new nosetests setuptools command, contributed by James Casbon, better support for python 2.2 thanks to a patch from Chad Whitacre, and some useful utilities for testing Twisted programs and writing decorators contributed by Antoine Pitrou. Thanks to them all, and the many other folks who contributed patches and filed bug reports and feature requests.

Nose's project home has moved from python hosting to Google code. Please update your svn checkouts and bookmarks. To check out the current trunk:

svn co http://python-nose.googlecode.com/svn/trunk

To file issues, go to the new issues page. To read up on features, writing plugins, and other topics, visit the new wiki.

nose has moved

nose has moved to google code. The new place to check out the development version and file bugs or feature requests is http://code.google.com/p/python-nose/.

The move was forced by a combination of unfortunate circumstances. First, python hosting has been hit with a wave of trac spam in their free trac/svn service. Second, they decided to handle this wave of spam by shutting down all of the projects that they didn't think were active. They gave no notice nor offered any explanation: the projects were simply 404'd. After waiting half a day for the apparent outage to be solved, and then reading here that they would no longer be accepting new projects until they had cleaned up their server, which could take "weeks or months," I decided that, whether or not I could regain access to nose.python-hosting.com, I would be foolish to continue using a service that might disappear and take my work with it at any time.

The folks at python hosting, once I was able to get an email reply from them, have been very accommodating and kindly turned the project back on so that I could pull down my tickets. I'm grateful to python hosting for hosting nose for over a year, and for the great service that they have provided to the whole python community by offering free hosting to open source projects. I hope this is just a hiccup, and that their service will be operational again soon. I only wish that they had chosen to handle their spam problem in a more open and professional manner. Given how they did handle it, though, I feel that I have no choice but to take my projects elsewhere.