Log message:
Needs py-funcsigs>=1, reported by joerg.
Bump PKGREVISION.

Log message:
Fix previous.

Log message:
Update py-mock to 2.0.0

Library
-------

- Issue #26323: Add Mock.assert_called() and Mock.assert_called_once()
  methods to unittest.mock. Patch written by Amit Saha.

- Issue #22138: Fix mock.patch behavior when patching descriptors. Restore
  original values after patching. Patch contributed by Sean McCully.

- Issue #24857: Comparing call_args to a long sequence now correctly returns a
  boolean result instead of raising an exception.  Patch by A Kaptur.

- Issue #23004: mock_open() now reads binary data correctly when the type of
  read_data is bytes.  Initial patch by Aaron Hill.

- Issue #21750: mock_open.read_data can now be read from each instance, as it
  could in Python 3.3.

- Issue #18622: unittest.mock.mock_open().reset_mock would recurse infinitely.
  Patch from Nicola Palumbo and Laurent De Buyst.

- Issue #23661: unittest.mock side_effects can now be exceptions again. This
  was a regression vs Python 3.4. Patch from Ignacio Rossi

- Issue #23310: Fix MagicMock's initializer to work with __methods__, just
  like configure_mock().  Patch by Kasia Jachim.

- Issue #23568: Add rdivmod support to MagicMock() objects.
  Patch by Håkan Lövdahl.

- Issue #23581: Add matmul support to MagicMock. Patch by Håkan Lövdahl.

- Issue #23326: Removed __ne__ implementations.  Since fixing default __ne__
  implementation in issue #21408 they are redundant. *** NOT BACKPORTED ***

- Issue #21270: We now override tuple methods in mock.call objects so that
  they can be used as normal call attributes.

- Issue #21256: Printout of keyword args should be in deterministic order in
  a mock function call. This will help to write better doctests.

- Issue #21262: New method assert_not_called for Mock.
  It raises AssertionError if the mock has been called.

- Issue #21238: New keyword argument `unsafe` to Mock. It raises
  `AttributeError` incase of an attribute startswith assert or assret.

- Issue #21239: patch.stopall() didn't work deterministically when the same
  name was patched more than once.

- Issue #21222: Passing name keyword argument to mock.create_autospec now
  works.

- Issue #17826: setting an iterable side_effect on a mock function created by
  create_autospec now works. Patch by Kushal Das.

- Issue #17826: setting an iterable side_effect on a mock function created by
  create_autospec now works. Patch by Kushal Das.

- Issue #20968: unittest.mock.MagicMock now supports division.
  Patch by Johannes Baiter.

- Issue #20189: unittest.mock now no longer assumes that any object for
  which it could get an inspect.Signature is a callable written in Python.
  Fix courtesy of Michael Foord.

- Issue #17467: add readline and readlines support to mock_open in
  unittest.mock.

- Issue #17015: When it has a spec, a Mock object now inspects its signature
  when matching calls, so that arguments can be matched positionally or
  by name.

- Issue #15323: improve failure message of Mock.assert_called_once_with

