Log message:
py-attrs: updated to 17.4.0

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.
  Due to the nature of this bug, a proper deprecation cycle was unfortunately \ 
impossible.
  Generally speaking, it's advisable to prefer kwargs-based initialization \ 
anyways – *especially* if you employ multiple inheritance and diamond-shaped \ 
hierarchies.
- 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 attr-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

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.

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.
- 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.
- ctypes is optional now however if it's missing, a bare super() will not work \ 
in slots classes.
  This should only happen in special environments like Google App Engine.
- 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.
- Subclasses of auto_attribs=True can be empty now.
- Equality tests are *much* faster now.
- All generated methods now have correct __module__, __name__, and (on Python 3) \ 
__qualname__ attributes.

Log message:
py-attrs: updated to 17.3.0

17.3.0:

Backward-incompatible Changes
- Attributes are not defined on the class body anymore.
  This means that if you define a class C with an attribute x, the class will \ 
*not* have an attribute x for introspe
ction anymore.
  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.

Changes
- super() and __class__ now work on Python 3 when slots=True.
- 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
- The combination of str=True and slots=True now works on Python 2.
- attr.Factory is hashable again.
- Subclasses now can overwrite attribute definitions of their superclass.

  That means that you can -- for example -- change the default value for an \ 
attribute by redefining it.
- 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.

Log message:
Disabled BUILD_DEPENDS: hypothesis now requires attrs

Log message:
Comment out dead MASTER_SITES/HOMEPAGEs.

Log message:
Changes 17.2.0:
Validators are hashable again. Note that validators may become frozen in the \ 
future, pending availability of no-overhead frozen classes.

Log message:
Changes 17.1.0:
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’s specification. 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).
* Correspondingly, attr.ib‘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.
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).
FrozenInstanceError is now raised when trying to delete an attribute from a \ 
frozen class.
Frozen-ness of classes is now inherited.
__attrs_post_init__() is now run if validation is disabled.
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.
Added attr.validators.and_() that composes multiple validators into one.
For convenience, the validator argument of @attr.s now can take a list of \ 
validators that are wrapped using and_().
Accordingly, attr.validators.optional() now can take a list of validators too.
Validators can now be defined conveniently inline by using the attribute as a \ 
decorator. Check out the examples to see it in action!
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.
Default factories can now also be defined inline using decorators. They are \ 
always passed the partially initialized instance.
Conversion can now be made optional using attr.converters.optional().
attr.make_class() now accepts the keyword argument bases which allows for \ 
subclassing.
Metaclasses are now preserved with slots=True.

Log message:
Changes 16.3.0:
* Attributes now can have user-defined metadata which greatly improves \ 
attrs‘s extensibility.

* Allow for a __attrs_post_init__ method that – if defined – will get \ 
called at the end of the attrs-generated __init__ method.

* Add @attr.s(str=True) that will optionally create a __str__ method that is \ 
identical to __repr__. This is mainly useful with Exceptions 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 Exceptions and were puzzled by the tracebacks: \ 
this option is for you.

* Don’t overwrite __name__ with __qualname__ for attr.s(slots=True) classes.

Log message:
Fix MASTER_SITES.

Log message:
Import py-attrs-15.2.0 as devel/py-attrs

attrs is an MIT-licensed Python package with class decorators that ease the
chores of implementing the most common attribute-related object protocols.

You just specify the attributes to work with and attrs gives you:

 * a nice human-readable __repr__,
 * a complete set of comparison methods,
 * an initializer,
 * and much more

without writing dull boilerplate code again and again.

This gives you the power to use actual classes with actual types in your code
instead of confusing tuples or confusingly behaving namedtuples.

So put down that type-less data structures and welcome some class into your
life!