./devel/py-hypothesis, Python library for property based testing

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 4.23.4, Package name: py37-hypothesis-4.23.4, Maintainer: pkgsrc-users

Hypothesis is a library for testing your Python code against a much
larger range of examples than you would ever want to write by hand.
It's based on the Haskell library, Quickcheck, and is designed to
integrate seamlessly into your existing Python unit testing work
flow.

Hypothesis is both extremely practical and also advances the state
of the art of unit testing by some way. It's easy to use, stable,
and extremely powerful. If you're not using Hypothesis to test your
project then you're missing out.


Required to run:
[devel/py-setuptools] [devel/py-attrs] [lang/python37]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: dd1d15cc36d8428ef054559c0cc0a6dca7af9b72
RMD160: 12fb6ff94c98ccc399f7dc92d8ff7d05599cd1d5
Filesize: 196.55 KB

Version history: (Expand)


CVS history: (Expand)


   2019-05-09 13:53:58 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 4.23.4

4.23.4:
Fixes a minor formatting issue the docstring of from_type()

4.23.3:
Adds a recipe to the docstring of from_type() that describes a means for drawing \ 
values for “everything except” a specified type. This recipe is especially \ 
useful for writing tests that perform input-type validation.

4.23.2:
This patch uses autoflake to remove some pointless pass statements, which \ 
improves our workflow but has no user-visible impact.

4.23.1:
This patch fixes an OverflowError in from_type(xrange) on Python 2.

It turns out that not only do the start and stop values have to fit in a C long, \ 
but so does stop - start. We now handle this even on 32bit platforms, but remind \ 
users that Python2 will not be supported after 2019 without specific funding.

4.23.0:
This release implements the slices() strategy, to generate slices of a \ 
length-size sequence.

4.22.3:
This patch exposes DataObject, solely to support more precise type hints. \ 
Objects of this type are provided by data(), and can be used to draw examples \ 
from strategies intermixed with your test code.

4.22.2:
This patch fixes the very rare issue 1798 in array_dtypes(), which caused an \ 
internal error in our tests.

4.22.1:
This patch fixes a rare bug in from_type(range).

4.22.0:
The unique_by argument to lists now accepts a tuple of callables such that every \ 
element of the generated list will be unique with respect to each callable in \ 
the tuple.

4.21.1:
This patch cleans up the internals of one_of(). You may see a slight change to \ 
the distribution of examples from this strategy but there is no change to the \ 
public API.

4.21.0:
The from_type() strategy now supports slice objects.

4.20.0:
This release improves the array_shapes() strategy, to choose an appropriate \ 
default for max_side based on the min_side, and max_dims based on the min_dims. \ 
An explicit error is raised for dimensions greater than 32, which are not \ 
supported by Numpy, as for other invalid combinations of arguments.

4.19.0:
The from_type() strategy now supports range objects (or xrange on Python 2).

4.18.3:
This release fixes a very rare edge case in the test-case mutator, which could \ 
cause an internal error with certain unusual tests.

4.18.2:
This patch makes Hypothesis compatible with the Python 3.8 alpha, which changed \ 
the representation of code objects to support positional-only arguments. Note \ 
however that Hypothesis does not (yet) support such functions as e.g. arguments \ 
to builds() or inputs to @given.

4.18.1:
This patch improves the performance of unique collections such as sets() when \ 
the elements are drawn from a sampled_from() strategy.

4.18.0:
This release adds the functions() strategy, which can be used to imitate your \ 
‘real’ function for callbacks.

4.17.2:
This release refactors stateful rule selection to share the new machinery with \ 
sampled_from() instead of using the original independent implementation.

4.17.1:
This patch allows Hypothesis to try a few more examples after finding the first \ 
bug, in hopes of reporting multiple distinct bugs. The heuristics described in \ 
issue 847 ensure that we avoid wasting time on fruitless searches, while still \ 
surfacing each bug as soon as possible.
   2019-04-16 09:14:00 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: updated to 4.17.0

4.17.0
This release adds the strategy \ 
:func:~hypothesis.extra.numpy.broadcastable_shapes, which generates array shapes \ 
that are broadcast-compatible with a provided shape.

