Skip to content

Releases: astex/needs

v1.0.9

Choose a tag to compare

@astex astex released this 01 Dec 19:09

Changes:

  • Fixed a bug where combination needs with or as the parent weren't raising the correct exception.

v1.0.8

Choose a tag to compare

@astex astex released this 01 Dec 18:51

Changes:

  • Fixed a bug where errors were not correctly preserved across combinations.

v1.0.7

Choose a tag to compare

@astex astex released this 03 Nov 20:24

Changes:

  • Errors inherit better for combination needs (e.g with true_need & false_need will raise false_need.error).

v1.0.6

Choose a tag to compare

@astex astex released this 22 Oct 21:20

Changes:

  • A Need can be initialized with a boolean (defaults to True).
  • Need casts is_met() to a boolean when used as a boolean, so is_met() may now return either a boolean or a Need.

v1.0.5

Choose a tag to compare

@astex astex released this 20 Oct 18:05

Changes:

  • @needs no longer wraps the need (for python 2 compatibility).

v1.0.4

Choose a tag to compare

@astex astex released this 20 Oct 17:37

Changes:

  • Needs can be used directly as decorators.
  • CombinationNeed is used directly in place of subclasses and is bound to the Need class. This should allow easier subclassing.
  • CombinationNeed.error and NegativeNeed.error are properties rather than being defined at instantiation. This should allow them to be overridden more easily when Need.combinator or Need.negator are overridden.

v1.0.3

Choose a tag to compare

@astex astex released this 15 Oct 21:19

Changes:

  • Needs can now be used as a boolean

v1.0.2

Choose a tag to compare

@astex astex released this 06 Sep 23:51

Changes:

  • @needs now works
  • @needs is now tested
  • error inheritance is tested

v1.0.1

Choose a tag to compare

@astex astex released this 06 Sep 05:19
new version