Scheduled monthly dependency update for November #96

pyup-bot · 2019-11-01T15:10:21Z

Update attrs from 19.1.0 to 19.3.0.

Changelog

19.3.0

-------------------

Changes
^^^^^^^

- Fixed ``auto_attribs`` usage when default values cannot be compared directly with ``==``, such as ``numpy`` arrays.
`585 &lt;https://github.com/python-attrs/attrs/issues/585&gt;`_


----

19.2.0

-------------------

Backward-incompatible Changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Removed deprecated ``Attribute`` attribute ``convert`` per scheduled removal on 2019/1.
This planned deprecation is tracked in issue `307 &lt;https://github.com/python-attrs/attrs/issues/307&gt;`_.
`504 &lt;https://github.com/python-attrs/attrs/issues/504&gt;`_
- ``__lt__``, ``__le__``, ``__gt__``, and ``__ge__`` do not consider subclasses comparable anymore.

This has been deprecated since 18.2.0 and was raising a ``DeprecationWarning`` for over a year.
`570 &lt;https://github.com/python-attrs/attrs/issues/570&gt;`_


Deprecations
^^^^^^^^^^^^

- The ``cmp`` argument to ``attr.s()`` and ``attr.ib()`` is now deprecated.

Please use ``eq`` to add equality methods (``__eq__`` and ``__ne__``) and ``order`` to add ordering methods (``__lt__``, ``__le__``, ``__gt__``, and ``__ge__``) instead – just like with `dataclasses &lt;https://docs.python.org/3/library/dataclasses.html&gt;`_.

Both are effectively ``True`` by default but it&#39;s enough to set ``eq=False`` to disable both at once.
Passing ``eq=False, order=True`` explicitly will raise a ``ValueError`` though.

Since this is arguably a deeper backward-compatibility break, it will have an extended deprecation period until 2021-06-01.
After that day, the ``cmp`` argument will be removed.

``attr.Attribute`` also isn&#39;t orderable anymore.
`574 &lt;https://github.com/python-attrs/attrs/issues/574&gt;`_


Changes
^^^^^^^

- Updated ``attr.validators.__all__`` to include new validators added in `425`_.
`517 &lt;https://github.com/python-attrs/attrs/issues/517&gt;`_
- Slotted classes now use a pure Python mechanism to rewrite the ``__class__`` cell when rebuilding the class, so ``super()`` works even on environments where ``ctypes`` is not installed.
`522 &lt;https://github.com/python-attrs/attrs/issues/522&gt;`_
- When collecting attributes using ``attr.s(auto_attribs=True)``, attributes with a default of ``None`` are now deleted too.
`523 &lt;https://github.com/python-attrs/attrs/issues/523&gt;`_,
`556 &lt;https://github.com/python-attrs/attrs/issues/556&gt;`_
- Fixed ``attr.validators.deep_iterable()`` and ``attr.validators.deep_mapping()`` type stubs.
`533 &lt;https://github.com/python-attrs/attrs/issues/533&gt;`_
- ``attr.validators.is_callable()`` validator now raises an exception ``attr.exceptions.NotCallableError``, a subclass of ``TypeError``, informing the received value.
`536 &lt;https://github.com/python-attrs/attrs/issues/536&gt;`_
- ``attr.s(auto_exc=True)`` now generates classes that are hashable by ID, as the documentation always claimed it would.
`543 &lt;https://github.com/python-attrs/attrs/issues/543&gt;`_,
`563 &lt;https://github.com/python-attrs/attrs/issues/563&gt;`_
- Added ``attr.validators.matches_re()`` that checks string attributes whether they match a regular expression.
`552 &lt;https://github.com/python-attrs/attrs/issues/552&gt;`_
- Keyword-only attributes (``kw_only=True``) and attributes that are excluded from the ``attrs``&#39;s ``__init__`` (``init=False``) now can appear before mandatory attributes.
`559 &lt;https://github.com/python-attrs/attrs/issues/559&gt;`_
- The fake filename for generated methods is now more stable.
It won&#39;t change when you restart the process.
`560 &lt;https://github.com/python-attrs/attrs/issues/560&gt;`_
- The value passed to ``attr.ib(repr=…)`` can now be either a boolean (as before) or a callable.
That callable must return a string and is then used for formatting the attribute by the generated ``__repr__()`` method.
`568 &lt;https://github.com/python-attrs/attrs/issues/568&gt;`_
- Added ``attr.__version_info__`` that can be used to reliably check the version of ``attrs`` and write forward- and backward-compatible code.
Please check out the `section on deprecated APIs &lt;http://www.attrs.org/en/stable/api.htmldeprecated-apis&gt;`_ on how to use it.
`580 &lt;https://github.com/python-attrs/attrs/issues/580&gt;`_

.. _`425`: https://github.com/python-attrs/attrs/issues/425


----

19.1.0

-------------------

Backward-incompatible Changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Fixed a bug where deserialized objects with ``cache_hash=True`` could have incorrect hash code values.
This change breaks classes with ``cache_hash=True`` when a custom ``__setstate__`` is present.
An exception will be thrown when applying the ``attrs`` annotation to such a class.
This limitation is tracked in issue `494 &lt;https://github.com/python-attrs/attrs/issues/494&gt;`_.
`482 &lt;https://github.com/python-attrs/attrs/issues/482&gt;`_


Changes
^^^^^^^

- Add ``is_callable``, ``deep_iterable``, and ``deep_mapping`` validators.

* ``is_callable``: validates that a value is callable
* ``deep_iterable``: Allows recursion down into an iterable,
 applying another validator to every member in the iterable
 as well as applying an optional validator to the iterable itself.
* ``deep_mapping``: Allows recursion down into the items in a mapping object,
 applying a key validator and a value validator to the key and value in every item.
 Also applies an optional validator to the mapping object itself.

You can find them in the ``attr.validators`` package.
`425`_
- Fixed stub files to prevent errors raised by mypy&#39;s ``disallow_any_generics = True`` option.
`443 &lt;https://github.com/python-attrs/attrs/issues/443&gt;`_
- Attributes with ``init=False`` now can follow after ``kw_only=True`` attributes.
`450 &lt;https://github.com/python-attrs/attrs/issues/450&gt;`_
- ``attrs`` now has first class support for defining exception classes.

If you define a class using ``attr.s(auto_exc=True)`` and subclass an exception, the class will behave like a well-behaved exception class including an appropriate ``__str__`` method, and all attributes additionally available in an ``args`` attribute.
`500 &lt;https://github.com/python-attrs/attrs/issues/500&gt;`_
- Clarified documentation for hashing to warn that hashable objects should be deeply immutable (in their usage, even if this is not enforced).
`503 &lt;https://github.com/python-attrs/attrs/issues/503&gt;`_


----

18.2.0

-------------------

Deprecations
^^^^^^^^^^^^

- Comparing subclasses using ``&lt;``, ``&gt;``, ``&lt;=``, and ``&gt;=`` is now deprecated.
The docs always claimed that instances are only compared if the types are identical, so this is a first step to conform to the docs.

Equality operators (``==`` and ``!=``) were always strict in this regard.
`394 &lt;https://github.com/python-attrs/attrs/issues/394&gt;`_


Changes
^^^^^^^

- ``attrs`` now ships its own `PEP 484 &lt;https://www.python.org/dev/peps/pep-0484/&gt;`_ type hints.
Together with `mypy &lt;http://mypy-lang.org&gt;`_&#39;s ``attrs`` plugin, you&#39;ve got all you need for writing statically typed code in both Python 2 and 3!

