| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
Overview of changes in Pango 1.225
==================================
* Fix bug report email address
Overview of changes in Pango 1.224
==================================
* Ignore MYMETA.*
* Hush a few compiler warnings
* Add gitweb link to old ChangeLog
* Created %meta_merge which follows v2 of CPAN Meta Spec
- %meta_merge is used for generating metadata via
ExtUtils::MakeMaker/CPAN::Meta
Overview of changes in Pango 1.223
==================================
* Fix a test failure in t/PangoCairo.t
|
|
Remove FETCH_USING because it's not intended to be put in package Makefiles.
|
|
|
|
Glib::Object::Introspection uses the gobject-introspection and libffi projects
to dynamically create Perl bindings for a wide variety of libraries. Examples
include gtk+, webkit, libsoup and many more.
|
|
|
|
Overview of changes in Glib 1.304 (stable)
==========================================
* Fix compilation against glib < 2.34.0.
Overview of changes in Glib 1.303 (stable)
==========================================
* Revert the change to ref counting of initial wrappers of custom subclasses,
introduced in Glib 1.300. It caused issues with subclasses inheriting from
Glib::InitiallyUnowned.
* Fix a test failure with perl >= 5.19.4.
* Create a GType for GSpawnFlags and register it with the bindings.
Overview of changes in Glib 1.302 (stable)
==========================================
* Avoid misusing the macro PL_na, thus preventing issues when Glib is used in
conjunction with certain XS modules, among them XML::Parser and
String::Approx.
* Avoid memory corruption when registering boxed synonyms repeatedly.
Overview of changes in Glib 1.301 (stable)
==========================================
* t/options.t: skip tests in non-UTF-8 locales; fixes RT#83490
Overview of changes in Glib 1.300 (stable)
==========================================
* Stable release to coincide with the release of Perl 5.18.0
Since 1.28x (The previous stable release)
-----------------------------------------
* Ensure timely destruction of initial wrapper of custom subclasses
* Start changing module version numbers in all Perl modules in the
distribution, not just lib/Glib.pm; (Bugzilla #690464)
* Make Glib::Object subclassing more robust. This should in particular fix
issues revealed by the change to hash randomization introduced in perl
5.17.6.
* Correctly handle utf8-encoded strings in GPerlArgv. This should fix issues
seen with utf8-encoded strings in @ARGV with, for example, Gtk2->init.
Overview of changes in Glib 1.291 (unstable)
============================================
* Ensure timely destruction of initial wrapper of custom subclasses
* Start changing module version numbers in all Perl modules in the
distribution, not just lib/Glib.pm; (Bugzilla #690464)
Overview of changes in Glib 1.290 (unstable)
============================================
* Make Glib::Object subclassing more robust. This should in particular fix
issues revealed by the change to hash randomization introduced in perl
5.17.6.
* Correctly handle utf8-encoded strings in GPerlArgv. This should fix issues
seen with utf8-encoded strings in @ARGV with, for example, Gtk2->init.
Overview of changes in Glib 1.280 (stable)
==========================================
Since 1.26x (the previous stable series)
----------------------------------------
* Correctly handle the boxed type for GError.
* Ensure that custom signal marshallers are always used irregardless of
the spelling used for the signal name.
* Make the stack handling of some marshallers more robust, in
preparation for custom Glib::Boxed converters that call back into
Perl code.
* Add new C API gperl_register_boxed_synonym.
Since 1.270
-----------
* Fix building with perl <= 5.14.
Overview of changes in Glib 1.270 (unstable)
============================================
* Correctly handle the boxed type for GError.
* Ensure that custom signal marshallers are always used irregardless of the
spelling used for the signal name.
* Make the stack handling of some marshallers more robust, in
preparation for custom Glib::Boxed converters that call back into Perl
code.
* Add new C API gperl_register_boxed_synonym.
|
|
|
|
* Pass -liconv to LDFLAGS
|
|
|
|
|
|
3.7.1 -- 13 December 2013
-------------------------
- Improved the speed of HTML report generation by about 20%.
- Fixed the mechanism for finding OS-installed static files for the HTML report
so that it will actually find OS-installed static files.
3.7 --- 6 October 2013
----------------------
- Added the ``--debug`` switch to ``coverage run``. It accepts a list of
options indicating the type of internal activity to log to stderr.
- Improved the branch coverage facility, fixing `issue 92`_ and `issue 175`_.
- Running code with ``coverage run -m`` now behaves more like Python does,
setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.
- Coverage can now run .pyc files directly, closing `issue 264`_.
- Coverage properly supports .pyw files, fixing `issue 261`_.
- Omitting files within a tree specified with the ``source`` option would
cause them to be incorrectly marked as unexecuted, as described in
`issue 218`_. This is now fixed.
- When specifying paths to alias together during data combining, you can now
specify relative paths, fixing `issue 267`_.
- Most file paths can now be specified with username expansion (``~/src``, or
``~build/src``, for example), and with environment variable expansion
(``build/$BUILDNUM/src``).
- Trying to create an XML report with no files to report on, would cause a
ZeroDivideError, but no longer does, fixing `issue 250`_.
- When running a threaded program under the Python tracer, coverage no longer
issues a spurious warning about the trace function changing: "Trace function
changed, measurement is likely wrong: None." This fixes `issue 164`_.
- Static files necessary for HTML reports are found in system-installed places,
to ease OS-level packaging of coverage.py. Closes `issue 259`_.
- Source files with encoding declarations, but a blank first line, were not
decoded properly. Now they are. Thanks, Roger Hu.
- The source kit now includes the ``__main__.py`` file in the root coverage
directory, fixing `issue 255`_.
.. _issue 92: https://bitbucket.org/ned/coveragepy/issue/92/finally-clauses-arent-treated-properly-in
.. _issue 164: https://bitbucket.org/ned/coveragepy/issue/164/trace-function-changed-warning-when-using
.. _issue 175: https://bitbucket.org/ned/coveragepy/issue/175/branch-coverage-gets-confused-in-certain
.. _issue 207: https://bitbucket.org/ned/coveragepy/issue/207/run-m-cannot-find-module-or-package-in
.. _issue 242: https://bitbucket.org/ned/coveragepy/issue/242/running-a-two-level-package-doesnt-work
.. _issue 218: https://bitbucket.org/ned/coveragepy/issue/218/run-command-does-not-respect-the-omit-flag
.. _issue 250: https://bitbucket.org/ned/coveragepy/issue/250/uncaught-zerodivisionerror-when-generating
.. _issue 255: https://bitbucket.org/ned/coveragepy/issue/255/directory-level-__main__py-not-included-in
.. _issue 259: https://bitbucket.org/ned/coveragepy/issue/259/allow-use-of-system-installed-third-party
.. _issue 261: https://bitbucket.org/ned/coveragepy/issue/261/pyw-files-arent-reported-properly
.. _issue 264: https://bitbucket.org/ned/coveragepy/issue/264/coverage-wont-run-pyc-files
.. _issue 267: https://bitbucket.org/ned/coveragepy/issue/267/relative-path-aliases-dont-work
Version 3.6 --- 5 January 2013
------------------------------
- Added a page to the docs about troublesome situations, closing `issue 226`_,
and added some info to the TODO file, closing `issue 227`_.
.. _issue 226: https://bitbucket.org/ned/coveragepy/issue/226/make-readme-section-to-describe-when
.. _issue 227: https://bitbucket.org/ned/coveragepy/issue/227/update-todo
Version 3.6b3 --- 29 December 2012
----------------------------------
- Beta 2 broke the nose plugin. It's fixed again, closing `issue 224`_.
.. _issue 224: https://bitbucket.org/ned/coveragepy/issue/224/36b2-breaks-nosexcover
Version 3.6b2 --- 23 December 2012
----------------------------------
- Coverage.py runs on Python 2.3 and 2.4 again. It was broken in 3.6b1.
- The C extension is optionally compiled using a different more widely-used
technique, taking another stab at fixing `issue 80`_ once and for all.
- Combining data files would create entries for phantom files if used with
``source`` and path aliases. It no longer does.
- ``debug sys`` now shows the configuration file path that was read.
- If an oddly-behaved package claims that code came from an empty-string
filename, coverage.py no longer associates it with the directory name,
fixing `issue 221`_.
.. _issue 80: https://bitbucket.org/ned/coveragepy/issue/80/is-there-a-duck-typing-way-to-know-we-cant
.. _issue 221: https://bitbucket.org/ned/coveragepy/issue/221/coveragepy-incompatible-with-pyratemp
Version 3.6b1 --- 28 November 2012
----------------------------------
- Wildcards in ``include=`` and ``omit=`` arguments were not handled properly
in reporting functions, though they were when running. Now they are handled
uniformly, closing `issue 143`_ and `issue 163`_. **NOTE**: it is possible
that your configurations may now be incorrect. If you use ``include`` or
``omit`` during reporting, whether on the command line, through the API, or
in a configuration file, please check carefully that you were not relying on
the old broken behavior.
- The **report**, **html**, and **xml** commands now accept a ``--fail-under``
switch that indicates in the exit status whether the coverage percentage was
less than a particular value. Closes `issue 139`_.
- The reporting functions coverage.report(), coverage.html_report(), and
coverage.xml_report() now all return a float, the total percentage covered
measurement.
- The HTML report's title can now be set in the configuration file, with the
``--title`` switch on the command line, or via the API.
- Configuration files now support substitution of environment variables, using
syntax like ``${WORD}``. Closes `issue 97`_.
- Embarrassingly, the `[xml] output=` setting in the .coveragerc file simply
didn't work. Now it does.
- The XML report now consistently uses filenames for the filename attribute,
rather than sometimes using module names. Fixes `issue 67`_.
Thanks, Marcus Cobden.
- Coverage percentage metrics are now computed slightly differently under
branch coverage. This means that completely unexecuted files will now
correctly have 0% coverage, fixing `issue 156`_. This also means that your
total coverage numbers will generally now be lower if you are measuring
branch coverage.
- When installing, now in addition to creating a "coverage" command, two new
aliases are also installed. A "coverage2" or "coverage3" command will be
created, depending on whether you are installing in Python 2.x or 3.x.
A "coverage-X.Y" command will also be created corresponding to your specific
version of Python. Closes `issue 111`_.
- The coverage.py installer no longer tries to bootstrap setuptools or
Distribute. You must have one of them installed first, as `issue 202`_
recommended.
- The coverage.py kit now includes docs (closing `issue 137`_) and tests.
- On Windows, files are now reported in their correct case, fixing `issue 89`_
and `issue 203`_.
- If a file is missing during reporting, the path shown in the error message
is now correct, rather than an incorrect path in the current directory.
Fixes `issue 60`_.
- Running an HTML report in Python 3 in the same directory as an old Python 2
HTML report would fail with a UnicodeDecodeError. This issue (`issue 193`_)
is now fixed.
- Fixed yet another error trying to parse non-Python files as Python, this
time an IndentationError, closing `issue 82`_ for the fourth time...
- If `coverage xml` fails because there is no data to report, it used to
create a zero-length XML file. Now it doesn't, fixing `issue 210`_.
- Jython files now work with the ``--source`` option, fixing `issue 100`_.
- Running coverage under a debugger is unlikely to work, but it shouldn't fail
with "TypeError: 'NoneType' object is not iterable". Fixes `issue 201`_.
- On some Linux distributions, when installed with the OS package manager,
coverage.py would report its own code as part of the results. Now it won't,
fixing `issue 214`_, though this will take some time to be repackaged by the
operating systems.
- Docstrings for the legacy singleton methods are more helpful. Thanks Marius
Gedminas. Closes `issue 205`_.
- The pydoc tool can now show docmentation for the class `coverage.coverage`.
Closes `issue 206`_.
- Added a page to the docs about contributing to coverage.py, closing
`issue 171`_.
- When coverage.py ended unsuccessfully, it may have reported odd errors like
``'NoneType' object has no attribute 'isabs'``. It no longer does,
so kiss `issue 153`_ goodbye.
.. _issue 60: https://bitbucket.org/ned/coveragepy/issue/60/incorrect-path-to-orphaned-pyc-files
.. _issue 67: https://bitbucket.org/ned/coveragepy/issue/67/xml-report-filenames-may-be-generated
.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 89: https://bitbucket.org/ned/coveragepy/issue/89/on-windows-all-packages-are-reported-in
.. _issue 97: https://bitbucket.org/ned/coveragepy/issue/97/allow-environment-variables-to-be
.. _issue 100: https://bitbucket.org/ned/coveragepy/issue/100/source-directive-doesnt-work-for-packages
.. _issue 111: https://bitbucket.org/ned/coveragepy/issue/111/when-installing-coverage-with-pip-not
.. _issue 137: https://bitbucket.org/ned/coveragepy/issue/137/provide-docs-with-source-distribution
.. _issue 139: https://bitbucket.org/ned/coveragepy/issue/139/easy-check-for-a-certain-coverage-in-tests
.. _issue 143: https://bitbucket.org/ned/coveragepy/issue/143/omit-doesnt-seem-to-work-in-coverage
.. _issue 153: https://bitbucket.org/ned/coveragepy/issue/153/non-existent-filename-triggers
.. _issue 156: https://bitbucket.org/ned/coveragepy/issue/156/a-completely-unexecuted-file-shows-14
.. _issue 163: https://bitbucket.org/ned/coveragepy/issue/163/problem-with-include-and-omit-filename
.. _issue 171: https://bitbucket.org/ned/coveragepy/issue/171/how-to-contribute-and-run-tests
.. _issue 193: https://bitbucket.org/ned/coveragepy/issue/193/unicodedecodeerror-on-htmlpy
.. _issue 201: https://bitbucket.org/ned/coveragepy/issue/201/coverage-using-django-14-with-pydb-on
.. _issue 202: https://bitbucket.org/ned/coveragepy/issue/202/get-rid-of-ez_setuppy-and
.. _issue 203: https://bitbucket.org/ned/coveragepy/issue/203/duplicate-filenames-reported-when-filename
.. _issue 205: https://bitbucket.org/ned/coveragepy/issue/205/make-pydoc-coverage-more-friendly
.. _issue 206: https://bitbucket.org/ned/coveragepy/issue/206/pydoc-coveragecoverage-fails-with-an-error
.. _issue 210: https://bitbucket.org/ned/coveragepy/issue/210/if-theres-no-coverage-data-coverage-xml
.. _issue 214: https://bitbucket.org/ned/coveragepy/issue/214/coveragepy-measures-itself-on-precise
Version 3.5.3 --- 29 September 2012
-----------------------------------
- Line numbers in the HTML report line up better with the source lines, fixing
`issue 197`_, thanks Marius Gedminas.
- When specifying a directory as the source= option, the directory itself no
longer needs to have a ``__init__.py`` file, though its subdirectories do, to
be considered as source files.
- Files encoded as UTF-8 with a BOM are now properly handled, fixing
`issue 179`_. Thanks, Pablo Carballo.
- Fixed more cases of non-Python files being reported as Python source, and
then not being able to parse them as Python. Closes `issue 82`_ (again).
Thanks, Julian Berman.
- Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes `issue 147`_.
- Optimized .pyo files may not have been handled correctly, `issue 195`_.
Thanks, Marius Gedminas.
- Certain unusually named file paths could have been mangled during reporting,
`issue 194`_. Thanks, Marius Gedminas.
- Try to do a better job of the impossible task of detecting when we can't
build the C extension, fixing `issue 183`_.
- Testing is now done with `tox`_, thanks, Marc Abramowitz.
.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 147: https://bitbucket.org/ned/coveragepy/issue/147/massive-memory-usage-by-ctracer
.. _issue 179: https://bitbucket.org/ned/coveragepy/issue/179/htmlreporter-fails-when-source-file-is
.. _issue 183: https://bitbucket.org/ned/coveragepy/issue/183/install-fails-for-python-23
.. _issue 194: https://bitbucket.org/ned/coveragepy/issue/194/filelocatorrelative_filename-could-mangle
.. _issue 195: https://bitbucket.org/ned/coveragepy/issue/195/pyo-file-handling-in-codeunit
.. _issue 197: https://bitbucket.org/ned/coveragepy/issue/197/line-numbers-in-html-report-do-not-align
.. _tox: http://tox.readthedocs.org/
Version 3.5.2 --- 4 May 2012
----------------------------
No changes since 3.5.2.b1
Version 3.5.2b1 --- 29 April 2012
---------------------------------
- The HTML report has slightly tweaked controls: the buttons at the top of
the page are color-coded to the source lines they affect.
- Custom CSS can be applied to the HTML report by specifying a CSS file as
the extra_css configuration value in the [html] section.
- Source files with custom encodings declared in a comment at the top are now
properly handled during reporting on Python 2. Python 3 always handled them
properly. This fixes `issue 157`_.
- Backup files left behind by editors are no longer collected by the source=
option, fixing `issue 168`_.
- If a file doesn't parse properly as Python, we don't report it as an error
if the filename seems like maybe it wasn't meant to be Python. This is a
pragmatic fix for `issue 82`_.
- The ``-m`` switch on ``coverage report``, which includes missing line numbers
in the summary report, can now be specifed as ``show_missing`` in the
config file. Closes `issue 173`_.
- When running a module with ``coverage run -m <modulename>``, certain details
of the execution environment weren't the same as for
``python -m <modulename>``. This had the unfortunate side-effect of making
``coverage run -m unittest discover`` not work if you had tests in a
directory named "test". This fixes `issue 155`_ and `issue 142`_.
- Now the exit status of your product code is properly used as the process
status when running ``python -m coverage run ...``. Thanks, JT Olds.
- When installing into pypy, we no longer attempt (and fail) to compile
the C tracer function, closing `issue 166`_.
.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 142: https://bitbucket.org/ned/coveragepy/issue/142/executing-python-file-syspath-is-replaced
.. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover
.. _issue 157: https://bitbucket.org/ned/coveragepy/issue/157/chokes-on-source-files-with-non-utf-8
.. _issue 166: https://bitbucket.org/ned/coveragepy/issue/166/dont-try-to-compile-c-extension-on-pypy
.. _issue 168: https://bitbucket.org/ned/coveragepy/issue/168/dont-be-alarmed-by-emacs-droppings
.. _issue 173: https://bitbucket.org/ned/coveragepy/issue/173/theres-no-way-to-specify-show-missing-in
|
|
Times have changed, and py-setuptools is now the cool kid again.
|
|
At least there is no release available for the current stable
release, 2.2.0.
ok maintainer gdt@
|
|
Replace PYTHON_PATCH_SCRIPTS with REPLACE_PYTHON.
|
|
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
|
|
Mark as not ready for python-3.x.
|
|
py-cairo dependency here. Fake presence for configure script using cairo
flags.
Bump PKGREVISION.
This change allows using this package for both python-2.x and python-3.x.
|
|
Mark as not ready for python-3.x though.
Set PY_PEP3147=no since the infrastructure doesn't support it.
Use versioned_dependencies.mk for cairo.
|
|
Also set PY_PEP3147=no since the package infrastructure does not handle
__pycache__ correctly.
|
|
Bump PKGREVISION.
Fix build and PLIST for python-3.x
XXX: strangely, this isn't happy with py-distribute for python-3.x.
XXX: I don't understand why, but a build dependency on setuptools fixes
XXX: installation, so I've done that.
|
|
Changelog:
What's new in 1.532.1 (2013/11/25)
Collecting findbugs analysis results occasionally causes ssh slave to go offline causing job to abort (issue 19619)
Bytecode compatibility transformer mistakenly corrupts org.apache.ivy.core.settings.IvySettings.triggers (issue 19383)
Functions.globalIota overflow (issue 20085)
Upgrade bundled versions of credentials, ssh-credentials and ssh-slaves plugins (issue 19945)
/me/my-views/editDescription may be used by any user to set global description (issue 18633)
Missing base directory in ZIP from .../artifact/dir/subdir/*zip*/subdir.zip (issue 19947)
After deleting last build, next build of last build is zombie (issue 19920)
Upgrade error to 1.531: PROXY_HEADER is null (issue 19613)
Upgrade bundled versions of credentials and ssh-slaves so we can assume available (issue 20071)
Collecting finbugs analysis results randomly fails with exception (issue 18879)
ViewJobFilter.filter expect "All jobs that are possible." but don't get recursive ones (issue 20143)
Download build artifacts as zip generates a corrupted file (issue 19752)
Jenkins redirecting from https to http (issue 10675)
java.io.IOException: Unexpected termination of the channel (issue 18836)
When installing a plugin and the needed dependencies have compatibility issues, warn the user (issue 19739)
Installing a plugin with optional dependencies doesn't upgrade the optional dependencies when needed (issue 19736)
After upgrade from 1.519 to 1.526 -> NumberFormatException occurs during maven 3 build (issue 19251)
What's new in 1.509.4 (2013/10/09)
Configurable loggers should capture messages on slaves (issue 18274)
@RequirePOST and similar should send a 405 (issue 16918)
Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate (issue 12629)
[XStream] ConcurrentModificationException from DefaultConverterLookup (issue 18775)
@QueryParameter with @RelativePath broken (issue 18776)
fingerprint are truncated (issue 19515)
Environment variable replacement/resolving (issue 16660)
failed to archive slave artifacts. Unexpected end of ZLIB input stream (issue 19473)
winstone.ClientSocketException: Failed to write to client (issue 10524)
/log/all polluted with FINE* messages from other loggers (issue 18959)
Incorrect redirect after editing view with Unicode name (issue 18373)
Flyweight jobs and zero executors (issue 7291)
ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization (issue 15437)
Buttons do not work in IE 11 (issue 19171)
CLI login command fails on Windows (issue 19192)
Problems with "Latest Test Result" and "Aggregated Test Result" links (issue 9637)
Exception while trigger downstream projects (issue 17247)
Maven 2 jobs fail (exception in MavenFingerprinter) (issue 18441)
Outdated JRuby libs (issue 14351)
Deadlock (issue 18589)
When copying folder, display names of contained jobs are gratuitously cleared (issue 18074)
Incorrect redirection after delete of job in folder in view (issue 17575)
Javadoc project action yields HTTP 404 (issue 19168)
Memory exhaustion parsing large test stdio from Surefire (issue 15382)
With lazy-build loading estimated build duration may become expensive (issue 18196)
Can't build using maven 3.1.0 (issue 15935)
Cannot create a custom logger matching any namespace (issue 17983)
Clean up fingerprint records that correspond to the deleted build recods (issue 18417)
"projects tied to slave" shows unrelated maven module jobs (issue 17451)
hudson.security.AccessDeniedException2: anonymous is missing the Administer permission (issue 15578)
”My Views" links leads to 404 Not Found (issue 17317)
Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers (issue 18677)
New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null (issue 18846)
|
|
Bump PKGREVISION.
|
|
0.9.34
~~~~~~
Improvements
------------
* Added ability for ``testtools.TestCase`` instances to force a test to
fail, even if no assertions failed. (Thomi Richards)
* Added ``testtools.content.StacktraceContent``, a content object that
automatically creates a ``StackLinesContent`` object containing the current
stack trace. (Thomi Richards)
* ``AnyMatch`` is now exported properly in ``testtools.matchers``.
(Robert Collins, Rob Kennedy, github #44)
* In Python 3.3, if there are duplicate test ids, tests.sort() will
fail and raise TypeError. Detect the duplicate test ids firstly in
sorted_tests() to ensure that all test ids are unique.
(Kui Shi, #1243922)
* ``json_content`` is now in the ``__all__`` attribute for
``testtools.content``. (Robert Collins)
* Network tests now bind to 127.0.0.1 to avoid (even temporary) network
visible ports. (Benedikt Morbach, github #46)
* Test listing now explicitly indicates by printing 'Failed to import' and
exiting (2) when an import has failed rather than only signalling through the
test name. (Robert Collins, #1245672)
* ``test_compat.TestDetectEncoding.test_bom`` now works on Python 3.3 - the
corner case with euc_jp is no longer permitted in Python 3.3 so we can
skip it. (Martin [gz], #1251962)
0.9.33
~~~~~~
Improvements
------------
* Added ``addDetailuniqueName`` method to ``testtools.TestCase`` class.
(Thomi Richards)
* Removed some unused code from ``testtools.content.TracebackContent``.
(Thomi Richards)
* Added ``testtools.StackLinesContent``: a content object for displaying
pre-processed stack lines. (Thomi Richards)
* ``StreamSummary`` was calculating testsRun incorrectly: ``exists`` status
tests were counted as run tests, but they are not.
(Robert Collins, #1203728)
0.9.32
~~~~~~
Regular maintenance release. Special thanks to new contributor, Xiao Hanyu!
Changes
-------
* ``testttols.compat._format_exc_info`` has been refactored into several
smaller functions. (Thomi Richards)
Improvements
------------
* Stacktrace filtering no longer hides unittest frames that are surrounded by
user frames. We will reenable this when we figure out a better algorithm for
retaining meaning. (Robert Collins, #1188420)
* The compatibility code for skipped tests with unittest2 was broken.
(Robert Collins, #1190951)
* Various documentation improvements (Clint Byrum, Xiao Hanyu).
0.9.31
~~~~~~
Improvements
------------
* ``ExpectedException`` now accepts a msg parameter for describing an error,
much the same as assertEquals etc. (Robert Collins)
0.9.30
~~~~~~
A new sort of TestResult, the StreamResult has been added, as a prototype for
a revised standard library test result API. Expect this API to change.
Although we will try to preserve compatibility for early adopters, it is
experimental and we might need to break it if it turns out to be unsuitable.
Improvements
------------
* ``assertRaises`` works properly for exception classes that have custom
metaclasses
* ``ConcurrentTestSuite`` was silently eating exceptions that propagate from
the test.run(result) method call. Ignoring them is fine in a normal test
runner, but when they happen in a different thread, the thread that called
suite.run() is not in the stack anymore, and the exceptions are lost. We now
create a synthetic test recording any such exception.
(Robert Collins, #1130429)
* Fixed SyntaxError raised in ``_compat2x.py`` when installing via Python 3.
(Will Bond, #941958)
* New class ``StreamResult`` which defines the API for the new result type.
(Robert Collins)
* New support class ``ConcurrentStreamTestSuite`` for convenient construction
and utilisation of ``StreamToQueue`` objects. (Robert Collins)
* New support class ``CopyStreamResult`` which forwards events onto multiple
``StreamResult`` objects (each of which receives all the events).
(Robert Collins)
* New support class ``StreamSummary`` which summarises a ``StreamResult``
stream compatibly with ``TestResult`` code. (Robert Collins)
* New support class ``StreamTagger`` which adds or removes tags from
``StreamResult`` events. (RobertCollins)
* New support class ``StreamToDict`` which converts a ``StreamResult`` to a
series of dicts describing a test. Useful for writing trivial stream
analysers. (Robert Collins)
* New support class ``TestControl`` which permits cancelling an in-progress
run. (Robert Collins)
* New support class ``StreamFailFast`` which calls a ``TestControl`` instance
to abort the test run when a failure is detected. (Robert Collins)
* New support class ``ExtendedToStreamDecorator`` which translates both regular
unittest TestResult API calls and the ExtendedTestResult API which testtools
has supported into the StreamResult API. ExtendedToStreamDecorator also
forwards calls made in the StreamResult API, permitting it to be used
anywhere a StreamResult is used. Key TestResult query methods like
wasSuccessful and shouldStop are synchronised with the StreamResult API
calls, but the detailed statistics like the list of errors are not - a
separate consumer will be created to support that.
(Robert Collins)
* New support class ``StreamToExtendedDecorator`` which translates
``StreamResult`` API calls into ``ExtendedTestResult`` (or any older
``TestResult``) calls. This permits using un-migrated result objects with
new runners / tests. (Robert Collins)
* New support class ``StreamToQueue`` for sending messages to one
``StreamResult`` from multiple threads. (Robert Collins)
* New support class ``TimestampingStreamResult`` which adds a timestamp to
events with no timestamp. (Robert Collins)
* New ``TestCase`` decorator ``DecorateTestCaseResult`` that adapts the
``TestResult`` or ``StreamResult`` a case will be run with, for ensuring that
a particular result object is used even if the runner running the test doesn't
know to use it. (Robert Collins)
* New test support class ``testtools.testresult.doubles.StreamResult``, which
captures all the StreamResult events. (Robert Collins)
* ``PlaceHolder`` can now hold tags, and applies them before, and removes them
after, the test. (Robert Collins)
* ``PlaceHolder`` can now hold timestamps, and applies them before the test and
then before the outcome. (Robert Collins)
* ``StreamResultRouter`` added. This is useful for demultiplexing - e.g. for
partitioning analysis of events or sending feedback encapsulated in
StreamResult events back to their source. (Robert Collins)
* ``testtools.run.TestProgram`` now supports the ``TestRunner`` taking over
responsibility for formatting the output of ``--list-tests``.
(Robert Collins)
* The error message for setUp and tearDown upcall errors was broken on Python
3.4. (Monty Taylor, Robert Collins, #1140688)
* The repr of object() on pypy includes the object id, which was breaking a
test that accidentally depended on the CPython repr for object().
(Jonathan Lange)
0.9.29
~~~~~~
A simple bug fix, and better error messages when you don't up-call.
Changes
-------
* ``testtools.content_type.ContentType`` incorrectly used ',' rather than ';'
to separate parameters. (Robert Collins)
Improvements
------------
* ``testtools.compat.unicode_output_stream`` was wrapping a stream encoder
around ``io.StringIO`` and ``io.TextIOWrapper`` objects, which was incorrect.
(Robert Collins)
* Report the name of the source file for setUp and tearDown upcall errors.
(Monty Taylor)
0.9.28
~~~~~~
Testtools has moved VCS - https://github.com/testing-cabal/testtools/ is
the new home. Bug tracking is still on Launchpad, and releases are on Pypi.
We made this change to take advantage of the richer ecosystem of tools around
Git, and to lower the barrier for new contributors.
Improvements
------------
* New ``testtools.testcase.attr`` and ``testtools.testcase.WithAttributes``
helpers allow marking up test case methods with simple labels. This permits
filtering tests with more granularity than organising them into modules and
test classes. (Robert Collins)
0.9.27
~~~~~~
Improvements
------------
* New matcher ``HasLength`` for matching the length of a collection.
(Robert Collins)
* New matcher ``MatchesPredicateWithParams`` make it still easier to create
ad hoc matchers. (Robert Collins)
* We have a simpler release process in future - see doc/hacking.rst.
(Robert Collins)
0.9.26
~~~~~~
Brown paper bag fix: failed to document the need for setup to be able to use
extras. Compounded by pip not supporting setup_requires.
Changes
-------
* setup.py now can generate egg_info even if extras is not available.
Also lists extras in setup_requires for easy_install.
(Robert Collins, #1102464)
0.9.25
~~~~~~
Changes
-------
* ``python -m testtools.run --load-list`` will now preserve any custom suites
(such as ``testtools.FixtureSuite`` or ``testresources.OptimisingTestSuite``)
rather than flattening them.
(Robert Collins, #827175)
* Testtools now depends on extras, a small library split out from it to contain
generally useful non-testing facilities. Since extras has been around for a
couple of testtools releases now, we're making this into a hard dependency of
testtools. (Robert Collins)
* Testtools now uses setuptools rather than distutils so that we can document
the extras dependency. (Robert Collins)
Improvements
------------
* Testtools will no longer override test code registered details called
'traceback' when reporting caught exceptions from test code.
(Robert Collins, #812793)
|
|
there are no common files.
Fix PLIST for python-3.x.
|
|
|
|
Mark as not for python-3.x. Bump PKGREVISION.
|
|
to distinfo
XXX: doesn't build
|
|
|
|
0.4.0
=====
:release date: 2013-10-21
Inconpatible Changes
--------------------
* Raises TypeError instead of ValueError when packer receives unsupported type.
Changes
-------
* Support New msgpack spec.
0.3.0
=====
Inconpatible Changes
--------------------
* Default value of ``use_list`` is ``True`` for now. (It was ``False`` for 0.2.x)
You should pass it explicitly for compatibility to 0.2.x.
* `Unpacker.unpack()` and some unpack methods now raise `OutOfData` instead of
`StopIteration`. `StopIteration` is used for iterator protocol only.
Changes
-------
* Pure Python fallback module is added. (thanks to bwesterb)
* Add ``.skip()`` method to ``Unpacker`` (thanks to jnothman)
* Add capturing feature. You can pass the writable object to
``Unpacker.unpack()`` as a second parameter.
* Add ``Packer.pack_array_header`` and ``Packer.pack_map_header``.
These methods only pack header of each type.
* Add ``autoreset`` option to ``Packer`` (default: True).
Packer doesn't return packed bytes and clear internal buffer.
* Add ``Packer.pack_map_pairs``. It packs sequence of pair to map type.
0.2.4
=======
:release date: 2012-12-22
Bugs fixed
----------
* Fix SEGV when object_hook or object_pairs_hook raise Exception. (#39)
0.2.3
=======
:release date: 2012-12-11
Changes
-------
* Warn when use_list is not specified. It's default value will be changed in 0.3.
Bugs fixed
-----------
* Can't pack subclass of dict.
0.2.2
=======
:release date: 2012-09-21
Changes
-------
* Add ``use_single_float`` option to ``Packer``. When it is true, packs float
object in single precision format.
Bugs fixed
-----------
* ``unpack()`` didn't restores gc state when it called with gc disabled.
``unpack()`` doesn't control gc now instead of restoring gc state collectly.
User can control gc state when gc cause performance issue.
* ``Unpacker``'s ``read_size`` option didn't used.
0.2.1
=======
:release date: 2012-08-20
Changes
-------
* Add ``max_buffer_size`` parameter to Unpacker. It limits internal buffer size
and allows unpack data from untrusted source safely.
* Unpacker's buffer reallocation algorithm is less greedy now. It cause perforamce
derease in rare case but memory efficient and don't allocate than ``max_buffer_size``.
Bugs fixed
----------
* Fix msgpack didn't work on SPARC Solaris. It was because choosing wrong byteorder
on compilation time. Use ``sys.byteorder`` to get correct byte order.
Very thanks to Chris Casey for giving test environment to me.
0.2.0
=======
:release date: 2012-06-27
Changes
-------
* Drop supporting Python 2.5 and unify tests for Py2 and Py3.
* Use new version of msgpack-c. It packs correctly on big endian platforms.
* Remove deprecated packs and unpacks API.
Bugs fixed
----------
* #8 Packing subclass of dict raises TypeError. (Thanks to Steeve Morin.)
|
|
2013-12-23 version 0.5.8:
* Move to the new github repository msgpack/msgpack-c
* Support the new deserialization specification
* fixes the problem of unpack helpers for array and map with 32bit compilers (#37, #38)
* Other bug fixes and refactoring: #46, #41, #36, #35, #33, #32, #30, #29, #28, #27, #26, #25, #8, #3
* Update of documents: #23, #18, #17
|
|
Fixes build with lua 5.1. Bump PKGREVISION.
|
|
|
|
|
|
Commit message that should have been in previous commit follows:
Version 2.2.0 is backwards compatible and adds the following new
features:
Added Sarprop training
Added fann_create_train for creating an empty training data struct
Added fann_copy for copying an ANN
Added cascade_min_out_epochs and cascade_min_cand_epochs to
improve cascade training
Added extra checks when training, to ensure that data and network
input and output sizes matches
Added Visual Studio 2010 solution
Added support for 64bit architecture
Cleanup in sources
Moved source from CVS to GIT
|
|
(However, it seems upstream no longer includes python bindings.)
|
|
|
|
|
|
|
|
Upstream changes:
0.24 2013-09-07
- added missing lib include (Karen Etheridge)
0.23 2013-09-04
- stop using old and deprecated (or soon to be deprecated) functions from
Class::MOP
|
|
Upstream changes:
2.1202 2014-01-19
[BUG FIXES]
- string comparisons are now possible with Moose exceptions (#92232)
2.1201 2014-01-11
[OTHER]
- re-release to index pod files (Moose::Cookbook::*, Moose::Manual::* etc).
|
|
Bump PKGREVISION.
|
|
and nothing in pkgsrc uses it.
|
|
Set LICENSE.
|
|
|
|
0.9.4 2013-11-30
IMPROVEMENTS
* Add ssh_kwargs attribute to ParamikoSSHVendor. (milki)
* Add Repo.set_description(). (Víðir Valberg Guðmundsson)
* Add a basic `dulwich.porcelain` module. (Jelmer Vernooij, Marcin Kuzminski)
* Various performance improvements for object access.
(Jelmer Vernooij)
* New function `get_transport_and_path_from_url`,
similar to `get_transport_and_path` but only
supports URLs.
(Jelmer Vernooij)
* Add support for file:// URLs in `get_transport_and_path_from_url`.
(Jelmer Vernooij)
* Add LocalGitClient implementation.
(Jelmer Vernooij)
BUG FIXES
* Support filesystems with 64bit inode and device numbers.
(André Roth)
CHANGES
* Ref handling has been moved to dulwich.refs.
(Jelmer Vernooij)
API CHANGES
* Remove long deprecated RefsContainer.set_ref().
(Jelmer Vernooij)
* Repo.ref() is now deprecated in favour of Repo.refs[].
(Jelmer Vernooij)
FEATURES
* Add support for graftpoints. (milki)
0.9.3 2013-09-27
BUG FIXES
* Fix path for stdint.h in MANIFEST.in. (Jelmer Vernooij)
0.9.2 2013-09-26
BUG FIXES
* Include stdint.h in MANIFEST.in (Mark Mikofski)
0.9.1 2013-09-22
BUG FIXES
* Support lookups of 40-character refs in BaseRepo.__getitem__. (Chow Loong Jin, Jelmer Vernooij)
* Fix fetching packs with side-band-64k capability disabled. (David Keijser, Jelmer Vernooij)
* Several fixes in send-pack protocol behaviour - handling of empty pack files and deletes.
(milki, #1063087)
* Fix capability negotiation when fetching packs over HTTP.
(#1072461, William Grant)
* Enforce determine_wants returning an empty list rather than None. (Fabien Boucher, Jelmer Vernooij)
* In the server, support pushes just removing refs. (Fabien Boucher, Jelmer Vernooij)
IMPROVEMENTS
* Support passing a single revision to BaseRepo.get_walker() rather than a list of revisions.
(Alberto Ruiz)
* Add `Repo.get_description` method. (Jelmer Vernooij)
* Support thin packs in Pack.iterobjects() and Pack.get_raw().
(William Grant)
* Add `MemoryObjectStore.add_pack` and `MemoryObjectStore.add_thin_pack` methods.
(David Bennett)
* Add paramiko-based SSH vendor. (Aaron O'Mullan)
* Support running 'dulwich.server' and 'dulwich.web' using 'python -m'.
(Jelmer Vernooij)
* Add ObjectStore.close(). (Jelmer Vernooij)
* Raise appropriate NotImplementedError when encountering dumb HTTP servers.
(Jelmer Vernooij)
API CHANGES
* SSHVendor.connect_ssh has been renamed to SSHVendor.run_command.
(Jelmer Vernooij)
* ObjectStore.add_pack() now returns a 3-tuple. The last element will be an
abort() method that can be used to cancel the pack operation.
(Jelmer Vernooij)
0.9.0 2013-05-31
BUG FIXES
* Push efficiency - report missing objects only. (#562676, Artem Tikhomirov)
* Use indentation consistent with C Git in config files.
(#1031356, Curt Moore, Jelmer Vernooij)
* Recognize and skip binary files in diff function.
(Takeshi Kanemoto)
* Fix handling of relative paths in dulwich.client.get_transport_and_path.
(Brian Visel, #1169368)
* Preserve ordering of entries in configuration.
(Benjamin Pollack)
* Support ~ expansion in SSH client paths. (milki, #1083439)
* Support relative paths in alternate paths.
(milki, Michel Lespinasse, #1175007)
* Log all error messages from wsgiref server to the logging module. This
makes the test suit quiet again. (Gary van der Merwe)
* Support passing None for empty tree in changes_from_tree.
(Kevin Watters)
* Support fetching empty repository in client. (milki, #1060462)
IMPROVEMENTS:
* Add optional honor_filemode flag to build_index_from_tree.
(Mark Mikofski)
* Support core/filemode setting when building trees. (Jelmer Vernooij)
* Add chapter on tags in tutorial. (Ryan Faulkner)
FEATURES
* Add support for mergetags. (milki, #963525)
* Add support for posix shell hooks. (milki)
|
|
Bump PKGREVISION.
|