4.16.0
This release allows :func:~hypothesis.strategies.register_type_strategy to be \ 
used with :obj:python:typing.NewType instances. This may be useful to e.g. \ 
provide only positive integers for :func:from_type(UserId) \ 
<hypothesis.strategies.from_type> with a UserId = NewType('UserId', int) \ 
type.

4.15.0
This release supports passing a :class:~python:datetime.timedelta as the \ 
:obj:~hypothesis.settings.deadline setting, so you no longer have to remember \ 
that the number is in milliseconds (:issue:1900).

Thanks to Damon Francisco for this change!

4.14.7
This patch makes the type annotations on hypothesis.extra.dateutil compatible \ 
with :pypi:mypy 0.700.

4.14.6
This release fixes a bug introduced in :ref:Hypothesis 4.14.3 <v4.14.3> \ 
that would sometimes cause :func:sampled_from(...).filter(...) \ 
<hypothesis.strategies.sampled_from> to encounter an internal assertion \ 
failure when there are three or fewer elements, and every element is rejected by \ 
the filter.

4.14.5
This patch takes the previous efficiency improvements to \ 
:func:sampled_from(...).filter(...) <hypothesis.strategies.sampled_from> \ 
strategies that reject most elements, and generalises them to also apply to \ 
sampled_from(...).filter(...).filter(...) and longer chains of filters.

4.14.4
This release fixes a bug that prevented \ 
:func:~hypothesis.strategies.random_module from correctly restoring the previous \ 
state of the random module.

The random state was instead being restored to a temporary deterministic state, \ 
which accidentally caused subsequent tests to see the same random values across \ 
multiple test runs.

4.14.3
This patch adds an internal special case to make \ 
:func:sampled_from(...).filter(...) <hypothesis.strategies.sampled_from> \ 
much more efficient when the filter rejects most elements
   2019-04-02 11:40:30 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: updated to 4.14.2

4.14.2
This patch improves the error message if the function f in :ref:s.flatmap(f) \ 
<flatmap> does not return a strategy.

4.14.1
This release modifies how Hypothesis selects operations to run during shrinking, \ 
by causing it to deprioritise previously useless classes of shrink until others \ 
have reached a fixed point.

This avoids certain pathological cases where the shrinker gets very close to \ 
finishing and then takes a very long time to finish the last small changes \ 
because it tries many useless shrinks for each useful one towards the end. It \ 
also should cause a more modest improvement (probably no more than about 30%) in \ 
shrinking performance for most tests.

4.14.0
This release blocks installation of Hypothesis on Python 3.4, which :PEP:reached \ 
its end of life date on 2019-03-18 <429>.

This should not be of interest to anyone but downstream maintainers - if you are \ 
affected, migrate to a secure version of Python as soon as possible or at least \ 
seek commercial support.

4.13.0
This release makes it an explicit error to call :func:floats(min_value=inf, \ 
exclude_min=True) <hypothesis.strategies.floats> or \ 
:func:floats(max_value=-inf, exclude_max=True) \ 
<hypothesis.strategies.floats>, as there are no possible values that can \ 
be generated (:issue:1859).

:func:floats(min_value=0.0, max_value=-0.0) <hypothesis.strategies.floats> \ 
is now deprecated. While 0. == -0. and we could thus generate either if \ 
comparing by value, violating the sequence ordering of floats is a special case \ 
we don't want or need.

4.12.1
This release should significantly reduce the amount of memory that Hypothesis \ 
uses for representing large test cases, by storing information in a more compact \ 
representation and only unpacking it lazily when it is first needed.

4.12.0
This update adds the :obj:~hypothesis.settings.report_multiple_bugs setting, \ 
which you can use to disable multi-bug reporting and only raise whichever bug \ 
had the smallest minimal example. This is occasionally useful when using a \ 
debugger or tools that annotate tracebacks via introspection.

4.11.7
This change makes a tiny improvement to the core engine's bookkeeping. There is \ 
no user-visible change.

4.11.6
This release changes some of Hypothesis's internal shrinking behaviour in order \ 
to reduce memory usage and hopefully improve performance.