At that occasion, we&#39;ve also added `narrative docs &lt;https://www.attrs.org/en/stable/types.html&gt;`_ about type annotations in ``attrs``.
`238 &lt;https://github.com/python-attrs/attrs/issues/238&gt;`_
- Added *kw_only* arguments to ``attr.ib`` and ``attr.s``, and a corresponding *kw_only* attribute to ``attr.Attribute``.
This change makes it possible to have a generated ``__init__`` with keyword-only arguments on Python 3, relaxing the required ordering of default and non-default valued attributes.
`281 &lt;https://github.com/python-attrs/attrs/issues/281&gt;`_,
`411 &lt;https://github.com/python-attrs/attrs/issues/411&gt;`_
- The test suite now runs with ``hypothesis.HealthCheck.too_slow`` disabled to prevent CI breakage on slower computers.
`364 &lt;https://github.com/python-attrs/attrs/issues/364&gt;`_,
`396 &lt;https://github.com/python-attrs/attrs/issues/396&gt;`_
- ``attr.validators.in_()`` now raises a ``ValueError`` with a useful message even if the options are a string and the value is not a string.
`383 &lt;https://github.com/python-attrs/attrs/issues/383&gt;`_
- ``attr.asdict()`` now properly handles deeply nested lists and dictionaries.
`395 &lt;https://github.com/python-attrs/attrs/issues/395&gt;`_
- Added ``attr.converters.default_if_none()`` that allows to replace ``None`` values in attributes.
For example ``attr.ib(converter=default_if_none(&quot;&quot;))`` replaces ``None`` by empty strings.
`400 &lt;https://github.com/python-attrs/attrs/issues/400&gt;`_,
`414 &lt;https://github.com/python-attrs/attrs/issues/414&gt;`_
- Fixed a reference leak where the original class would remain live after being replaced when ``slots=True`` is set.
`407 &lt;https://github.com/python-attrs/attrs/issues/407&gt;`_
- Slotted classes can now be made weakly referenceable by passing ``attr.s(weakref_slot=True)``.
`420 &lt;https://github.com/python-attrs/attrs/issues/420&gt;`_
- Added *cache_hash* option to ``attr.s`` which causes the hash code to be computed once and stored on the object.
`426 &lt;https://github.com/python-attrs/attrs/issues/426&gt;`_
- Attributes can be named ``property`` and ``itemgetter`` now.
`430 &lt;https://github.com/python-attrs/attrs/issues/430&gt;`_
- It is now possible to override a base class&#39; class variable using only class annotations.
`431 &lt;https://github.com/python-attrs/attrs/issues/431&gt;`_


----

18.1.0

-------------------

Changes
^^^^^^^

- ``x=X(); x.cycle = x; repr(x)`` will no longer raise a ``RecursionError``, and will instead show as ``X(x=...)``.

`95 &lt;https://github.com/python-attrs/attrs/issues/95&gt;`_
- ``attr.ib(factory=f)`` is now syntactic sugar for the common case of ``attr.ib(default=attr.Factory(f))``.

`178 &lt;https://github.com/python-attrs/attrs/issues/178&gt;`_,
`356 &lt;https://github.com/python-attrs/attrs/issues/356&gt;`_
- Added ``attr.field_dict()`` to return an ordered dictionary of ``attrs`` attributes for a class, whose keys are the attribute names.

`290 &lt;https://github.com/python-attrs/attrs/issues/290&gt;`_,
`349 &lt;https://github.com/python-attrs/attrs/issues/349&gt;`_
- The order of attributes that are passed into ``attr.make_class()`` or the *these* argument of ``attr.s()`` is now retained if the dictionary is ordered (i.e. ``dict`` on Python 3.6 and later, ``collections.OrderedDict`` otherwise).

Before, the order was always determined by the order in which the attributes have been defined which may not be desirable when creating classes programatically.

`300 &lt;https://github.com/python-attrs/attrs/issues/300&gt;`_,
`339 &lt;https://github.com/python-attrs/attrs/issues/339&gt;`_,
`343 &lt;https://github.com/python-attrs/attrs/issues/343&gt;`_
- In slotted classes, ``__getstate__`` and ``__setstate__`` now ignore the ``__weakref__`` attribute.

`311 &lt;https://github.com/python-attrs/attrs/issues/311&gt;`_,
`326 &lt;https://github.com/python-attrs/attrs/issues/326&gt;`_
- Setting the cell type is now completely best effort.
This fixes ``attrs`` on Jython.

We cannot make any guarantees regarding Jython though, because our test suite cannot run due to dependency incompatabilities.

`321 &lt;https://github.com/python-attrs/attrs/issues/321&gt;`_,
`334 &lt;https://github.com/python-attrs/attrs/issues/334&gt;`_
- If ``attr.s`` is passed a *these* argument, it will no longer attempt to remove attributes with the same name from the class body.

`322 &lt;https://github.com/python-attrs/attrs/issues/322&gt;`_,
`323 &lt;https://github.com/python-attrs/attrs/issues/323&gt;`_
- The hash of ``attr.NOTHING`` is now vegan and faster on 32bit Python builds.

`331 &lt;https://github.com/python-attrs/attrs/issues/331&gt;`_,
`332 &lt;https://github.com/python-attrs/attrs/issues/332&gt;`_
- The overhead of instantiating frozen dict classes is virtually eliminated.
`336 &lt;https://github.com/python-attrs/attrs/issues/336&gt;`_
- Generated ``__init__`` methods now have an ``__annotations__`` attribute derived from the types of the fields.

`363 &lt;https://github.com/python-attrs/attrs/issues/363&gt;`_
- We have restructured the documentation a bit to account for ``attrs``&#39; growth in scope.
Instead of putting everything into the `examples &lt;https://www.attrs.org/en/stable/examples.html&gt;`_ page, we have started to extract narrative chapters.

So far, we&#39;ve added chapters on `initialization &lt;https://www.attrs.org/en/stable/init.html&gt;`_ and `hashing &lt;https://www.attrs.org/en/stable/hashing.html&gt;`_.

Expect more to come!

`369 &lt;https://github.com/python-attrs/attrs/issues/369&gt;`_,
`370 &lt;https://github.com/python-attrs/attrs/issues/370&gt;`_


----

17.4.0

-------------------

Backward-incompatible Changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- The traversal of MROs when using multiple inheritance was backward:
If you defined a class ``C`` that subclasses ``A`` and ``B`` like ``C(A, B)``, ``attrs`` would have collected the attributes from ``B`` *before* those of ``A``.

This is now fixed and means that in classes that employ multiple inheritance, the output of ``__repr__`` and the order of positional arguments in ``__init__`` changes.
Because of the nature of this bug, a proper deprecation cycle was unfortunately impossible.

Generally speaking, it&#39;s advisable to prefer ``kwargs``-based initialization anyways – *especially* if you employ multiple inheritance and diamond-shaped hierarchies.

`298 &lt;https://github.com/python-attrs/attrs/issues/298&gt;`_,
`299 &lt;https://github.com/python-attrs/attrs/issues/299&gt;`_,
`304 &lt;https://github.com/python-attrs/attrs/issues/304&gt;`_
- The ``__repr__`` set by ``attrs`` no longer produces an ``AttributeError`` when the instance is missing some of the specified attributes (either through deleting or after using ``init=False`` on some attributes).

This can break code that relied on ``repr(attr_cls_instance)`` raising ``AttributeError`` to check if any ``attrs``-specified members were unset.

If you were using this, you can implement a custom method for checking this::

   def has_unset_members(self):
       for field in attr.fields(type(self)):
           try:
               getattr(self, field.name)
           except AttributeError:
               return True
       return False

`308 &lt;https://github.com/python-attrs/attrs/issues/308&gt;`_


Deprecations
^^^^^^^^^^^^

- The ``attr.ib(convert=callable)`` option is now deprecated in favor of ``attr.ib(converter=callable)``.

This is done to achieve consistency with other noun-based arguments like *validator*.

*convert* will keep working until at least January 2019 while raising a ``DeprecationWarning``.

`307 &lt;https://github.com/python-attrs/attrs/issues/307&gt;`_


Changes
^^^^^^^

- Generated ``__hash__`` methods now hash the class type along with the attribute values.
Until now the hashes of two classes with the same values were identical which was a bug.

The generated method is also *much* faster now.

`261 &lt;https://github.com/python-attrs/attrs/issues/261&gt;`_,
`295 &lt;https://github.com/python-attrs/attrs/issues/295&gt;`_,
`296 &lt;https://github.com/python-attrs/attrs/issues/296&gt;`_
- ``attr.ib``\ ’s *metadata* argument now defaults to a unique empty ``dict`` instance instead of sharing a common empty ``dict`` for all.
The singleton empty ``dict`` is still enforced.

`280 &lt;https://github.com/python-attrs/attrs/issues/280&gt;`_
- ``ctypes`` is optional now however if it&#39;s missing, a bare ``super()`` will not work in slotted classes.
This should only happen in special environments like Google App Engine.

