TestFixtures 2.0.0 Released!

0 views
Skip to first unread message

Chris Withers

unread,
Sep 23, 2011, 3:46:41 AM9/23/11
to testing-...@lists.idyll.org, Python List, simpl...@googlegroups.com
Hi All,

I'm happy to announce a new release major release of TestFixtures.
This release is 99% backwards compatible, but a lot has changed under
the hood and there's some major new functionality, so thought it was
time for a bump.

The big changes are:

- compare now uses a registry of comparers in the same way that
unitest2's assertEquals does. You can register your own globally,
register the default comparers for your own types and use a specific
registry for a specific call to compare.

- The handling of timezones has been reworked in `test_datetime` again.
(did anyone ever mention that timezones are hard ;-) )
It feels more intuitive now, but it is backwards incompatible in
the case where the `tzinfo` parameter to the `test_datetime`
constructor was used.

For details, read:

http://packages.python.org/testfixtures/datetime.html#timezones

The full list of changes can be found here:

http://packages.python.org/testfixtures/changes.html

The package is on PyPI and a full list of all the links to docs, issue
trackers and the like can be found here:

http://www.simplistix.co.uk/software/python/testfixtures

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Chris Withers

unread,
Sep 23, 2011, 7:52:40 AM9/23/11
to testing-...@lists.idyll.org, Python List, simpl...@googlegroups.com
On 23/09/2011 08:46, Chris Withers wrote:
> I'm happy to announce a new release major release of TestFixtures.
> This release is 99% backwards compatible, but a lot has changed under
> the hood and there's some major new functionality, so thought it was
> time for a bump.

Of course, a 2.0.0 release wouldn't be complete without a fairly
show-stopping lack of backwards compatibility... Thankfully, I've
managed to return the case (comparison of generators with iterators) to
its previous state with the 2.0.1 release I've just pushed out...

Reply all
Reply to author
Forward
0 new messages