4.11.5
This release adds a micro-optimisation to how Hypothesis handles debug reporting \ 
internally. Hard to shrink test may see a slight performance improvement, but in \ 
most common scenarios it is unlikely to be noticeable.

4.11.4
This release removes some redundant code that was no longer needed but was still \ 
running a significant amount of computation and allocation on the hot path. This \ 
should result in a modest speed improvement for most tests, especially those \ 
with large test cases.

4.11.3
This release adds a micro-optimisation to how Hypothesis caches test cases. This \ 
will cause a small improvement in speed and memory usage for large test cases, \ 
but in most common scenarios it is unlikely to be noticeable.

4.11.2
This release removes some internal code that populates a field that is no longer \ 
used anywhere. This should result in some modest performance and speed \ 
improvements and no other user visible effects.
   2019-03-13 09:51:48 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: updated to 4.11.1

4.11.1:
This is a formatting-only patch, enabled by a new version of :pypi:isort.

4.11.0:
This release deprecates :func:~hypothesis.strategies.sampled_from with empty \ 
sequences. This returns :func:~hypothesis.strategies.nothing, which gives a \ 
clear error if used directly... but simply vanishes if combined with another \ 
strategy.

Tests that silently generate less than expected are a serious problem for anyone \ 
relying on them to find bugs, and we think reliability more important than \ 
convenience in this case.

4.10.0:
This release improves Hypothesis's to detect flaky tests, by noticing when the \ 
behaviour of the test changes between runs. In particular this will notice many \ 
new cases where data generation depends on external state (e.g. external sources \ 
of randomness) and flag those as flaky sooner and more reliably.

The basis of this feature is a considerable reengineering of how Hypothesis \ 
stores its history of test cases, so on top of this its memory usage should be \ 
considerably reduced.

4.9.0:
This release adds the strategy :func:~hypothesis.extra.numpy.valid_tuple_axes, \ 
which generates tuples of axis-indices that can be passed to the axis argument \ 
in NumPy's sequential functions (e.g. :func:numpy:numpy.sum).

4.8.0:
This release significantly tightens validation in :class:hypothesis.settings. \ 
:obj:~hypothesis.settings.max_examples, :obj:~hypothesis.settings.buffer_size, \ 
and :obj:~hypothesis.settings.stateful_step_count must be positive integers; \ 
:obj:~hypothesis.settings.deadline must be a positive number or None; and \ 
:obj:~hypothesis.settings.derandomize must be either True or False.

As usual, this replaces existing errors with a more helpful error and starts new \ 
validation checks as deprecation warnings.

4.7.19:
This release makes some micro-optimisations to certain calculations performed in \ 
the shrinker. These should particularly speed up large test cases where the \ 
shrinker makes many small changes. It will also reduce the amount allocated, but \ 
most of this is garbage that would have been immediately thrown away, so you \ 
probably won't see much effect specifically from that.

4.7.18:
This patch removes some overhead from :func:~hypothesis.extra.numpy.arrays with \ 
a constant shape and dtype. The resulting performance improvement is modest, but \ 
worthwile for small arrays.
   2019-03-02 15:22:10 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 4.7.17

4.7.17:
This release makes some micro-optimisations within Hypothesis's internal \ 
representation of test cases. This should cause heavily nested test cases to \ 
allocate less during generation and shrinking, which should speed things up \ 
slightly.

4.7.16:
This changes the order in which Hypothesis runs certain operations during \ 
shrinking. This should significantly decrease memory usage and speed up \ 
shrinking of large examples.

4.7.15:
This release allows Hypothesis to calculate a number of attributes of generated \ 
test cases lazily. This should significantly reduce memory usage and modestly \ 
improve performance, especially for large test cases.

4.7.14:
This release reduces the number of operations the shrinker will try when \ 
reordering parts of a test case. This should in some circumstances significantly \ 
speed up shrinking. It may result in different final test cases, and if so \ 
usually slightly worse ones, but it should not generally have much impact on the \ 
end result as the operations removed were typically useless.

4.7.13:
This release changes how Hypothesis reorders examples within a test case during \ 
shrinking. This should make shrinking considerably faster.