`284 &lt;https://github.com/python-attrs/attrs/issues/284&gt;`_,
`286 &lt;https://github.com/python-attrs/attrs/issues/286&gt;`_
- The attribute redefinition feature introduced in 17.3.0 now takes into account if an attribute is redefined via multiple inheritance.
In that case, the definition that is closer to the base of the class hierarchy wins.

`285 &lt;https://github.com/python-attrs/attrs/issues/285&gt;`_,
`287 &lt;https://github.com/python-attrs/attrs/issues/287&gt;`_
- Subclasses of ``auto_attribs=True`` can be empty now.

`291 &lt;https://github.com/python-attrs/attrs/issues/291&gt;`_,
`292 &lt;https://github.com/python-attrs/attrs/issues/292&gt;`_
- Equality tests are *much* faster now.

`306 &lt;https://github.com/python-attrs/attrs/issues/306&gt;`_
- All generated methods now have correct ``__module__``, ``__name__``, and (on Python 3) ``__qualname__`` attributes.

`309 &lt;https://github.com/python-attrs/attrs/issues/309&gt;`_


----

17.3.0

-------------------

Backward-incompatible Changes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Attributes are no longer defined on the class body.

This means that if you define a class ``C`` with an attribute ``x``, the class will *not* have an attribute ``x`` for introspection.
Instead of ``C.x``, use ``attr.fields(C).x`` or look at ``C.__attrs_attrs__``.
The old behavior has been deprecated since version 16.1.
(`253 &lt;https://github.com/python-attrs/attrs/issues/253&gt;`_)


Changes
^^^^^^^

- ``super()`` and ``__class__`` now work with slotted classes on Python 3.
(`102 &lt;https://github.com/python-attrs/attrs/issues/102&gt;`_, `226 &lt;https://github.com/python-attrs/attrs/issues/226&gt;`_, `269 &lt;https://github.com/python-attrs/attrs/issues/269&gt;`_, `270 &lt;https://github.com/python-attrs/attrs/issues/270&gt;`_, `272 &lt;https://github.com/python-attrs/attrs/issues/272&gt;`_)
- Added *type* argument to ``attr.ib()`` and corresponding ``type`` attribute to ``attr.Attribute``.

This change paves the way for automatic type checking and serialization (though as of this release ``attrs`` does not make use of it).
In Python 3.6 or higher, the value of ``attr.Attribute.type`` can alternately be set using variable type annotations
(see `PEP 526 &lt;https://www.python.org/dev/peps/pep-0526/&gt;`_).
(`151 &lt;https://github.com/python-attrs/attrs/issues/151&gt;`_, `214 &lt;https://github.com/python-attrs/attrs/issues/214&gt;`_, `215 &lt;https://github.com/python-attrs/attrs/issues/215&gt;`_, `239 &lt;https://github.com/python-attrs/attrs/issues/239&gt;`_)
- The combination of ``str=True`` and ``slots=True`` now works on Python 2.
(`198 &lt;https://github.com/python-attrs/attrs/issues/198&gt;`_)
- ``attr.Factory`` is hashable again.
(`204 &lt;https://github.com/python-attrs/attrs/issues/204&gt;`_)
- Subclasses now can overwrite attribute definitions of their base classes.

That means that you can -- for example -- change the default value for an attribute by redefining it.
(`221 &lt;https://github.com/python-attrs/attrs/issues/221&gt;`_, `229 &lt;https://github.com/python-attrs/attrs/issues/229&gt;`_)
- Added new option *auto_attribs* to ``attr.s`` that allows to collect annotated fields without setting them to ``attr.ib()``.

Setting a field to an ``attr.ib()`` is still possible to supply options like validators.
Setting it to any other value is treated like it was passed as ``attr.ib(default=value)`` -- passing an instance of ``attr.Factory`` also works as expected.
(`262 &lt;https://github.com/python-attrs/attrs/issues/262&gt;`_, `277 &lt;https://github.com/python-attrs/attrs/issues/277&gt;`_)
- Instances of classes created using ``attr.make_class()`` can now be pickled.
(`282 &lt;https://github.com/python-attrs/attrs/issues/282&gt;`_)


----

17.2.0

-------------------


Changes:
^^^^^^^^

- Validators are hashable again.
Note that validators may become frozen in the future, pending availability of no-overhead frozen classes.
`192 &lt;https://github.com/python-attrs/attrs/issues/192&gt;`_


----

17.1.0

-------------------

To encourage more participation, the project has also been moved into a `dedicated GitHub organization &lt;https://github.com/python-attrs/&gt;`_ and everyone is most welcome to join!

``attrs`` also has a logo now!

.. image:: https://www.attrs.org/en/latest/_static/attrs_logo.png
:alt: attrs logo


Backward-incompatible Changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- ``attrs`` will set the ``__hash__()`` method to ``None`` by default now.
The way hashes were handled before was in conflict with `Python&#39;s specification &lt;https://docs.python.org/3/reference/datamodel.htmlobject.__hash__&gt;`_.
This *may* break some software although this breakage is most likely just surfacing of latent bugs.
You can always make ``attrs`` create the ``__hash__()`` method using ``attr.s(hash=True)``.
See `136`_ for the rationale of this change.

.. warning::

 Please *do not* upgrade blindly and *do* test your software!
 *Especially* if you use instances as dict keys or put them into sets!

- Correspondingly, ``attr.ib``&#39;s *hash* argument is ``None`` by default too and mirrors the *cmp* argument as it should.


Deprecations:
^^^^^^^^^^^^^

- ``attr.assoc()`` is now deprecated in favor of ``attr.evolve()`` and will stop working in 2018.


Changes:
^^^^^^^^

- Fix default hashing behavior.
Now *hash* mirrors the value of *cmp* and classes are unhashable by default.
`136`_
`142 &lt;https://github.com/python-attrs/attrs/issues/142&gt;`_
- Added ``attr.evolve()`` that, given an instance of an ``attrs`` class and field changes as keyword arguments, will instantiate a copy of the given instance with the changes applied.
``evolve()`` replaces ``assoc()``, which is now deprecated.
``evolve()`` is significantly faster than ``assoc()``, and requires the class have an initializer that can take the field values as keyword arguments (like ``attrs`` itself can generate).
`116 &lt;https://github.com/python-attrs/attrs/issues/116&gt;`_
`124 &lt;https://github.com/python-attrs/attrs/pull/124&gt;`_
`135 &lt;https://github.com/python-attrs/attrs/pull/135&gt;`_
- ``FrozenInstanceError`` is now raised when trying to delete an attribute from a frozen class.
`118 &lt;https://github.com/python-attrs/attrs/pull/118&gt;`_
- Frozen-ness of classes is now inherited.
`128 &lt;https://github.com/python-attrs/attrs/pull/128&gt;`_
- ``__attrs_post_init__()`` is now run if validation is disabled.
`130 &lt;https://github.com/python-attrs/attrs/pull/130&gt;`_
- Added ``attr.validators.in_(options)`` that, given the allowed ``options``, checks whether the attribute value is in it.
This can be used to check constants, enums, mappings, etc.
`181 &lt;https://github.com/python-attrs/attrs/pull/181&gt;`_
- Added ``attr.validators.and_()`` that composes multiple validators into one.
`161 &lt;https://github.com/python-attrs/attrs/issues/161&gt;`_
- For convenience, the *validator* argument of ``attr.s`` now can take a list of validators that are wrapped using ``and_()``.
`138 &lt;https://github.com/python-attrs/attrs/issues/138&gt;`_
- Accordingly, ``attr.validators.optional()`` now can take a list of validators too.
`161 &lt;https://github.com/python-attrs/attrs/issues/161&gt;`_
- Validators can now be defined conveniently inline by using the attribute as a decorator.
Check out the `validator examples &lt;http://www.attrs.org/en/stable/init.htmldecorator&gt;`_ to see it in action!
`143 &lt;https://github.com/python-attrs/attrs/issues/143&gt;`_
- ``attr.Factory()`` now has a *takes_self* argument that makes the initializer to pass the partially initialized instance into the factory.
In other words you can define attribute defaults based on other attributes.
`165`_
`189 &lt;https://github.com/python-attrs/attrs/issues/189&gt;`_
- Default factories can now also be defined inline using decorators.
They are *always* passed the partially initialized instance.
`165`_
- Conversion can now be made optional using ``attr.converters.optional()``.
`105 &lt;https://github.com/python-attrs/attrs/issues/105&gt;`_
`173 &lt;https://github.com/python-attrs/attrs/pull/173&gt;`_
- ``attr.make_class()`` now accepts the keyword argument ``bases`` which allows for subclassing.
`152 &lt;https://github.com/python-attrs/attrs/pull/152&gt;`_
- Metaclasses are now preserved with ``slots=True``.
`155 &lt;https://github.com/python-attrs/attrs/pull/155&gt;`_