- Issue #14857: fix regression in references to PEP 3135 implicit __class__
  closure variable (Reopens issue #12370)

- Issue #14295: Add unittest.mock

Log message:
py-mock requires py-funcsigs on Python<3.3. Bump PKGREVISION.

Log message:
Add SHA512 digests for distfiles for devel category

Issues found with existing distfiles:
	distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
	distfiles/fortran-utils-1.1.tar.gz
	distfiles/ivykis-0.39.tar.gz
	distfiles/enum-1.11.tar.gz
	distfiles/pvs-3.2-libraries.tgz
	distfiles/pvs-3.2-linux.tgz
	distfiles/pvs-3.2-solaris.tgz
	distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Log message:
Update to 1.3.0:

1.3.0
-----

* Update sync point
* Issue #21750: Further fixup to be styled like other mock APIs
* Typo fix in mock.patch

Log message:
Update to 1.2.0:

1.2.0
-----

* Revert "Issue #21750: mock_open.read_data can now be read from each \ 
instance, as it"

1.1.4
-----

* Add 2.6 back to classifiers
* Record sync point
* Issue #21750: mock_open.read_data can now be read from each instance, as it \ 
could in Python 3.3
* Issue #18622: unittest.mock.mock_open().reset_mock would recurse infinitely
* Folk should test 2.6 locally too
* Closes #279: setuptools.version is too new
* Support python 2.6

1.1.3
-----

* Update sync point and sync docs
* Issue #23661: unittest.mock side_effects can now be exceptions again
* Abort installation if the installer is using setuptools<17.1

Log message:
Add "pbr" and "six" dependencies, from requirements.txt. \ 
Bump PKGREVISION.

Log message:
Update to 1.1.2:

1.1.2
-----

* Closes #269: setup_requires pbr 1.3

1.1.1
-----

* Closes #257: version the dependency on six
* Rename README.txt to README.rst

1.1.0
-----

* Make reproducing travis behaviour somewhat easier
* Cleanup version number handling
* Overhaul docs
* Update docs
* Remove stale MANIFEST.in, ignore pbr outputs
* Convert to a package, use pbr, update metadata
* Bump versions
* Officially drop 2.6 support
* Issue #23310: Fix MagicMock's initializer to work with __methods__. Behavior \ 
equivalent to m.configure_mock(). Patch by Kasia Jachim
* Issue #23568: Add rdivmod support to MagicMock() objects
* Issue #23581: Add matmul support to MagicMock
* Issue #23326: Removed __ne__ implementations. Since fixing default __ne__ \ 
implementation in issue #21408 they are redundant
* Issue #22823: Use set literals instead of creating a set from a list. Fixed an \ 
output of sets in examples
* Closes #21270 : We now override tuple methods in mock.call objects
* Suppress a couple more DeprecationWarnings in the test suite
* Closes #21256: Printout of keyword args in deterministic order in mock calls
* Removes unused varargs and varkwargs from assert_not_called()
* Closes Issue 21262: New method assert_not_called for Mock
* Closes Issue 21238: New keyword argument `unsafe` to Mock
* Closes issue 21239. unittest.mock.patch.stopall() did not work \ 
deterministically when the same name was patched multiple times
* Closes Issue 21222
* Closes issue 17660. You no longer need to explicitly pass create=True when \ 
patching builtin names
* Issue 17826. Setting an iterable side_effect on a mock created by \ 
create_autospec now works
* Issue 20968. unittest.mock.MagicMock now supports division
* Issue #20189: Four additional builtin types (PyTypeObject, PyMethodDescr_Type, \ 
_PyMethodWrapper_Type, and PyWrapperDescr_Type) have been modified to provide \ 
introspection information for builtins. Also: many additional Lib, test suite, \ 
and Argument Clinic fixes
* Issue #19594: Use specific asserts in unittest tests
* Remove shadowed test
* Adjust comment
* Issue #19013: add a __main__ to unittest.test.testmock to ease CLI invocation
* Issue #19013: add unittest.main() epilogs to unittest.mock's own test modules
* Process DEFAULT values in mock side_effect that returns iterator
* Closes issue 17467. Add readline and readlines support to unittest.mock.mock_open
* Issue #17047: remove doubled words added in 3.3 as reported by Serhiy \ 
Storchaka and Matthew Barnett
* Issue #17015: When it has a spec, a Mock object now inspects its signature \ 
when matching calls, so that arguments can be matched positionally or by name
* Closes issue 15323. Improve failure message of Mock.assert_called_once_with
* Close #14857: fix regression in references to PEP 3135 implicit __class__ \ 
closure variable. Reopens issue #12370, but also updates unittest.mock to \ 
workaround that issue
* Remove incorrect comment
* Closes issue 14634. unittest.mock.create_autospec now supports keyword only \ 
arguments
* unittest.mock: removed another bit of Python 2 only code
* Adding unittest.mock documentation
* unittest.mock: remove another piece of Python 2 specific code
* Remove more Python 2 code from unittest.mock (obsolete function attributes)
* Support subclassing unittest.mock._patch and fix various obscure bugs around \ 
patcher spec arguments
* unittest.mock.MagicMock objects are now unorderable by default
* Removed XXX from unittest.mock docstring and switch to a nicer \ 
try...except...finally
* Remove more Python 2 compatibility cruft from unittest.mock
* PEP 417: Adding unittest.mock
* Ignore patch rejects too
* Add NEWS
* Add PyPy to travis
* Issue #20189: Four additional builtin types
* Just hard-depend on unittest2
* Fix typo in test name
* Some basic release process notes
* Ignore more editor files
* Add testrepository configuration
* We never need sudo. Containers FTW
* Fixup ignores
* Iterating on .travis.yml
* Setup Travis-CI

Log message:
Update to 1.0.1

Upstream changes:
2012/11/5 Version 1.0.1
Functions decorated with patch variants have a __wrapped__ attribute pointing to \ 
the original function. This brings compatibility with the default behaviour in \ 
Python 3.3 (due to a new feature in functools.wraps).
Note that due to changes in tox, mock is no longer tested with Python 2.4. The \ 
compatibility code has not been removed so it probably still works, but tests \ 
are no longer run.

2012/10/07 Version 1.0.0
No changes since 1.0.0 beta 1. This version has feature parity with \ 
unittest.mock in Python 3.3.

Full list of changes since 0.8:

mocksignature, along with the mocksignature argument to patch, removed
Support for deleting attributes (accessing deleted attributes will raise an \ 
AttributeError)
Added the mock_open helper function for mocking the builtin open
__class__ is assignable, so a mock can pass an isinstance check without \ 
requiring a spec
Addition of PropertyMock, for mocking properties
MagicMocks made unorderable by default (in Python 3). The comparison methods \ 
(other than equality and inequality) now return NotImplemented
Propagate traceback info to support subclassing of _patch by other libraries
create_autospec works with attributes present in results of dir that can’t be \ 
fetched from the object’s class. Contributed by Konstantine Rybnikov
Any exceptions in an iterable side_effect will be raised instead of returned
In Python 3, create_autospec now supports keyword only arguments
Added patch.stopall method to stop all active patches created by start
BUGFIX: calling MagicMock.reset_mock wouldn’t reset magic method mocks
BUGFIX: calling reset_mock on a MagicMock created with autospec could raise an \ 
exception
BUGFIX: passing multiple spec arguments to patchers (spec , spec_set and \ 
autospec) had unpredictable results, now it is an error
BUGFIX: using spec=True and create=True as arguments to patchers could result in \ 
using DEFAULT as the spec. Now it is an error instead
BUGFIX: using spec or autospec arguments to patchers, along with spec_set=True \ 
did not work correctly
BUGFIX: using an object that evaluates to False as a spec could be ignored
BUGFIX: a list as the spec argument to a patcher would always result in a \ 
non-callable mock. Now if __call__ is in the spec the mock is callable