4.7.12:
This release slightly improves the shrinker's ability to replace parts of a test \ 
case with their minimal version, by allowing it to do so in bulk rather than one \ 
at a time. Where this is effective, shrinker performance should be modestly \ 
improved.

4.7.11:
This release makes some micro-optimisations to common operations performed \ 
during shrinking. Shrinking should now be slightly faster, especially for large \ 
examples with relatively fast test functions.

4.7.10:
This release is a purely internal refactoring of Hypothesis's API for \ 
representing test cases. There should be no user visible effect.

4.7.9:
This release changes certain shrink passes to make them more efficient when they \ 
aren't making progress.

4.7.8:
This patch removes some unused code, which makes the internals a bit easier to \ 
understand. There is no user-visible impact.

4.7.7:
This release reduces the number of operations the shrinker will try when \ 
reordering parts of a test case. This should in some circumstances significantly \ 
speed up shrinking. It may result in different final test cases, and if so \ 
usually slightly worse ones, but it should not generally have much impact on the \ 
end result as the operations removed were typically useless.

4.7.6:
This patch removes some unused code from the shrinker. There is no user-visible \ 
change.

4.7.5:
This release changes certain shrink passes to make them adaptive - that is, in \ 
cases where they are successfully making progress they may now do so \ 
significantly faster.

4.7.4:
This is a docs-only patch, noting that because the :pypi:lark-parser is under \ 
active development at version 0.x, hypothesis[lark] APIs may break in minor \ 
releases if necessary to keep up with the upstream package.

4.7.3:
This changes Hypothesis to no longer import various test frameworks by default \ 
(if they are installed). which will speed up the initial import hypothesis call.

4.7.2:
This release changes Hypothesis's internal representation of a test case to \ 
calculate some expensive structural information on demand rather than eagerly. \ 
This should reduce memory usage a fair bit, and may make generation somewhat \ 
faster.

4.7.1:
This release refactors the internal representation of previously run test cases. \ 
The main thing you should see as a result is that Hypothesis becomes somewhat \ 
less memory hungry.

4.7.0:
This patch allows :func:~hypothesis.extra.numpy.array_shapes to generate shapes \ 
with side-length or even dimension zero, though the minimum still defaults to \ 
one. These shapes are rare and have some odd behavior, but are particularly \ 
important to test for just that reason!

In a related bigfix, :func:~hypothesis.extra.numpy.arrays now supports \ 
generating zero-dimensional arrays with dtype=object and a strategy for iterable \ 
elements. Previously, the array element would incorrectly be set to the first \ 
item in the generated iterable.
   2019-02-17 00:36:02 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 4.5.11

4.5.11:
This release fixes :issue:1813, a bug introduced in :ref:3.59.1 <v3.59.1>, \ 
which caused :py:meth:~hypothesis.strategies.random_module to no longer affect \ 
the body of the test: Although Hypothesis would claim to be seeding the random \ 
module in fact tests would always run with a seed of zero.

4.5.10:
This patch fixes an off-by-one error in the maximum length of \ 
:func:~hypothesis.strategies.emails. Thanks to Krzysztof Jurewicz for \ 
:pull:1812.

4.5.9:
This patch removes some unused code from the shrinker. There is no user-visible \ 
change.

4.5.8:
This release fixes an internal IndexError in Hypothesis that could sometimes be \ 
triggered during shrinking.

4.5.7:
This release modifies the shrinker to interleave different types of reduction \ 
operations, e.g. switching between deleting data and lowering scalar values \ 
rather than trying entirely deletions then entirely lowering.

This may slow things down somewhat in the typical case, but has the major \ 
advantage that many previously difficult to shrink examples should become much \ 
faster, because the shrinker will no longer tend to stall when trying some \ 
ineffective changes to the shrink target but will instead interleave it with \ 
other more effective operations.

4.5.6:
This release makes a number of internal changes to the implementation of \ 
:func:hypothesis.extra.lark.from_lark. These are primarily intended as a \ 
refactoring, but you may see some minor improvements to performance when \ 
generating large strings, and possibly to shrink quality.

4.5.5:
This patch prints an explanatory note when :issue:1798 is triggered, because the \ 
error message from Numpy is too terse to locate the problem.