.. _`136`: https://github.com/python-attrs/attrs/issues/136
.. _`165`: https://github.com/python-attrs/attrs/issues/165


----

16.3.0

-------------------

Changes:
^^^^^^^^

- Attributes now can have user-defined metadata which greatly improves ``attrs``&#39;s extensibility.
`96 &lt;https://github.com/python-attrs/attrs/pull/96&gt;`_
- Allow for a ``__attrs_post_init__()`` method that -- if defined -- will get called at the end of the ``attrs``-generated ``__init__()`` method.
`111 &lt;https://github.com/python-attrs/attrs/pull/111&gt;`_
- Added ``attr.s(str=True)`` that will optionally create a ``__str__()`` method that is identical to ``__repr__()``.
This is mainly useful with ``Exception``\ s and other classes that rely on a useful ``__str__()`` implementation but overwrite the default one through a poor own one.
Default Python class behavior is to use ``__repr__()`` as ``__str__()`` anyways.

If you tried using ``attrs`` with ``Exception``\ s and were puzzled by the tracebacks: this option is for you.
- ``__name__`` is no longer overwritten with ``__qualname__`` for ``attr.s(slots=True)`` classes.
`99 &lt;https://github.com/python-attrs/attrs/issues/99&gt;`_


----

16.2.0

-------------------

Changes:
^^^^^^^^

- Added ``attr.astuple()`` that -- similarly to ``attr.asdict()`` -- returns the instance as a tuple.
`77 &lt;https://github.com/python-attrs/attrs/issues/77&gt;`_
- Converters now work with frozen classes.
`76 &lt;https://github.com/python-attrs/attrs/issues/76&gt;`_
- Instantiation of ``attrs`` classes with converters is now significantly faster.
`80 &lt;https://github.com/python-attrs/attrs/pull/80&gt;`_
- Pickling now works with slotted classes.
`81 &lt;https://github.com/python-attrs/attrs/issues/81&gt;`_
- ``attr.assoc()`` now works with slotted classes.
`84 &lt;https://github.com/python-attrs/attrs/issues/84&gt;`_
- The tuple returned by ``attr.fields()`` now also allows to access the ``Attribute`` instances by name.
Yes, we&#39;ve subclassed ``tuple`` so you don&#39;t have to!
Therefore ``attr.fields(C).x`` is equivalent to the deprecated ``C.x`` and works with slotted classes.
`88 &lt;https://github.com/python-attrs/attrs/issues/88&gt;`_


----

16.1.0

-------------------

Backward-incompatible Changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- All instances where function arguments were called ``cl`` have been changed to the more Pythonic ``cls``.
Since it was always the first argument, it&#39;s doubtful anyone ever called those function with in the keyword form.
If so, sorry for any breakage but there&#39;s no practical deprecation path to solve this ugly wart.


Deprecations:
^^^^^^^^^^^^^

- Accessing ``Attribute`` instances on class objects is now deprecated and will stop working in 2017.
If you need introspection please use the ``__attrs_attrs__`` attribute or the ``attr.fields()`` function that carry them too.
In the future, the attributes that are defined on the class body and are usually overwritten in your ``__init__`` method are simply removed after ``attr.s`` has been applied.

This will remove the confusing error message if you write your own ``__init__`` and forget to initialize some attribute.
Instead you will get a straightforward ``AttributeError``.
In other words: decorated classes will work more like plain Python classes which was always ``attrs``&#39;s goal.
- The serious business aliases ``attr.attributes`` and ``attr.attr`` have been deprecated in favor of ``attr.attrs`` and ``attr.attrib`` which are much more consistent and frankly obvious in hindsight.
They will be purged from documentation immediately but there are no plans to actually remove them.


Changes:
^^^^^^^^

- ``attr.asdict()``\ &#39;s ``dict_factory`` arguments is now propagated on recursion.
`45 &lt;https://github.com/python-attrs/attrs/issues/45&gt;`_
- ``attr.asdict()``, ``attr.has()`` and ``attr.fields()`` are significantly faster.
`48 &lt;https://github.com/python-attrs/attrs/issues/48&gt;`_
`51 &lt;https://github.com/python-attrs/attrs/issues/51&gt;`_
- Add ``attr.attrs`` and ``attr.attrib`` as a more consistent aliases for ``attr.s`` and ``attr.ib``.
- Add *frozen* option to ``attr.s`` that will make instances best-effort immutable.
`60 &lt;https://github.com/python-attrs/attrs/issues/60&gt;`_
- ``attr.asdict()`` now takes ``retain_collection_types`` as an argument.
If ``True``, it does not convert attributes of type ``tuple`` or ``set`` to ``list``.
`69 &lt;https://github.com/python-attrs/attrs/issues/69&gt;`_


----

16.0.0

-------------------

Backward-incompatible Changes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

- Python 3.3 and 2.6 are no longer supported.
They may work by chance but any effort to keep them working has ceased.

The last Python 2.6 release was on October 29, 2013 and is no longer supported by the CPython core team.
Major Python packages like Django and Twisted dropped Python 2.6 a while ago already.

Python 3.3 never had a significant user base and wasn&#39;t part of any distribution&#39;s LTS release.

Changes:
^^^^^^^^

- ``__slots__`` have arrived!
Classes now can automatically be `slotted &lt;https://docs.python.org/3/reference/datamodel.htmlslots&gt;`_-style (and save your precious memory) just by passing ``slots=True``.
`35 &lt;https://github.com/python-attrs/attrs/issues/35&gt;`_
- Allow the case of initializing attributes that are set to ``init=False``.
This allows for clean initializer parameter lists while being able to initialize attributes to default values.
`32 &lt;https://github.com/python-attrs/attrs/issues/32&gt;`_
- ``attr.asdict()`` can now produce arbitrary mappings instead of Python ``dict``\ s when provided with a ``dict_factory`` argument.
`40 &lt;https://github.com/python-attrs/attrs/issues/40&gt;`_
- Multiple performance improvements.


----

15.2.0

-------------------

Changes:
^^^^^^^^

- Added a ``convert`` argument to ``attr.ib``, which allows specifying a function to run on arguments.
This allows for simple type conversions, e.g. with ``attr.ib(convert=int)``.
`26 &lt;https://github.com/python-attrs/attrs/issues/26&gt;`_
- Speed up object creation when attribute validators are used.
`28 &lt;https://github.com/python-attrs/attrs/issues/28&gt;`_


----

15.1.0

-------------------

Changes:
^^^^^^^^

- Added ``attr.validators.optional()`` that wraps other validators allowing attributes to be ``None``.
`16 &lt;https://github.com/python-attrs/attrs/issues/16&gt;`_
- Multi-level inheritance now works.
`24 &lt;https://github.com/python-attrs/attrs/issues/24&gt;`_
- ``__repr__()`` now works with non-redecorated subclasses.
`20 &lt;https://github.com/python-attrs/attrs/issues/20&gt;`_


----

15.0.0

-------------------

Changes:
^^^^^^^^

Initial release.

Links

PyPI: https://pypi.org/project/attrs
Changelog: https://pyup.io/changelogs/attrs/
Homepage: https://www.attrs.org/

Update certifi from 2019.3.9 to 2019.9.11.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/certifi
Homepage: https://certifi.io/

Update colored from 1.3.93 to 1.4.0.

The bot wasn't able to find a changelog for this release. Got an idea?

Links

PyPI: https://pypi.org/project/colored
Repo: https://gitlab.com/dslackw/colored

Update coverage from 4.5.3 to 4.5.4.

Changelog

4.5.4

---------------------------

- Multiprocessing support in Python 3.8 was broken, but is now fixed.  Closes
`issue 828`_.

.. _issue 828: https://github.com/nedbat/coveragepy/issues/828


.. _changes_453:

4.5.3

---------------------------

- Only packaging metadata changes.


.. _changes_452:

4.5.2

----------------------------

- Namespace packages are supported on Python 3.7, where they used to cause
TypeErrors about path being None. Fixes `issue 700`_.

- Python 3.8 (as of today!) passes all tests.  Fixes `issue 707`_ and
`issue 714`_.

- Development moved from `Bitbucket`_ to `GitHub`_.

.. _issue 700: https://github.com/nedbat/coveragepy/issues/700
.. _issue 707: https://github.com/nedbat/coveragepy/issues/707
.. _issue 714: https://github.com/nedbat/coveragepy/issues/714

.. _Bitbucket: https://bitbucket.org/ned/coveragepy
.. _GitHub: https://github.com/nedbat/coveragepy


.. _changes_451:

4.5.1

----------------------------

- Now that 4.5 properly separated the ``[run] omit`` and ``[report] omit``
settings, an old bug has become apparent.  If you specified a package name
for ``[run] source``, then omit patterns weren&#39;t matched inside that package.
This bug (`issue 638`_) is now fixed.

- On Python 3.7, reporting about a decorated function with no body other than a
docstring would crash coverage.py with an IndexError (`issue 640`_).  This is
now fixed.

- Configurer plugins are now reported in the output of ``--debug=sys``.

.. _issue 638: https://bitbucket.org/ned/coveragepy/issues/638/run-omit-is-ignored-since-45
.. _issue 640: https://bitbucket.org/ned/coveragepy/issues/640/indexerror-reporting-on-an-empty-decorated


.. _changes_45:

4.5

--------------------------

- A new kind of plugin is supported: configurators are invoked at start-up to
allow more complex configuration than the .coveragerc file can easily do.
See :ref:`api_plugin` for details.  This solves the complex configuration
problem described in `issue 563`_.

- The ``fail_under`` option can now be a float.  Note that you must specify the
``[report] precision`` configuration option for the fractional part to be
used.  Thanks to Lars Hupfeldt Nielsen for help with the implementation.
Fixes `issue 631`_.

- The ``include`` and ``omit`` options can be specified for both the ``[run]``
and ``[report]`` phases of execution.  4.4.2 introduced some incorrect
interactions between those phases, where the options for one were confused
for the other.  This is now corrected, fixing `issue 621`_ and `issue 622`_.
Thanks to Daniel Hahler for seeing more clearly than I could.

- The ``coverage combine`` command used to always overwrite the data file, even
when no data had been read from apparently combinable files.  Now, an error
is raised if we thought there were files to combine, but in fact none of them
could be used.  Fixes `issue 629`_.

- The ``coverage combine`` command could get confused about path separators
when combining data collected on Windows with data collected on Linux, as
described in `issue 618`_.  This is now fixed: the result path always uses
the path separator specified in the ``[paths]`` result.

- On Windows, the HTML report could fail when source trees are deeply nested,
due to attempting to create HTML filenames longer than the 250-character
maximum.  Now filenames will never get much larger than 200 characters,
fixing `issue 627`_.  Thanks to Alex Sandro for helping with the fix.

.. _issue 563: https://bitbucket.org/ned/coveragepy/issues/563/platform-specific-configuration
.. _issue 618: https://bitbucket.org/ned/coveragepy/issues/618/problem-when-combining-windows-generated
.. _issue 621: https://bitbucket.org/ned/coveragepy/issues/621/include-ignored-warning-when-using
.. _issue 622: https://bitbucket.org/ned/coveragepy/issues/622/report-omit-overwrites-run-omit
.. _issue 627: https://bitbucket.org/ned/coveragepy/issues/627/failure-generating-html-reports-when-the
.. _issue 629: https://bitbucket.org/ned/coveragepy/issues/629/multiple-use-of-combine-leads-to-empty
.. _issue 631: https://bitbucket.org/ned/coveragepy/issues/631/precise-coverage-percentage-value


.. _changes_442:

4.4.2

----------------------------

- Support for Python 3.7.  In some cases, class and module docstrings are no
longer counted in statement totals, which could slightly change your total
results.

- Specifying both ``--source`` and ``--include`` no longer silently ignores the
include setting, instead it displays a warning. Thanks, Loïc Dachary.  Closes
`issue 265`_ and `issue 101`_.

- Fixed a race condition when saving data and multiple threads are tracing
(`issue 581`_). It could produce a &quot;dictionary changed size during iteration&quot;
RuntimeError.  I believe this mostly but not entirely fixes the race
condition.  A true fix would likely be too expensive.  Thanks, Peter Baughman
for the debugging, and Olivier Grisel for the fix with tests.

- Configuration values which are file paths will now apply tilde-expansion,
closing `issue 589`_.

- Now secondary config files like tox.ini and setup.cfg can be specified
explicitly, and prefixed sections like `[coverage:run]` will be read. Fixes
`issue 588`_.

- Be more flexible about the command name displayed by help, fixing
`issue 600`_. Thanks, Ben Finney.

.. _issue 101: https://bitbucket.org/ned/coveragepy/issues/101/settings-under-report-affect-running
.. _issue 581: https://bitbucket.org/ned/coveragepy/issues/581/race-condition-when-saving-data-under
.. _issue 588: https://bitbucket.org/ned/coveragepy/issues/588/using-rcfile-path-to-toxini-uses-run
.. _issue 589: https://bitbucket.org/ned/coveragepy/issues/589/allow-expansion-in-coveragerc
.. _issue 600: https://bitbucket.org/ned/coveragepy/issues/600/get-program-name-from-command-line-when


.. _changes_441:

4.4.1

----------------------------

- No code changes: just corrected packaging for Python 2.7 Linux wheels.


.. _changes_44:

4.4

--------------------------

- Reports could produce the wrong file names for packages, reporting ``pkg.py``
instead of the correct ``pkg/__init__.py``.  This is now fixed.  Thanks, Dirk
Thomas.

- XML reports could produce ``&lt;source&gt;`` and ``&lt;class&gt;`` lines that together
didn&#39;t specify a valid source file path.  This is now fixed. (`issue 526`_)

- Namespace packages are no longer warned as having no code. (`issue 572`_)

- Code that uses ``sys.settrace(sys.gettrace())`` in a file that wasn&#39;t being
coverage-measured would prevent correct coverage measurement in following
code. An example of this was running doctests programmatically. This is now
fixed. (`issue 575`_)

- Errors printed by the ``coverage`` command now go to stderr instead of
stdout.

- Running ``coverage xml`` in a directory named with non-ASCII characters would
fail under Python 2. This is now fixed. (`issue 573`_)

.. _issue 526: https://bitbucket.org/ned/coveragepy/issues/526/generated-xml-invalid-paths-for-cobertura
.. _issue 572: https://bitbucket.org/ned/coveragepy/issues/572/no-python-source-warning-for-namespace
.. _issue 573: https://bitbucket.org/ned/coveragepy/issues/573/cant-generate-xml-report-if-some-source
.. _issue 575: https://bitbucket.org/ned/coveragepy/issues/575/running-doctest-prevents-complete-coverage

4.4b1

----------------------------

- Some warnings can now be individually disabled.  Warnings that can be
disabled have a short name appended.  The ``[run] disable_warnings`` setting
takes a list of these warning names to disable. Closes both `issue 96`_ and
`issue 355`_.

- The XML report now includes attributes from version 4 of the Cobertura XML
format, fixing `issue 570`_.

- In previous versions, calling a method that used collected data would prevent
further collection.  For example, `save()`, `report()`, `html_report()`, and
others would all stop collection.  An explicit `start()` was needed to get it
going again.  This is no longer true.  Now you can use the collected data and
also continue measurement. Both `issue 79`_ and `issue 448`_ described this
problem, and have been fixed.

- Plugins can now find unexecuted files if they choose, by implementing the
`find_executable_files` method.  Thanks, Emil Madsen.

- Minimal IronPython support. You should be able to run IronPython programs
under ``coverage run``, though you will still have to do the reporting phase
with CPython.

- Coverage.py has long had a special hack to support CPython&#39;s need to measure
the coverage of the standard library tests. This code was not installed by
kitted versions of coverage.py.  Now it is.

