Version 0.9.6
http://svn.edgewall.org/repos/babel/tags/0.9.6/
(Mar 17 2011, from branches/stable/0.9.x)
* Backport r493-494: documentation typo fixes.
* Make the CLDR import script work with Python 2.7.
* Fix various typos.
* Fixed Python 2.3 compatibility (ticket #146, #233).
* Sort output of list-locales.
* Make the POT-Creation-Date of the catalog being updated equal to
POT-Creation-Date of the template used to update (ticket #148).
* Use a more explicit error message if no option or argument (command) is
passed to pybabel (ticket #81).
* Keep the PO-Revision-Date if it is not the default value (ticket #148).
* Make --no-wrap work by reworking --width's default and mimic xgettext's
behaviour of always wrapping comments (ticket #145).
* Fixed negative offset handling of Catalog._set_mime_headers (ticket #165).
* Add --project and --version options for commandline (ticket #173).
* Add a __ne__() method to the Local class.
* Explicitly sort instead of using sorted() and don't assume ordering
(Python 2.3 and Jython compatibility).
* Removed ValueError raising for string formatting message checkers if the
string does not contain any string formattings (ticket #150).
* Fix Serbian plural forms (ticket #213).
* Small speed improvement in format_date() (ticket #216).
* Fix number formatting for locales where CLDR specifies alt or draft
items (ticket #217)
* Fix bad check in format_time (ticket #257, reported with patch and tests by
jomae)
* Fix so frontend.CommandLineInterface.run does not accumulate logging
handlers (#227, reported with initial patch by dfraser)
* Fix exception if environment contains an invalid locale setting (#200)
0.9.12
~~~~~~
This is a very big release. We've made huge improvements on three fronts:
1. Test failures are way nicer and easier to read
2. Matchers and ``assertThat`` are much more convenient to use
3. Correct handling of extended unicode characters
We've trimmed off the fat from the stack trace you get when tests fail, we've
cut out the bits of error messages that just didn't help, we've made it easier
to annotate mismatch failures, to compare complex objects and to match raised
exceptions.
Testing code was never this fun.
Changes
-------
* ``AfterPreproccessing`` renamed to ``AfterPreprocessing``, which is a more
correct spelling. Old name preserved for backwards compatibility, but is
now deprecated. Please stop using it.
(Jonathan Lange, #813460)
* ``assertThat`` raises ``MismatchError`` instead of
``TestCase.failureException``. ``MismatchError`` is a subclass of
``AssertionError``, so in most cases this change will not matter. However,
if ``self.failureException`` has been set to a non-default value, then
mismatches will become test errors rather than test failures.
* ``gather_details`` takes two dicts, rather than two detailed objects.
(Jonathan Lange, #801027)
* ``MatchesRegex`` mismatch now says "<value> does not match /<regex>/" rather
than "<regex> did not match <value>". The regular expression contains fewer
backslashes too. (Jonathan Lange, #818079)
* Tests that run with ``AsynchronousDeferredRunTest`` now have the ``reactor``
attribute set to the running reactor. (Jonathan Lange, #720749)
Improvements
------------
* All public matchers are now in ``testtools.matchers.__all__``.
(Jonathan Lange, #784859)
* ``assertThat`` can actually display mismatches and matchers that contain
extended unicode characters. (Jonathan Lange, Martin [gz], #804127)
* ``assertThat`` output is much less verbose, displaying only what the mismatch
tells us to display. Old-style verbose output can be had by passing
``verbose=True`` to assertThat. (Jonathan Lange, #675323, #593190)
* ``assertThat`` accepts a message which will be used to annotate the matcher.
This can be given as a third parameter or as a keyword parameter.
(Robert Collins)
* Automated the Launchpad part of the release process.
(Jonathan Lange, #623486)
* Correctly display non-ASCII unicode output on terminals that claim to have a
unicode encoding. (Martin [gz], #804122)
* ``DocTestMatches`` correctly handles unicode output from examples, rather
than raising an error. (Martin [gz], #764170)
* ``ErrorHolder`` and ``PlaceHolder`` added to docs. (Jonathan Lange, #816597)
* ``ExpectedException`` now matches any exception of the given type by
default, and also allows specifying a ``Matcher`` rather than a mere regular
expression. (Jonathan Lange, #791889)
* ``FixtureSuite`` added, allows test suites to run with a given fixture.
(Jonathan Lange)
* Hide testtools's own stack frames when displaying tracebacks, making it
easier for test authors to focus on their errors.
(Jonathan Lange, Martin [gz], #788974)
* Less boilerplate displayed in test failures and errors.
(Jonathan Lange, #660852)
* ``MatchesException`` now allows you to match exceptions against any matcher,
rather than just regular expressions. (Jonathan Lange, #791889)
* ``MatchesException`` now permits a tuple of types rather than a single type
(when using the type matching mode). (Robert Collins)
* ``MatchesStructure.byEquality`` added to make the common case of matching
many attributes by equality much easier. ``MatchesStructure.byMatcher``
added in case folk want to match by things other than equality.
(Jonathan Lange)
* New convenience assertions, ``assertIsNone`` and ``assertIsNotNone``.
(Christian Kampka)
* New matchers:
* ``AllMatch`` matches many values against a single matcher.
(Jonathan Lange, #615108)
* ``Contains``. (Robert Collins)
* ``GreaterThan``. (Christian Kampka)
* New helper, ``safe_hasattr`` added. (Jonathan Lange)
* ``reraise`` added to ``testtools.compat``. (Jonathan Lange)
HDF5 is a data model, library, and file format for storing and
managing data. It supports an unlimited variety of datatypes, and
is designed for flexible and efficient I/O and for high volume and
complex data. HDF5 is portable and is extensible, allowing applications
to evolve in their use of HDF5. The HDF5 Technology suite includes
tools and applications for managing, manipulating, viewing, and
analyzing data in the HDF5 format.
This package provides C++ wrappers for the HDF5 C library.
Changes from previous:
0.98 Wed, 23 Feb 2011 14:38:02 +1100
Bug Fixes
* subtest() should not fail if $? is non-zero. (Aaron Crane)
Docs
* The behavior of is() and undef has been documented. (Pedro Melo)
0.97_01 Fri Aug 27 22:50:30 PDT 2010
Test Fixes
* Adapted the tests for the new Perl 5.14 regex stringification.
(Karl Williamson) [github 44]
Doc Fixes
* Document how to test "use Foo ()". (Todd Rinaldo) [github 41]
Feature Changes
* subtest() no longer has a prototype. It was just getting in the way.
[rt.cpan.org 54239]
* The filehandles used by default will now inherit any filehandle
disciplines from STDOUT and STDERR IF AND ONLY IF they were applied
before Test::Builder is loaded. More later. [rt.cpan.org 46542]
Changes from previous:
0.3.0
- Reverted feature to match POD head section =head2, =head3 and =head4
because of backward compatibility issue (RT bug #70942)
0.2.9 2011-09-03
- This command does not generate warnings anymore:
perl -e 'use Getopt::Euclid; print $Getopt::Euclid::VERSION;'
- Required and optional arguments can now be put in a POD head section
=head2, =head3 and =head4 for more flexibility
0.2.8 2011-09-02
- Support for optional defaults (RT bug #61438, patch from Paolo Medeo)
- Extended the grammar of recognized POD headers
- Usage error message now mentions the --man option in addition to --help
Changes from previous:
0.22 2011-05-09
- Fix issues where the metaclass gets reinitialized after the call to
'extends' but before 'make_immutable'. This could happen if a role
used an extension which provided an application_to_class metarole,
since the role application would then apply a metarole to the class,
and metarole application currently causes metaclass reinitialization
in Moose. (ugh.)
0.21 2011-04-29
- Allow this module to work with constructors with names other than
'new'. If you're extending a class with a constructor named something
other than 'new', you should declare this when calling extends, as in:
extends 'Foo' => { -constructor_name => 'create' };
This will ensure that calling 'create' will also call Moose's
constructor.
0.20 2011-03-22
- fix warning when passing inline_constructor => 0 with no superclass new
method (rafl).
0.19 2011-03-02
- don't die if superclass doesn't have a 'new' method
0.18 2011-02-09
- forward compat for Moose 2.0
0.17 2010-11-08
- convert to Test::Fatal, and dep on it
0.16 2010-10-05
- Make it work with Moose 1.15 (Dave Rolsky).
Allow maximum number of targets in initiator to be set in mk.conf
with ISCSI_INITIATOR_MAX_TARGETS
Changes:
Provide function in libiscsi to return the compile-time limit on number of
targets. Use this function in the initiator, to ensure that the same limit
is used throughout (i.e. stop you attempting to compile the initiator with a
different limit to the library - the initiator uses the library for most of
its functionality).
If truncating the number of targets in the initiator, truncate it to the
correct amount, not half of what it should be.
Obey RFC3720 when determining targets. SendTargets=All MUST be supported
on a discovery session, and MUST NOT be supported on an operational session.
Previously, SendTargets=All was used both in the initial discovery session
and the later session. (from Daisuke Aoyama - author of istgt).
The GPRBuild Solaris targets were too specific and didn't recognize
GNAT-AUX on Solaris (actually OpenIndiana). This patch makes sure
GPRBuild-AUX can use GNAT-AUX and any other gcc-based compiler.
so it can be closed without affecting anybody else. gcc < 3.4 used to
have a separate argument to control this behaviour which was apparently
removed.
Untested, please report any problems to GNATS.
Changelog:
2011-06-13 release 1.0.22 of cvsd
changes since 1.0.21:
+ don't log EINTR on select() any more, not even in debug mode
+ fix for cvsd-buildroot to also work on multiarch setups
+ log address and port with bind() failures
+ Debian packaging updates
2010-09-08 release 1.0.21 of cvsd
changes since 1.0.20:
+ handle failure to bind() as a fatal error now
2010-09-05 release 1.0.20 of cvsd
changes since 1.0.19:
+ correctly listen on IPv4 and IPv6 addresses with recent Glibc
versions by not depending on the order of address records returned by
getaddrinfo() and work regardless of net.ipv6.bindv6only sysctl
2010-08-17 release 1.0.19 of cvsd
changes since 1.0.18:
+ cvsd-buildroot: ignore commented out lines in CVSROOT/passwd files
+ cvsd-buildroot: set an umask for generated files
+ some documentation updates
+ change init script dependency on $remote_fs (for /usr) from Should
to Required (thanks lintian)
+ Debian packaging improvements
2010-01-14 release 1.0.18 of cvsd
changes since 1.0.17:
+ use simpler shell semantics in cvsd-buildroot to fix a problem
with bash 4
+ fix call to uname in the cvsd-buginfo script
2009-12-30 release 1.0.17 of cvsd
changes since 1.0.16:
+ update to automake 1.11
+ some small spelling fixes in documentation
+ changed references to home page and contact email addresses to use
arthurdejong.org
+ Debian packaging improvements
Drastically improved memory handling for certain use cases
Added a new rendering backend to speed up Canvas operations on Windows systems
Bookmark and password changes now sync almost instantly when using Firefox Sync
The 'http://' URL prefix is now hidden by default
Added support for text-overflow: ellipsis
Added support for the Web Timing specification
Enhanced support for MathML
The WebSocket protocol has been updated from version 7 to version 8
Added an opt-in system for users to send performance data back to Mozilla
to improve future versions of Firefox
Fixed several stability issues
Fixed several security issues
* Use a monotonically increasing timer
* Immediately expire items when given a negative expiration time
* Fix memcached-tool to print about all slabs
* Properly daemonize memcached for debian
* Don't permanently close UDP listeners on error
* Allow memcached-init to start multiple instances (not recommended)
* Issue 214: Search for network libraries before searching for libevent
* Issue 213: Search for clock_gettime in librt
* Issue 115: accont for CAS in item_size_ok
* Fix incredibly slim race for maxconns handler. Should no longer hang ever
* Issue 183: Reclaim items dead by flush_all
* Issue 200: Don't fire dtrace probe as the last thing in a function
* Several SSL bufferevent fixes
* A Solaris sendfile bugfix
* A few other IOCP and rate-limiting bufferevent fixes
* Memory leak fixes
* Coverity fixes
* Portability and build fixes
* and more...
- The makefile's substitution of PREFIX and SH accidentally got rolled
into patch-ac at some point and thereby hardcoded. Since all patch-ac
was doing was setting these, make the substitution work without a
patch and remove patch-ac entirely.
- Commit some LP64 fixes I've had sitting in my tree since 2008 for
some reason.
- Fix some pkglint.
- PKGREVISION -> 4.
XXX: This is not right, but the way this thing is built doesn't give
XXX: too many choices at the moment. Should be fixed properly sometime.
XXX: This way the package is at least installable...
(for some reason there are two separate copies of it) to match the
POSIX definition.
Fixing this "right" would be a lot of work and does not seem
worthwhile, especially since this package looks to be more or less
dead upstream and is probably a good candidate for removal.
Revision history for Scope-Upper
0.16 2011-09-03 23:00 UTC
+ Add : uplevel($code, @args, $cxt) executes $code with arguments @args
in the upper context pointed by $cxt.
This is an XS version of the well-known uplevel() routine from
Sub::Uplevel. There are a few differences between both
implmentations that are listed in the documentation.
The XS version is roughly 10 times faster than the pure-Perl
version.
0.15 2011-08-24 14:20 UTC
+ Fix : Localizing subroutines in an higher scope will now correctly
update the method cache.
0.14 2011-02-27 00:00 UTC
+ Fix : [RT #64997] : Compatibility with perl 5.13.10.
Thanks Dave Mitchell for the notice.
+ Tst : Lengthy tests have been ported to Test::Leaner, making the
whole test suite about 50% faster.
0.13 2010-12-20 01:00 UTC
+ Fix : [RT #61904] : Stack corruption when using unwind() under
Devel::NYTProf.
Thanks Sergey Aleynikov for contributing a fix.
+ Fix : [RT #63378] : Compatibility with perl 5.13.8.
Thanks Andreas J. König for bisecting the issue.
+ Tst : Threads tests are now only run on perl 5.13.4 and higher.
They could segfault randomly because of what seems to be an
internal bug of Perl, which has been addressed in 5.13.4.
There is also an environment variable that allows you to
forcefully run those tests, but it should be set only for
author testing and not for end users.