4.5.4:
In Python 2, long integers are not allowed in the shape argument to \ 
:func:~hypothesis.extra.numpy.arrays. Thanks to Ryan Turner for fixing this.

4.5.3:
This release makes a small internal refactoring to clarify how Hypothesis \ 
instructs tests to stop running when appropriate. There is no user-visible \ 
change.

4.5.2:
This release standardises all of the shrinker's internal operations on running \ 
in a random order.

The main effect you will see from this that it should now be much less common \ 
for the shrinker to stall for a long time before making further progress. In \ 
some cases this will correspond to shrinking more slowly, but on average it \ 
should result in faster shrinking.

4.5.1:
This patch updates some docstrings, but has no runtime changes.

4.5.0:
This release adds exclude_min and exclude_max arguments to \ 
:func:~hypothesis.strategies.floats, so that you can easily generate values from \ 
open or half-open intervals
   2019-02-01 12:50:30 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 4.4.3

4.4.3:
This release fixes an open file leak that used to cause ResourceWarnings.

4.4.2:
This release changes Hypothesis's internal approach to caching the results of \ 
executing test cases. The result should be that it is now significantly less \ 
memory hungry, especially when shrinking large test cases.

Some tests may get slower or faster depending on whether the new or old caching \ 
strategy was well suited to them, but any change in speed in either direction \ 
should be minor.

4.4.1:
This patch tightens up some of our internal heuristics to deal with shrinking \ 
floating point numbers, which will now run in fewer circumstances.

You are fairly unlikely to see much difference from this, but if you do you are \ 
likely to see shrinking become slightly faster and/or producing slightly worse \ 
results.

4.4.0:
This release adds the :func:~hypothesis.extra.django.from_form function, which \ 
allows automatic testing against Django forms. (:issue:35)

4.3.0:
This release deprecates HealthCheck.hung_test and disables the associated \ 
runtime check for tests that ran for more than five minutes. Such a check is \ 
redundant now that we enforce the deadline and max_examples setting, which can \ 
be adjusted independently.

4.2.0:
This release adds a new module, hypothesis.extra.lark, which you can use to \ 
generate strings matching a context-free grammar.

In this initial version, only :pypi:lark-parser EBNF grammars are supported, by \ 
the new :func:hypothesis.extra.lark.from_lark function.

4.1.2:
This patch fixes a very rare overflow bug (:issue:1748) which could raise an \ 
InvalidArgument error in :func:~hypothesis.strategies.complex_numbers even \ 
though the arguments were valid.

4.1.1:
This release makes some improvements to internal code organisation and \ 
documentation and has no impact on behaviour.

4.1.0:
This release adds :func:~hypothesis.register_random, which registers \ 
random.Random instances or compatible objects to be seeded and reset by \ 
Hypothesis to ensure that test cases are deterministic.

We still recommend explicitly passing a random.Random instance from \ 
:func:~hypothesis.strategies.randoms if possible, but registering a \ 
framework-global state for Hypothesis to manage is better than flaky tests!

4.0.2:
This patch fixes :issue:1387, where bounded \ 
:func:~hypothesis.strategies.integers with a very large range would almost \ 
always generate very large numbers. Now, we usually use the same tuned \ 
distribution as unbounded :func:~hypothesis.strategies.integers.

4.0.1:
This release randomizes the order in which the shrinker tries some of its \ 
initial normalization operations. You are unlikely to see much difference as a \ 
result unless your generated examples are very large. In this case you may see \ 
some performance improvements in shrinking.

4.0.0:
Welcome to the next major version of Hypothesis!

There are no new features here, as we release those in minor versions. Instead, \ 
4.0 is a chance for us to remove deprecated features (many already converted \ 
into no-ops), and turn a variety of warnings into errors.

If you were running on the last version of Hypothesis 3.x without any Hypothesis \ 
deprecation warnings (or using private APIs), this will be a very boring \ 
upgrade. In fact, nothing will change for you at all. Per :ref:our deprecation \ 
policy <deprecation-policy>, warnings added in the last six months (after \ 
2018-07-05) have not been converted to errors.