.. _issue 79: https://bitbucket.org/ned/coveragepy/issues/79/save-prevents-harvesting-on-stop
.. _issue 96: https://bitbucket.org/ned/coveragepy/issues/96/unhelpful-warnings-produced-when-using
.. _issue 355: https://bitbucket.org/ned/coveragepy/issues/355/warnings-should-be-suppressable
.. _issue 448: https://bitbucket.org/ned/coveragepy/issues/448/save-and-html_report-prevent-further
.. _issue 570: https://bitbucket.org/ned/coveragepy/issues/570/cobertura-coverage-04dtd-support


.. _changes_434:

4.3.4

----------------------------

- Fixing 2.6 in version 4.3.3 broke other things, because the too-tricky
exception wasn&#39;t properly derived from Exception, described in `issue 556`_.
A newb mistake; it hasn&#39;t been a good few days.

.. _issue 556: https://bitbucket.org/ned/coveragepy/issues/556/43-fails-if-there-are-html-files-in-the


.. _changes_433:

4.3.3

----------------------------

- Python 2.6 support was broken due to a testing exception imported for the
benefit of the coverage.py test suite.  Properly conditionalizing it fixed
`issue 554`_ so that Python 2.6 works again.

.. _issue 554: https://bitbucket.org/ned/coveragepy/issues/554/traceback-on-python-26-starting-with-432


.. _changes_432:

4.3.2

----------------------------

- Using the ``--skip-covered`` option on an HTML report with 100% coverage
would cause a &quot;No data to report&quot; error, as reported in `issue 549`_. This is
now fixed; thanks, Loïc Dachary.

- If-statements can be optimized away during compilation, for example, `if 0:`
or `if __debug__:`.  Coverage.py had problems properly understanding these
statements which existed in the source, but not in the compiled bytecode.
This problem, reported in `issue 522`_, is now fixed.

- If you specified ``--source`` as a directory, then coverage.py would look for
importable Python files in that directory, and could identify ones that had
never been executed at all.  But if you specified it as a package name, that
detection wasn&#39;t performed.  Now it is, closing `issue 426`_. Thanks to Loïc
Dachary for the fix.

- If you started and stopped coverage measurement thousands of times in your
process, you could crash Python with a &quot;Fatal Python error: deallocating
None&quot; error.  This is now fixed.  Thanks to Alex Groce for the bug report.

- On PyPy, measuring coverage in subprocesses could produce a warning: &quot;Trace
function changed, measurement is likely wrong: None&quot;.  This was spurious, and
has been suppressed.

- Previously, coverage.py couldn&#39;t start on Jython, due to that implementation
missing the multiprocessing module (`issue 551`_). This problem has now been
fixed. Also, `issue 322`_ about not being able to invoke coverage
conveniently, seems much better: ``jython -m coverage run myprog.py`` works
properly.

- Let&#39;s say you ran the HTML report over and over again in the same output
directory, with ``--skip-covered``. And imagine due to your heroic
test-writing efforts, a file just achieved the goal of 100% coverage. With
coverage.py 4.3, the old HTML file with the less-than-100% coverage would be
left behind.  This file is now properly deleted.

.. _issue 322: https://bitbucket.org/ned/coveragepy/issues/322/cannot-use-coverage-with-jython
.. _issue 426: https://bitbucket.org/ned/coveragepy/issues/426/difference-between-coverage-results-with
.. _issue 522: https://bitbucket.org/ned/coveragepy/issues/522/incorrect-branch-reporting
.. _issue 549: https://bitbucket.org/ned/coveragepy/issues/549/skip-covered-with-100-coverage-throws-a-no
.. _issue 551: https://bitbucket.org/ned/coveragepy/issues/551/coveragepy-cannot-be-imported-in-jython27


.. _changes_431:

4.3.1

----------------------------

- Some environments couldn&#39;t install 4.3, as described in `issue 540`_. This is
now fixed.

- The check for conflicting ``--source`` and ``--include`` was too simple in a
few different ways, breaking a few perfectly reasonable use cases, described
in `issue 541`_.  The check has been reverted while we re-think the fix for
`issue 265`_.

.. _issue 540: https://bitbucket.org/ned/coveragepy/issues/540/cant-install-coverage-v43-into-under
.. _issue 541: https://bitbucket.org/ned/coveragepy/issues/541/coverage-43-breaks-nosetest-with-coverage


.. _changes_43:

4.3

--------------------------

Special thanks to **Loïc Dachary**, who took an extraordinary interest in
coverage.py and contributed a number of improvements in this release.

- Subprocesses that are measured with `automatic subprocess measurement`_ used
to read in any pre-existing data file.  This meant data would be incorrectly
carried forward from run to run.  Now those files are not read, so each
subprocess only writes its own data. Fixes `issue 510`_.

- The ``coverage combine`` command will now fail if there are no data files to
combine. The combine changes in 4.2 meant that multiple combines could lose
data, leaving you with an empty .coverage data file. Fixes
`issue 525`_, `issue 412`_, `issue 516`_, and probably `issue 511`_.

- Coverage.py wouldn&#39;t execute `sys.excepthook`_ when an exception happened in
your program.  Now it does, thanks to Andrew Hoos.  Closes `issue 535`_.

- Branch coverage fixes:

- Branch coverage could misunderstand a finally clause on a try block that
 never continued on to the following statement, as described in `issue
 493`_.  This is now fixed. Thanks to Joe Doherty for the report and Loïc
 Dachary for the fix.

- A while loop with a constant condition (while True) and a continue
 statement would be mis-analyzed, as described in `issue 496`_. This is now
 fixed, thanks to a bug report by Eli Skeggs and a fix by Loïc Dachary.

- While loops with constant conditions that were never executed could result
 in a non-zero coverage report.  Artem Dayneko reported this in `issue
 502`_, and Loïc Dachary provided the fix.

- The HTML report now supports a ``--skip-covered`` option like the other
reporting commands.  Thanks, Loïc Dachary for the implementation, closing
`issue 433`_.

- Options can now be read from a tox.ini file, if any. Like setup.cfg, sections
are prefixed with &quot;coverage:&quot;, so ``[run]`` options will be read from the
``[coverage:run]`` section of tox.ini. Implements part of `issue 519`_.
Thanks, Stephen Finucane.

- Specifying both ``--source`` and ``--include`` no longer silently ignores the
include setting, instead it fails with a message. Thanks, Nathan Land and
Loïc Dachary. Closes `issue 265`_.

- The ``Coverage.combine`` method has a new parameter, ``strict=False``, to
support failing if there are no data files to combine.

- When forking subprocesses, the coverage data files would have the same random
number appended to the file name. This didn&#39;t cause problems, because the
file names had the process id also, making collisions (nearly) impossible.
But it was disconcerting.  This is now fixed.

- The text report now properly sizes headers when skipping some files, fixing
`issue 524`_. Thanks, Anthony Sottile and Loïc Dachary.

- Coverage.py can now search .pex files for source, just as it can .zip and
.egg.  Thanks, Peter Ebden.

- Data files are now about 15% smaller.

- Improvements in the ``[run] debug`` setting:

- The &quot;dataio&quot; debug setting now also logs when data files are deleted during
 combining or erasing.

- A new debug option, &quot;multiproc&quot;, for logging the behavior of
 ``concurrency=multiprocessing``.

- If you used the debug options &quot;config&quot; and &quot;callers&quot; together, you&#39;d get a
 call stack printed for every line in the multi-line config output. This is
 now fixed.

- Fixed an unusual bug involving multiple coding declarations affecting code
containing code in multi-line strings: `issue 529`_.

- Coverage.py will no longer be misled into thinking that a plain file is a
package when interpreting ``--source`` options.  Thanks, Cosimo Lupo.

- If you try to run a non-Python file with coverage.py, you will now get a more
useful error message. `Issue 514`_.

- The default pragma regex changed slightly, but this will only matter to you
if you are deranged and use mixed-case pragmas.

- Deal properly with non-ASCII file names in an ASCII-only world, `issue 533`_.

- Programs that set Unicode configuration values could cause UnicodeErrors when
generating HTML reports.  Pytest-cov is one example.  This is now fixed.

- Prevented deprecation warnings from configparser that happened in some
circumstances, closing `issue 530`_.

- Corrected the name of the jquery.ba-throttle-debounce.js library. Thanks,
Ben Finney.  Closes `issue 505`_.