Removals
hypothesis.extra.datetime has been removed, replaced by the core date and time \ 
strategies.
hypothesis.extra.fakefactory has been removed, replaced by general expansion of \ 
Hypothesis' strategies and the third-party ecosystem.
The SQLite example database backend has been removed.

Settings
The :obj:~hypothesis.settings.deadline is now enforced by default, rather than \ 
just emitting a warning when the default (200 milliseconds per test case) \ 
deadline is exceeded.
The database_file setting has been removed; use :obj:~hypothesis.settings.database.
The perform_health_check setting has been removed; use \ 
:obj:~hypothesis.settings.suppress_health_check.
The max_shrinks setting has been removed; use :obj:~hypothesis.settings.phases \ 
to disable shrinking.
The min_satisfying_examples, max_iterations, strict, timeout, and use_coverage \ 
settings have been removed without user-configurable replacements.

Strategies
The elements argument is now required for collection strategies.
The average_size argument was a no-op and has been removed.
Date and time strategies now only accept min_value and max_value for bounds.
:func:~hypothesis.strategies.builds now requires that the thing to build is \ 
passed as the first positional argument.
Alphabet validation for :func:~hypothesis.strategies.text raises errors, not \ 
warnings, as does category validation for \ 
:func:~hypothesis.strategies.characters.
The choices() strategy has been removed. Instead, you can use \ 
:func:~hypothesis.strategies.data with \ 
:func:~hypothesis.strategies.sampled_from, so choice(elements) becomes \ 
data.draw(sampled_from(elements)).
The streaming() strategy has been removed. Instead, you can use \ 
:func:~hypothesis.strategies.data and replace iterating over the stream with \ 
data.draw() calls.
:func:~hypothesis.strategies.sampled_from and \ 
:func:~hypothesis.strategies.permutations raise errors instead of warnings if \ 
passed a collection that is not a sequence.

Miscellaneous
Applying :func:@given <hypothesis.given> to a test function multiple times \ 
was really inefficient, and now it's also an error.
Using the .example() method of a strategy (intended for interactive exploration) \ 
within another strategy or a test function always weakened data generation and \ 
broke shrinking, and now it's an error too.
The HYPOTHESIS_DATABASE_FILE environment variable is no longer supported, as the \ 
database_file setting has been removed.
The HYPOTHESIS_VERBOSITY_LEVEL environment variable is no longer supported. You \ 
can use the --hypothesis-verbosity pytest argument instead, or write your own \ 
setup code using the settings profile system to replace it.
Using :func:@seed <hypothesis.seed> or :obj:derandomize=True \ 
<hypothesis.settings.derandomize> now forces :obj:database=None \ 
<hypothesis.settings.database> to ensure results are in fact reproducible. \ 
If :obj:~hypothesis.settings.database is not None, doing so also emits a \ 
HypothesisWarning.
Unused exception types have been removed from hypothesis.errors; namely \ 
AbnormalExit, BadData, BadTemplateDraw, DefinitelyNoSuchExample, Timeout, and \ 
WrongFormat.
   2019-01-07 09:31:28 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: updated to 3.86.5

3.86.5:
This is a docs-only patch, which fixes some typos and removes a few hyperlinks \ 
for deprecated features.

3.86.4:
This release changes the order in which the shrinker tries to delete data. For \ 
large and slow tests this may significantly improve the performance of \ 
shrinking.

3.86.3:
This release fixes a bug where certain places Hypothesis internal errors could \ 
be raised during shrinking when a user exception occurred that suppressed an \ 
exception Hypothesis uses internally in its generation.

The two known ways to trigger this problem were:

Errors raised in stateful tests’ teardown function.
Errors raised in finally blocks that wrapped a call to data.draw.
These cases will now be handled correctly.

3.86.2:
This patch is a docs-only change to fix a broken hyperlink.

3.86.1:
This patch fixes issue 1732, where integers() would always return long values on \ 
Python 2.

3.86.0:
This release ensures that infinite numbers are never generated by floats() with \ 
allow_infinity=False, which could previously happen in some cases where one \ 
bound was also provided.

The trivially inconsistent min_value=inf, allow_infinity=False now raises an \ 
InvalidArgumentError, as does the inverse with max_value. You can still use \ 
just(inf) to generate inf without violating other constraints.