- Testing against PyPy 5.6 and PyPy3 5.5.

- Switched to pytest from nose for running the coverage.py tests.

- Renamed AUTHORS.txt to CONTRIBUTORS.txt, since there are other ways to
contribute than by writing code. Also put the count of contributors into the
author string in setup.py, though this might be too cute.

.. _sys.excepthook: https://docs.python.org/3/library/sys.htmlsys.excepthook
.. _issue 265: https://bitbucket.org/ned/coveragepy/issues/265/when-using-source-include-is-silently
.. _issue 412: https://bitbucket.org/ned/coveragepy/issues/412/coverage-combine-should-error-if-no
.. _issue 433: https://bitbucket.org/ned/coveragepy/issues/433/coverage-html-does-not-suport-skip-covered
.. _issue 493: https://bitbucket.org/ned/coveragepy/issues/493/confusing-branching-failure
.. _issue 496: https://bitbucket.org/ned/coveragepy/issues/496/incorrect-coverage-with-branching-and
.. _issue 502: https://bitbucket.org/ned/coveragepy/issues/502/incorrect-coverage-report-with-cover
.. _issue 505: https://bitbucket.org/ned/coveragepy/issues/505/use-canonical-filename-for-debounce
.. _issue 514: https://bitbucket.org/ned/coveragepy/issues/514/path-to-problem-file-not-reported-when
.. _issue 510: https://bitbucket.org/ned/coveragepy/issues/510/erase-still-needed-in-42
.. _issue 511: https://bitbucket.org/ned/coveragepy/issues/511/version-42-coverage-combine-empties
.. _issue 516: https://bitbucket.org/ned/coveragepy/issues/516/running-coverage-combine-twice-deletes-all
.. _issue 519: https://bitbucket.org/ned/coveragepy/issues/519/coverage-run-sections-in-toxini-or-as
.. _issue 524: https://bitbucket.org/ned/coveragepy/issues/524/coverage-report-with-skip-covered-column
.. _issue 525: https://bitbucket.org/ned/coveragepy/issues/525/coverage-combine-when-not-in-parallel-mode
.. _issue 529: https://bitbucket.org/ned/coveragepy/issues/529/encoding-marker-may-only-appear-on-the
.. _issue 530: https://bitbucket.org/ned/coveragepy/issues/530/deprecationwarning-you-passed-a-bytestring
.. _issue 533: https://bitbucket.org/ned/coveragepy/issues/533/exception-on-unencodable-file-name
.. _issue 535: https://bitbucket.org/ned/coveragepy/issues/535/sysexcepthook-is-not-called


.. _changes_42:

4.2

--------------------------

- Since ``concurrency=multiprocessing`` uses subprocesses, options specified on
the coverage.py command line will not be communicated down to them.  Only
options in the configuration file will apply to the subprocesses.
Previously, the options didn&#39;t apply to the subprocesses, but there was no
indication.  Now it is an error to use ``--concurrency=multiprocessing`` and
other run-affecting options on the command line.  This prevents
failures like those reported in `issue 495`_.

- Filtering the HTML report is now faster, thanks to Ville Skyttä.

.. _issue 495: https://bitbucket.org/ned/coveragepy/issues/495/branch-and-concurrency-are-conflicting

4.2b1

----------------------------

Work from the PyCon 2016 Sprints!

- BACKWARD INCOMPATIBILITY: the ``coverage combine`` command now ignores an
existing ``.coverage`` data file.  It used to include that file in its
combining.  This caused confusing results, and extra tox &quot;clean&quot; steps.  If
you want the old behavior, use the new ``coverage combine --append`` option.

- The ``concurrency`` option can now take multiple values, to support programs
using multiprocessing and another library such as eventlet.  This is only
possible in the configuration file, not from the command line. The
configuration file is the only way for sub-processes to all run with the same
options.  Fixes `issue 484`_.  Thanks to Josh Williams for prototyping.

- Using a ``concurrency`` setting of ``multiprocessing`` now implies
``--parallel`` so that the main program is measured similarly to the
sub-processes.

- When using `automatic subprocess measurement`_, running coverage commands
would create spurious data files.  This is now fixed, thanks to diagnosis and
testing by Dan Riti.  Closes `issue 492`_.

- A new configuration option, ``report:sort``, controls what column of the
text report is used to sort the rows.  Thanks to Dan Wandschneider, this
closes `issue 199`_.

- The HTML report has a more-visible indicator for which column is being
sorted.  Closes `issue 298`_, thanks to Josh Williams.

- If the HTML report cannot find the source for a file, the message now
suggests using the ``-i`` flag to allow the report to continue. Closes
`issue 231`_, thanks, Nathan Land.

- When reports are ignoring errors, there&#39;s now a warning if a file cannot be
parsed, rather than being silently ignored.  Closes `issue 396`_. Thanks,
Matthew Boehm.

- A new option for ``coverage debug`` is available: ``coverage debug config``
shows the current configuration.  Closes `issue 454`_, thanks to Matthew
Boehm.

- Running coverage as a module (``python -m coverage``) no longer shows the
program name as ``__main__.py``.  Fixes `issue 478`_.  Thanks, Scott Belden.

- The `test_helpers` module has been moved into a separate pip-installable
package: `unittest-mixins`_.

.. _automatic subprocess measurement: https://coverage.readthedocs.io/en/latest/subprocess.html
.. _issue 199: https://bitbucket.org/ned/coveragepy/issues/199/add-a-way-to-sort-the-text-report
.. _issue 231: https://bitbucket.org/ned/coveragepy/issues/231/various-default-behavior-in-report-phase
.. _issue 298: https://bitbucket.org/ned/coveragepy/issues/298/show-in-html-report-that-the-columns-are
.. _issue 396: https://bitbucket.org/ned/coveragepy/issues/396/coverage-xml-shouldnt-bail-out-on-parse
.. _issue 454: https://bitbucket.org/ned/coveragepy/issues/454/coverage-debug-config-should-be
.. _issue 478: https://bitbucket.org/ned/coveragepy/issues/478/help-shows-silly-program-name-when-running
.. _issue 484: https://bitbucket.org/ned/coveragepy/issues/484/multiprocessing-greenlet-concurrency
.. _issue 492: https://bitbucket.org/ned/coveragepy/issues/492/subprocess-coverage-strange-detection-of
.. _unittest-mixins: https://pypi.org/project/unittest-mixins/


.. _changes_41:

4.1

--------------------------

- The internal attribute `Reporter.file_reporters` was removed in 4.1b3.  It
should have come has no surprise that there were third-party tools out there
using that attribute.  It has been restored, but with a deprecation warning.

4.1b3

----------------------------

- When running your program, execution can jump from an ``except X:`` line to
some other line when an exception other than ``X`` happens.  This jump is no
longer considered a branch when measuring branch coverage.

- When measuring branch coverage, ``yield`` statements that were never resumed
were incorrectly marked as missing, as reported in `issue 440`_.  This is now
fixed.

- During branch coverage of single-line callables like lambdas and generator
expressions, coverage.py can now distinguish between them never being called,
or being called but not completed.  Fixes `issue 90`_, `issue 460`_ and
`issue 475`_.

- The HTML report now has a map of the file along the rightmost edge of the
page, giving an overview of where the missed lines are.  Thanks, Dmitry
Shishov.

- The HTML report now uses different monospaced fonts, favoring Consolas over
Courier.  Along the way, `issue 472`_ about not properly handling one-space
indents was fixed.  The index page also has slightly different styling, to
try to make the clickable detail pages more apparent.

- Missing branches reported with ``coverage report -m`` will now say ``-&gt;exit``
for missed branches to the exit of a function, rather than a negative number.
Fixes `issue 469`_.

- ``coverage --help`` and ``coverage --version`` now mention which tracer is
installed, to help diagnose problems. The docs mention which features need
the C extension. (`issue 479`_)

- Officially support PyPy 5.1, which required no changes, just updates to the
docs.

- The `Coverage.report` function had two parameters with non-None defaults,
which have been changed.  `show_missing` used to default to True, but now
defaults to None.  If you had been calling `Coverage.report` without
specifying `show_missing`, you&#39;ll need to explicitly set it to True to keep
the same behavior.  `skip_covered` used to default to False. It is now None,
which doesn&#39;t change the behavior.  This fixes `issue 485`_.

- It&#39;s never been possible to pass a namespace module to one of the analysis
functions, but now at least we raise a more specific error message, rather
than getting confused. (`issue 456`_)

- The `coverage.process_startup` function now returns the `Coverage` instance
it creates, as suggested in `issue 481`_.

- Make a small tweak to how we compare threads, to avoid buggy custom
comparison code in thread classes. (`issue 245`_)

.. _issue 90: https://bitbucket.org/ned/coveragepy/issues/90/lambda-expression-confuses-branch
.. _issue 245: https://bitbucket.org/ned/coveragepy/issues/245/change-solution-for-issue-164
.. _issue 440: https://bitbucket.org/ned/coveragepy/issues/440/yielded-twisted-failure-marked-as-missed
.. _issue 456: https://bitbucket.org/ned/coveragepy/issues/456/coverage-breaks-with-implicit-namespaces
.. _issue 460: https://bitbucket.org/ned/coveragepy/issues/460/confusing-html-report-for-certain-partial
.. _issue 469: https://bitbucket.org/ned/coveragepy/issues/469/strange-1-line-number-in-branch-coverage
.. _issue 472: https://bitbucket.org/ned/coveragepy/issues/472/html-report-indents-incorrectly-for-one
.. _issue 475: https://bitbucket.org/ned/coveragepy/issues/475/generator-expression-is-marked-as-not
.. _issue 479: https://bitbucket.org/ned/coveragepy/issues/479/clarify-the-need-for-the-c-extension
.. _issue 481: https://bitbucket.org/ned/coveragepy/issues/481/asyncioprocesspoolexecutor-tracing-not
.. _issue 485: https://bitbucket.org/ned/coveragepy/issues/485/coveragereport-ignores-show_missing-and

4.1b2

----------------------------

- Problems with the new branch measurement in 4.1 beta 1 were fixed:

- Class docstrings were considered executable.  Now they no longer are.

- ``yield from`` and ``await`` were considered returns from functions, since
 they could transfer control to the caller.  This produced unhelpful
 &quot;missing branch&quot; reports in a number of circumstances.  Now they no longer
 are considered returns.

- In unusual situations, a missing branch to a negative number was reported.
 This has been fixed, closing `issue 466`_.

- The XML report now produces correct package names for modules found in
directories specified with ``source=``.  Fixes `issue 465`_.

- ``coverage report`` won&#39;t produce trailing whitespace.

.. _issue 465: https://bitbucket.org/ned/coveragepy/issues/465/coveragexml-produces-package-names-with-an
.. _issue 466: https://bitbucket.org/ned/coveragepy/issues/466/impossible-missed-branch-to-a-negative

4.1b1

----------------------------

- Branch analysis has been rewritten: it used to be based on bytecode, but now
uses AST analysis.  This has changed a number of things:

- More code paths are now considered runnable, especially in
 ``try``/``except`` structures.  This may mean that coverage.py will
 identify more code paths as uncovered.  This could either raise or lower
 your overall coverage number.

- Python 3.5&#39;s ``async`` and ``await`` keywords are properly supported,
 fixing `issue 434`_.

- Some long-standing branch coverage bugs were fixed:

 - `issue 129`_: functions with only a docstring for a body would
   incorrectly report a missing branch on the ``def`` line.

 - `issue 212`_: code in an ``except`` block could be incorrectly marked as
   a missing branch.

 - `issue 146`_: context managers (``with`` statements) in a loop or ``try``
   block could confuse the branch measurement, reporting incorrect partial
   branches.

 - `issue 422`_: in Python 3.5, an actual partial branch could be marked as
   complete.

- Pragmas to disable coverage measurement can now be used on decorator lines,
and they will apply to the entire function or class being decorated.  This
implements the feature requested in `issue 131`_.

- Multiprocessing support is now available on Windows.  Thanks, Rodrigue
Cloutier.

- Files with two encoding declarations are properly supported, fixing
`issue 453`_. Thanks, Max Linke.

- Non-ascii characters in regexes in the configuration file worked in 3.7, but
stopped working in 4.0.  Now they work again, closing `issue 455`_.

- Form-feed characters would prevent accurate determination of the beginning of
statements in the rest of the file.  This is now fixed, closing `issue 461`_.

.. _issue 129: https://bitbucket.org/ned/coveragepy/issues/129/misleading-branch-coverage-of-empty
.. _issue 131: https://bitbucket.org/ned/coveragepy/issues/131/pragma-on-a-decorator-line-should-affect
.. _issue 146: https://bitbucket.org/ned/coveragepy/issues/146/context-managers-confuse-branch-coverage
.. _issue 212: https://bitbucket.org/ned/coveragepy/issues/212/coverage-erroneously-reports-partial
.. _issue 422: https://bitbucket.org/ned/coveragepy/issues/422/python35-partial-branch-marked-as-fully
.. _issue 434: https://bitbucket.org/ned/coveragepy/issues/434/indexerror-in-python-35
.. _issue 453: https://bitbucket.org/ned/coveragepy/issues/453/source-code-encoding-can-only-be-specified
.. _issue 455: https://bitbucket.org/ned/coveragepy/issues/455/unusual-exclusions-stopped-working-in
.. _issue 461: https://bitbucket.org/ned/coveragepy/issues/461/multiline-asserts-need-too-many-pragma


.. _changes_403:

4.0.3

----------------------------

- Fixed a mysterious problem that manifested in different ways: sometimes
hanging the process (`issue 420`_), sometimes making database connections
fail (`issue 445`_).

- The XML report now has correct ``&lt;source&gt;`` elements when using a
``--source=`` option somewhere besides the current directory.  This fixes
`issue 439`_. Thanks, Arcady Ivanov.

- Fixed an unusual edge case of detecting source encodings, described in
`issue 443`_.

- Help messages that mention the command to use now properly use the actual
command name, which might be different than &quot;coverage&quot;.  Thanks to Ben
Finney, this closes `issue 438`_.

.. _issue 420: https://bitbucket.org/ned/covera

pyup-bot · 2020-02-01T15:09:33Z

Closing this in favor of #97

pyup-bot added 13 commits November 1, 2019 12:10

Pin attrs to latest version 19.3.0

6a30cef

Pin certifi to latest version 2019.9.11

ba7c7e9

Pin colored to latest version 1.4.0

7d9933e

Pin coverage to latest version 4.5.4

225c3d1

Pin more-itertools to latest version 7.2.0

441dfa5

Pin pip to latest version 19.3.1

ebfb254

Pin pytest to latest version 5.2.2

cbc614d

Pin pytest-cov to latest version 2.8.1

e89e096

Pin requests to latest version 2.22.0

8bd13d7

Pin setuptools to latest version 41.6.0

68f96ea

Pin urllib3 to latest version 1.25.6

15f5d8c

Pin wheel to latest version 0.33.6

306b510

Pin twine to latest version 2.0.0

1f65f45

pyup-bot mentioned this pull request Nov 1, 2019

Scheduled monthly dependency update for October #95

Closed

pyup-bot closed this Feb 1, 2020

andre-filho deleted the pyup-scheduled-update-2019-11-01 branch February 1, 2020 15:09

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Scheduled monthly dependency update for November #96

Scheduled monthly dependency update for November #96

Uh oh!

pyup-bot commented Nov 1, 2019

Uh oh!

pyup-bot commented Feb 1, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Scheduled monthly dependency update for November #96

Scheduled monthly dependency update for November #96

Uh oh!

Conversation

pyup-bot commented Nov 1, 2019

Update attrs from 19.1.0 to 19.3.0.

19.3.0

19.2.0

19.1.0

18.2.0

18.1.0

17.4.0

17.3.0

17.2.0

17.1.0

16.3.0

16.2.0

16.1.0

16.0.0

15.2.0

15.1.0

15.0.0

Update certifi from 2019.3.9 to 2019.9.11.

Update colored from 1.3.93 to 1.4.0.

Update coverage from 4.5.3 to 4.5.4.

4.5.4

4.5.3

4.5.2

4.5.1

4.5

4.4.2

4.4.1

4.4

4.4b1

4.3.4

4.3.3

4.3.2

4.3.1

4.3

4.2

4.2b1

4.1

4.1b3

4.1b2

4.1b1

4.0.3

Uh oh!

pyup-bot commented Feb 1, 2020

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants