Auto clearing of mail.outbox has been re-introduced to not break
functionality in 3.x.x release. This means that Compatibility issues
mentioned in the 3.1.0 release are no longer present. Related issue:
_pytest-django issue <https://github.com/pytest-dev/pytest-django/issues/433>
3.1.1
Bug fixes
^^^^^^^^^
Workaround --pdb interaction with Django TestCase. The issue is caused by
Django TestCase not implementing TestCase.debug() properly but was brought to
attention with recent changes in pytest 3.0.2. Related issues: pytest issue <https://github.com/pytest-dev/pytest/issues/1977>,
Django issue <https://code.djangoproject.com/ticket/27391>.
3.1.0
Features
^^^^^^^^
Added new function scoped fixture mailoutbox that gives access to
djangos mail.outbox. The will clean/empty the mail.outbox to
assure that no old mails are still in the outbox.
If django.contrib.sites is in your INSTALLED_APPS, Site cache will
be cleared for each test to avoid hitting the cache and cause wrong Site
object to be returned by Site.objects.get_current().
Compatibility
^^^^^^^^^^^^^
IMPORTANT: the internal autouse fixture _django_clear_outbox has been
removed. If you have relied on this to get an empty outbox for your
test, you should change tests to use the mailoutbox fixture instead.
See documentation of mailoutbox fixture for usage. If you try to
access mail.outbox directly, AssertionError will be raised. If you
previously relied on the old behaviour and do not want to change your
tests, put this in your project conftest.py::
pytest.fixture(autouse=True)
def clear_outbox():
from django.core import mail
mail.outbox = []
3.0.0
Bug fixes
^^^^^^^^^
Fix error when Django happens to be imported before pytest-django runs.
Thanks to Will Harris for the bug report <https://github.com/pytest-dev/pytest-django/issues/289>_.
Features
^^^^^^^^
Added a new option --migrations to negate a default usage of
--nomigrations.
The previously internal pytest-django fixture that handles database creation
and setup has been refactored, refined and made a public API.
This opens up more flexibility and advanced use cases to configure the test
database in new ways.
See :ref:advanced-database-configuration for more information on the new
fixtures and example use cases.
Compatibility
^^^^^^^^^^^^^
Official for the pytest 3.0.0 (2.9.2 release should work too, though). The
documentation is updated to mention pytest instead of py.test.
Django versions 1.4, 1.5 and 1.6 is no longer supported. The supported
versions are now 1.7 and forward. Django master is supported as of
2016-08-21.
pytest-django no longer supports Python 2.6.
Specifying the DJANGO_TEST_LIVE_SERVER_ADDRESS environment variable is no
longer supported. Use DJANGO_LIVE_TEST_SERVER_ADDRESS instead.
Ensuring accidental database access is now stricter than before. Previously
database access was prevented on the cursor level. To be safer and prevent
more cases, it is now prevented at the connection level. If you previously
had tests which interacted with the databases without a database cursor, you
will need to mark them with the :func:pytest.mark.django_db marker or
request the db fixture.
The previously undocumented internal fixtures _django_db_setup,
_django_cursor_wrapper have been removed in favour of the new public
fixtures. If you previously relied on these internal fixtures, you must
update your code. See :ref:advanced-database-configuration for more
information on the new fixtures and example use cases.
pytest 2.9.1 -> 3.0.5
3.0.5
==================
Add warning when not passing option=value correctly to -o/--override-ini (2105).
Also improved the help documentation. Thanks to mbukatov for the report and
lwm_ for the PR.
Now --confcutdir and --junit-xml are properly validated if they are directories
and filenames, respectively (2089 and 2078). Thanks to lwm_ for the PR.
Add hint to error message hinting possible missing __init__.py (478). Thanks DuncanBetts.
More accurately describe when fixture finalization occurs in documentation (687). Thanks DuncanBetts.
Provide :ref: targets for recwarn.rst so we can use intersphinx referencing.
Thanks to dupuy for the report and lwm for the PR.
In Python 2, use a simple +- ASCII string in the string representation of pytest.approx (for example "4 +- 4.0e-06")
because it is brittle to handle that in different contexts and representations internally in pytest
which can result in bugs such as 2111. In Python 3, the representation still uses ± (for example 4 ± 4.0e-06).
Thanks kerrick-lyft for the report and nicoddemus_ for the PR.
Using item.Function, item.Module, etc., is now issuing deprecation warnings, prefer
pytest.Function, pytest.Module, etc., instead (2034).
Thanks nmundar for the PR.
Fix error message using approx with complex numbers (2082).
Thanks adler-j for the report and nicoddemus_ for the PR.
Fixed false-positives warnings from assertion rewrite hook for modules imported more than
once by the pytest_plugins mechanism.
Thanks nicoddemus_ for the PR.
Remove an internal cache which could cause hooks from conftest.py files in
sub-directories to be called in other directories incorrectly (2016).
Thanks d-b-w for the report and nicoddemus_ for the PR.
Remove internal code meant to support earlier Python 3 versions that produced the side effect
of leaving None in sys.modules when expressions were evaluated by pytest (for example passing a condition
as a string to pytest.mark.skipif)(2103).
Thanks jaraco for the report and nicoddemus_ for the PR.
Cope gracefully with a .pyc file with no matching .py file (2038). Thanks
nedbat.
Import errors when collecting test modules now display the full traceback (1976).
Thanks cwitty for the report and nicoddemus_ for the PR.
Fix confusing command-line help message for custom options with two or more metavar properties (2004).
Thanks okulynyak and davehunt for the report and nicoddemus for the PR.
When loading plugins, import errors which contain non-ascii messages are now properly handled in Python 2 (1998).
Thanks nicoddemus for the PR.
Fixed cyclic reference when pytest.raises is used in context-manager form (1965_). Also as a
result of this fix, sys.exc_info() is left empty in both context-manager and function call usages.
Previously, sys.exc_info would contain the exception caught by the context manager,
even when the expected exception occurred.
Thanks MSeifert04_ for the report and the PR.
Fixed false-positives warnings from assertion rewrite hook for modules that were rewritten but
were later marked explicitly by pytest.register_assert_rewrite
or implicitly as a plugin (2005).
Thanks RonnyPfannschmidt for the report and nicoddemus_ for the PR.
Report teardown output on test failure (442).
Thanks matclab for the PR.
Fix teardown error message in generated xUnit XML.
Thanks gdyuldin_ for the PR.
Properly handle exceptions in multiprocessing tasks (1984).
Thanks adborden for the report and nicoddemus_ for the PR.
Clean up unittest TestCase objects after tests are complete (1649_).
Thanks d_b_w_ for the report and PR.
Improve error message when passing non-string ids to pytest.mark.parametrize (1857).
Thanks okken for the report and nicoddemus_ for the PR.
Add buffer attribute to stdin stub class pytest.capture.DontReadFromInput
Thanks joguSD_ for the PR.
Fix UnicodeEncodeError when string comparison with unicode has failed. (1864)
Thanks AiOO for the PR.
pytest_plugins is now handled correctly if defined as a string (as opposed as
a sequence of strings) when modules are considered for assertion rewriting.
Due to this bug, much more modules were being rewritten than necessary
if a test suite uses pytest_plugins to load internal plugins (1888).
Thanks jaraco for the report and nicoddemus for the PR (1891).
Do not call tearDown and cleanups when running tests from
unittest.TestCase subclasses with --pdb
enabled. This allows proper post mortem debugging for all applications
which have significant logic in their tearDown machinery (1890). Thanks
mbyt for the PR.
Fix use of deprecated getfuncargvalue method in the internal doctest plugin.
Thanks ViviCoder for the report (1898).
Fix regression when importorskip is used at module level (1822).
Thanks jaraco and The-Compiler for the report and nicoddemus for the PR.
Fix parametrization scope when session fixtures are used in conjunction
with normal parameters in the same call (1832).
Thanks The-Compiler for the report, Kingdread and nicoddemus for the PR.
Fix internal error when parametrizing tests or fixtures using an empty ids argument (1849).
Thanks OPpuolitaival for the report and nicoddemus_ for the PR.
Fix loader error when running pytest embedded in a zipfile.
Thanks mbachry_ for the PR.
A number of incompatible changes were made in this release, with the intent of removing features deprecated for a long
time or change existing behaviors in order to make them less surprising/more useful.
Reinterpretation mode has now been removed. Only plain and rewrite
mode are available, consequently the --assert=reinterp option is
no longer available. This also means files imported from plugins or
conftest.py will not benefit from improved assertions by
default, you should use pytest.register_assert_rewrite() to
explicitly turn on assertion rewriting for those files. Thanks
flub_ for the PR.
The following deprecated commandline options were removed:
--genscript: no longer supported;
--no-assert: use --assert=plain instead;
--nomagic: use --assert=plain instead;
--report: use -r instead;
Thanks to RedBeardCode for the PR (1664).
ImportErrors in plugins now are a fatal error instead of issuing a
pytest warning (1479). Thanks to The-Compiler for the PR.
Removed support code for Python 3 versions < 3.3 (1627_).
Removed all py.test-X* entry points. The versioned, suffixed entry points
were never documented and a leftover from a pre-virtualenv era. These entry
points also created broken entry points in wheels, so removing them also
removes a source of confusion for users (1632).
Thanks obestwalter for the PR.
pytest.skip() now raises an error when used to decorate a test function,
as opposed to its original intent (to imperatively skip a test inside a test function). Previously
this usage would cause the entire module to be skipped (607).
Thanks omarkohl for the complete PR (1519_).
Exit tests if a collection error occurs. A poll indicated most users will hit CTRL-C
anyway as soon as they see collection errors, so pytest might as well make that the default behavior (1421).
A --continue-on-collection-errors option has been added to restore the previous behaviour.
Thanks olegpidsadnyi and omarkohl for the complete PR (1628).
Renamed the pytest pdb module (plugin) into debugging to avoid clashes with the builtin pdb module.
Raise a helpful failure message when requesting a parametrized fixture at runtime,
e.g. with request.getfixturevalue. Previously these parameters were simply
never defined, so a fixture decorated like pytest.fixture(params=[0, 1, 2])
only ran once (460).
Thanks to nikratio for the bug report, RedBeardCode and tomviner for the PR.
_pytest.monkeypatch.monkeypatch class has been renamed to _pytest.monkeypatch.MonkeyPatch
so it doesn't conflict with the monkeypatch fixture.
--exitfirst / -x can now be overridden by a following --maxfail=N
and is just a synonym for --maxfail=1.
New Features
Support nose-style __test__ attribute on methods of classes,
including unittest-style Classes. If set to False, the test will not be
collected.
New doctest_namespace fixture for injecting names into the
namespace in which doctests run.
Thanks milliams for the complete PR (1428).
New --doctest-report option available to change the output format of diffs
when running (failing) doctests (implements 1749).
Thanks hartym for the PR.
New name argument to pytest.fixture decorator which allows a custom name
for a fixture (to solve the funcarg-shadowing-fixture problem).
Thanks novas0x2a for the complete PR (1444).
New approx() function for easily comparing floating-point numbers in
tests.
Thanks kalekundert for the complete PR (1441).
Ability to add global properties in the final xunit output file by accessing
the internal junitxml plugin (experimental).
Thanks tareqalayan for the complete PR 1454).
New ExceptionInfo.match() method to match a regular expression on the
string representation of an exception (372).
Thanks omarkohl for the complete PR (1502_).
__tracebackhide__ can now also be set to a callable which then can decide
whether to filter the traceback based on the ExceptionInfo object passed
to it. Thanks The-Compiler for the complete PR (1526).
New pytest_make_parametrize_id(config, val) hook which can be used by plugins to provide
friendly strings for custom types.
Thanks palaviv_ for the PR.
capsys and capfd now have a disabled() context-manager method, which
can be used to temporarily disable capture within a test.
Thanks nicoddemus_ for the PR.
New cli flag --fixtures-per-test: shows which fixtures are being used
for each selected test item. Features doc strings of fixtures by default.
Can also show where fixtures are defined if combined with -v.
Thanks hackebrot_ for the PR.
Introduce pytest command as recommended entry point. Note that py.test
still works and is not scheduled for removal. Closes proposal
1629. Thanks obestwalter and davehunt for the complete PR
(1633).
New cli flags:
--setup-plan: performs normal collection and reports
the potential setup and teardown and does not execute any fixtures and tests;
--setup-only: performs normal collection, executes setup and teardown of
fixtures and reports them;
--setup-show: performs normal test execution and additionally shows
setup and teardown of fixtures;
--keep-duplicates: py.test now ignores duplicated paths given in the command
line. To retain the previous behavior where the same test could be run multiple
times by specifying it in the command-line multiple times, pass the --keep-duplicates
argument (1609_);
Thanks d6e, kvas-it, sallner, ioggstream and omarkohl_ for the PRs.
New CLI flag --override-ini/-o: overrides values from the ini file.
For example: "-o xfail_strict=True"'.
Thanks blueyed and fengxx for the PR.
pytest_fixture_post_finalizer(fixturedef): called after the fixture's
finalizer and has access to the fixture's result cache.
Thanks d6e, sallner.
Issue warnings for asserts whose test is a tuple literal. Such asserts will
never fail because tuples are always truthy and are usually a mistake
(see 1562). Thanks kvas-it, for the PR.
Allow passing a custom debugger class (e.g. --pdbcls=IPython.core.debugger:Pdb).
Thanks to anntzer_ for the PR.
Changes
Plugins now benefit from assertion rewriting. Thanks
sober7, nicoddemus and flub_ for the PR.
Change report.outcome for xpassed tests to "passed" in non-strict
mode and "failed" in strict mode. Thanks to hackebrot for the PR
(1795) and gprasad84 for report (1546).
Tests marked with xfail(strict=False) (the default) now appear in
JUnitXML reports as passing tests instead of skipped.
Thanks to hackebrot for the PR (1795).
Highlight path of the file location in the error report to make it easier to copy/paste.
Thanks suzaku for the PR (1778).
Fixtures marked with pytest.fixture can now use yield statements exactly like
those marked with the pytest.yield_fixture decorator. This change renders
pytest.yield_fixture deprecated and makes pytest.fixture with yield statements
the preferred way to write teardown code (1461).
Thanks csaftoiu for bringing this to attention and nicoddemus_ for the PR.
Explicitly passed parametrize ids do not get escaped to ascii (1351).
Thanks ceridwen for the PR.
Fixtures are now sorted in the error message displayed when an unknown
fixture is declared in a test function.
Thanks nicoddemus_ for the PR.
pytest_terminal_summary hook now receives the exitstatus
of the test session as argument. Thanks blueyed for the PR (1809).
Parametrize ids can accept None as specific test id, in which case the
automatically generated id for that argument will be used.
Thanks palaviv for the complete PR (1468).
The parameter to xunit-style setup/teardown methods (setup_method,
setup_module, etc.) is now optional and may be omitted.
Thanks okken for bringing this to attention and nicoddemus for the PR.
Improved automatic id generation selection in case of duplicate ids in
parametrize.
Thanks palaviv for the complete PR (1474).
Now pytest warnings summary is shown up by default. Added a new flag
--disable-pytest-warnings to explicitly disable the warnings summary (1668_).
Make ImportError during collection more explicit by reminding
the user to check the name of the test module/package(s) (1426).
Thanks omarkohl for the complete PR (1520_).
Add build/ and dist/ to the default --norecursedirs list. Thanks
mikofski for the report and tomviner for the PR (1544_).
pytest.raises in the context manager form accepts a custom
message to raise when no exception occurred.
Thanks palaviv for the complete PR (1616).
conftest.py files now benefit from assertion rewriting; previously it
was only available for test modules. Thanks flub, sober7 and
nicoddemus for the PR (1619).
Text documents without any doctests no longer appear as "skipped".
Thanks graingert for reporting and providing a full PR (1580).
Ensure that a module within a namespace package can be found when it
is specified on the command line together with the --pyargs
option. Thanks to taschini for the PR (1597).
Always include full assertion explanation during assertion rewriting. The previous behaviour was hiding
sub-expressions that happened to be False, assuming this was redundant information.
Thanks bagerard for reporting (1503). Thanks to davehunt and
tomviner for the PR.
OptionGroup.addoption() now checks if option names were already
added before, to make it easier to track down issues like 1618_.
Before, you only got exceptions later from argparse library,
giving no clue about the actual reason for double-added options.
yield-based tests are considered deprecated and will be removed in pytest-4.0.
Thanks nicoddemus_ for the PR.
[pytest] sections in setup.cfg files should now be named [tool:pytest]
to avoid conflicts with other distutils commands (see 567). [pytest] sections in
pytest.ini or tox.ini files are supported and unchanged.
Thanks nicoddemus for the PR.
Using pytest_funcarg__ prefix to declare fixtures is considered deprecated and will be
removed in pytest-4.0 (1684).
Thanks nicoddemus for the PR.
Passing a command-line string to pytest.main() is considered deprecated and scheduled
for removal in pytest-4.0. It is recommended to pass a list of arguments instead (1723_).
Rename getfuncargvalue to getfixturevalue. getfuncargvalue is
still present but is now considered deprecated. Thanks to RedBeardCode and tomviner
for the PR (1626_).
optparse type usage now triggers DeprecationWarnings (1740_).
Refined logic for determining the rootdir, considering only valid
paths which fixes a number of issues: 1594, 1435 and 1471.
Updated the documentation according to current behavior. Thanks to
blueyed, davehunt and matthiasha for the PR.
Always include full assertion explanation. The previous behaviour was hiding
sub-expressions that happened to be False, assuming this was redundant information.
Thanks bagerard for reporting (1503). Thanks to davehunt and
tomviner for PR.
Better message in case of not using parametrized variable (see 1539).
Thanks to tramwaj29 for the PR.
Updated docstrings with a more uniform style.
Add stderr write for pytest.exit(msg) during startup. Previously the message was never shown.
Thanks BeyondEvil for reporting 1210. Thanks to JonathonSonesen and
tomviner for the PR.
No longer display the incorrect test deselection reason (1372).
Thanks ronnypfannschmidt for the PR.
The --resultlog command line option has been deprecated: it is little used
and there are more modern and better alternatives (see 830).
Thanks nicoddemus for the PR.
Improve error message with fixture lookup errors: add an 'E' to the first
line and '>' to the rest. Fixes 717. Thanks blueyed for reporting and
a PR, eolo999 for the initial PR and tomviner for his guidance during
EuroPython2016 sprint.
Bug Fixes
Parametrize now correctly handles duplicated test ids.
Fix internal error issue when the method argument is missing for
teardown_method() (1605_).
Fix exception visualization in case the current working directory (CWD) gets
deleted during testing (1235). Thanks bukzor for reporting. PR by
marscher_.
Improve test output for logical expression with brackets (925).
Thanks DRMacIver for reporting and RedBeardCode_ for the PR.
Create correct diff for strings ending with newlines (1553).
Thanks Vogtinator for reporting and RedBeardCode and
tomviner for the PR.
ConftestImportFailure now shows the traceback making it easier to
identify bugs in conftest.py files (1516). Thanks txomon for
the PR.
Text documents without any doctests no longer appear as "skipped".
Thanks graingert for reporting and providing a full PR (1580).
Fixed collection of classes with custom __new__ method.
Fixes 1579. Thanks to Stranger6667 for the PR.
Fixed scope overriding inside metafunc.parametrize (634).
Thanks to Stranger6667 for the PR.
Fixed the total tests tally in junit xml output (1798).
Thanks to cryporchild for the PR.
Fixed off-by-one error with lines from request.node.warn.
Thanks to blueyed_ for the PR.
Prepare CLI options to pytest 3.0, to avoid a deprecation warning.
Fix error due to missing CHANGES.rst when creating the source distribution
by adding a MANIFEST.in.
requests 2.10.0 -> 2.12.4
2.12.4
+++++++++++++++++++
Bugfixes
Fixed regression from 2.12.2 where non-string types were rejected in the
basic auth parameters. While support for this behaviour has been readded,
the behaviour is deprecated and will be removed in the future.
2.12.3
+++++++++++++++++++
Bugfixes
Fixed regression from v2.12.1 for URLs with schemes that begin with "http".
These URLs have historically been processed as though they were HTTP-schemed
URLs, and so have had parameters added. This was removed in v2.12.2 in an
overzealous attempt to resolve problems with IDNA-encoding those URLs. This
change was reverted: the other fixes for IDNA-encoding have been judged to
be sufficient to return to the behaviour Requests had before v2.12.0.
2.12.2
+++++++++++++++++++
Bugfixes
Fixed several issues with IDNA-encoding URLs that are technically invalid but
which are widely accepted. Requests will now attempt to IDNA-encode a URL if
it can but, if it fails, and the host contains only ASCII characters, it will
be passed through optimistically. This will allow users to opt-in to using
IDNA2003 themselves if they want to, and will also allow technically invalid
but still common hostnames.
Fixed an issue where URLs with leading whitespace would raise
InvalidSchema errors.
Fixed an issue where some URLs without the HTTP or HTTPS schemes would still
have HTTP URL preparation applied to them.
Fixed an issue where Unicode strings could not be used in basic auth.
Fixed an issue encountered by some Requests plugins where constructing a
Response object would cause Response.content to raise an
AttributeError.
2.12.1
+++++++++++++++++++
Bugfixes
Updated setuptools 'security' extra for the new PyOpenSSL backend in urllib3.
Miscellaneous
Updated bundled urllib3 to 1.19.1.
2.12.0
+++++++++++++++++++
Improvements
Updated support for internationalized domain names from IDNA2003 to IDNA2008.
This updated support is required for several forms of IDNs and is mandatory
for .de domains.
Much improved heuristics for guessing content lengths: Requests will no
longer read an entire StringIO into memory.
Much improved logic for recalculating Content-Length headers for
PreparedRequest objects.
Improved tolerance for file-like objects that have no tell method but
do have a seek method.
Anything that is a subclass of Mapping is now treated like a dictionary
by the data= keyword argument.
Requests now tolerates empty passwords in proxy credentials, rather than
stripping the credentials.
If a request is made with a file-like object as the body and that request is
redirected with a 307 or 308 status code, Requests will now attempt to
rewind the body object so it can be replayed.
Bugfixes
When calling response.close, the call to close will be propagated
through to non-urllib3 backends.
Fixed issue where the ALL_PROXY environment variable would be preferred
over scheme-specific variables like HTTP_PROXY.
Fixed issue where non-UTF8 reason phrases got severely mangled by falling
back to decoding using ISO 8859-1 instead.
Fixed a bug where Requests would not correctly correlate cookies set when
using custom Host headers if those Host headers did not use the native
string type for the platform.
Miscellaneous
Updated bundled urllib3 to 1.19.
Updated bundled certifi certs to 2016.09.26.
2.11.1
+++++++++++++++++++
Bugfixes
Fixed a bug when using iter_content with decode_unicode=True for
streamed bodies would raise AttributeError. This bug was introduced in
2.11.
Strip Content-Type and Transfer-Encoding headers from the header block when
following a redirect that transforms the verb from POST/PUT to GET.
2.11.0
+++++++++++++++++++
Improvements
Added support for the ALL_PROXY environment variable.
Reject header values that contain leading whitespace or newline characters to
reduce risk of header smuggling.
Bugfixes
Fixed occasional TypeError when attempting to decode a JSON response that
occurred in an error case. Now correctly returns a ValueError.
Requests would incorrectly ignore a non-CIDR IP address in the NO_PROXY
environment variables: Requests now treats it as a specific IP.
Fixed a bug when sending JSON data that could cause us to encounter obscure
OpenSSL errors in certain network conditions (yes, really).
Added type checks to ensure that iter_content only accepts integers and
None for chunk sizes.
Fixed issue where responses whose body had not been fully consumed would have
the underlying connection closed but not returned to the connection pool,
which could cause Requests to hang in situations where the HTTPAdapter
had been configured to use a blocking connection pool.
Miscellaneous
Updated bundled urllib3 to 1.16.
Some previous releases accidentally accepted non-strings as acceptable header values. This release does not.
pip-tools 1.6.5 -> 1.8.0
1.8.0
Adds support for upgrading individual packages with a new option
--upgrade-package. To upgrade a specific package to the latest or
a specific version use --upgrade-package <pkg>. To upgrade all packages,
you can still use pip-compile --upgrade. (409)
Adds support for pinning dependencies even further by including the hashes
found on PyPI at compilation time, which will be re-checked when dependencies
are installed at installation time. This adds protection against packages
that are tampered with. (383)
Improve support for extras, like hypothesis[django]
Drop support for pip < 8
1.7.1
Add --allow-unsafe option (377)
1.7.0
Add compatibility with pip >= 8.1.2 (374)
Thanks so much, jmbowman!
python-dateutil 2.5.3 -> 2.6.0
2.6.0
Added PEP-495-compatible methods to address ambiguous and imaginary dates in
time zones in a backwards-compatible way. Ambiguous dates and times can now
be safely represented by all dateutil time zones. Many thanks to Alexander
Belopolski (abalkin) and Tim Peters tim-one for their inputs on how to
address this. Original issues reported by Yupeng and zed (lP: 1390262,
gh issues 57, 112, 249, 284, 286, prs 127, 225, 248, 264, 302).
Added new methods for working with ambiguous and imaginary dates to the tz
module. datetime_ambiguous() determines if a datetime is ambiguous for a given
zone and datetime_exists() determines if a datetime exists in a given zone.
This works for all fold-aware datetimes, not just those provided by dateutil.
(gh issue 253, gh pr 302)
Fixed an issue where dst() in Portugal in 1996 was returning the wrong value
in tz.tzfile objects. Reported by abalkin (gh issue 128, pr 225)
Fixed an issue where zoneinfo.ZoneInfoFile errors were not being properly
deep-copied. (gh issue 226, pr 225)
Refactored tzwin and tzrange as a subclass of a common class, tzrangebase, as
there was substantial overlapping functionality. As part of this change,
tzrange and tzstr now expose a transitions() function, which returns the
DST on and off transitions for a given year. (gh issue 260, pr 302)
Deprecated zoneinfo.gettz() due to confusion with tz.gettz(), in favor of
get() method of zoneinfo.ZoneInfoFile objects. (gh issue 11, pr 310)
For non-character, non-stream arguments, parser.parse now raises TypeError
instead of AttributeError. (gh issues 171, 269, pr 247)
Fixed an issue where tzfile objects were not properly handling dst() and
tzname() when attached to datetime.time objects. Reported by ovacephaloid.
(gh issue 292, pr 309)
/usr/share/lib/zoneinfo was added to TZPATHS for compatibility with Solaris
systems. Reported by dhduvall (gh issue 276, pr 307)
tzoffset and tzrange objects now accept either a number of seconds or a
datetime.timedelta() object wherever previously only a number of seconds was
allowed. (gh pr 264, 277)
datetime.timedelta objects can now be added to relativedelta objects. Reported
and added by Alec Nikolas Reiter (justanr) (gh issue 282, pr 283
Refactored relativedelta.weekday and rrule.weekday into a common base class
to reduce code duplication. (gh issue 140, pr 311)
An issue where the WKST parameter was improperly rendering in str(rrule) was
reported and fixed by Daniel LePage (dplepage). (gh issue 262, pr 263)
A replace() method has been added to rrule objects by jendas1, which creates
new rrule with modified attributes, analogous to datetime.replace (gh pr 167)
Made some significant performance improvements to rrule objects in Python 2.x
(gh pr 245)
All classes defining equality functions now return NotImplemented when
compared to unsupported classes, rather than raising TypeError, to allow other
classes to provide fallback support. (gh pr 236)
Several classes have been marked as explicitly unhashable to maintain
identical behavior between Python 2 and 3. Submitted by Roy Williams
(rowillia) (gh pr 296)
Trailing whitespace in easter.py has been removed. Submitted by OmgImAlexis
(gh pr 299)
Windows-only batch files in build scripts had line endings switched to CRLF.
(gh pr 237)
adamchainz updated the documentation links to reflect that the canonical
location for readthedocs links is now at .io, not .org. (gh pr 272)
Made some changes to the CI and codecov to test against newer versions of
Python and pypy, and to adjust the code coverage requirements. For the moment,
full pypy3 compatibility is not supported until a new release is available,
due to upstream bugs in the old version affecting PEP-495 support.
(gh prs 265, 266, 304, 308)
The full PGP signing key fingerprint was added to the README.md in favor of
the previously used long-id. Reported by valholl (gh issue 287, pr 304)
Updated zoneinfo to 2016i. (gh issue 298, gh pr 306)
fix issue70: added ability to copy all stat info in py.path.local.copy.
make TerminalWriter.fullwidth a property. This results in the correct
value when the terminal gets resized.
update supported html tags to include recent additions.
Thanks Denis Afonso for the PR.
Remove internal code in Source.compile meant to support earlier Python 3 versions that produced the side effect
of leaving None in sys.modules when called (see pytest-dev/pytest2103).
Thanks Bruno Oliveira for the PR.
coverage 4.0.3 -> 4.3.1
4.3.1
Some environments couldn'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.
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 issues
issue 525, issue 412, issue 516, and probably issue 511.
Coverage.py wouldn't execute sys.excepthook when an exception happened in
your program. Now it does, thanks to Andrew Hoos. Closes issue 535.
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 "coverage:", 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'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 "dataio" debug setting now also logs when data files are deleted during
combining or erasing.
A new debug option, "multiproc", for logging the behavior of
concurrency=multiprocessing.
If you used the debug options "config" and "callers" together, you'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.
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'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ä.
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 "clean" 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'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_.
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 ->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'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't change the behavior. This fixes issue 485_.
It'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_)
This is my first visit to this fine repo so I have bundled all updates in a single pull request to make things easier for you to merge.
Close this pull request and delete the branch if you want me to start with single pull requests right away
Here's the executive summary:
Updates
Here's a list of all the updates bundled in this pull request. I've added some links to make it easier for you to find all the information you need.
Changelogs
pytest-django 2.9.1 -> 3.1.2
pytest 2.9.1 -> 3.0.5
pytest-rerunfailures 2.0.0 -> 2.1.0
requests 2.10.0 -> 2.12.4
pip-tools 1.6.5 -> 1.8.0
python-dateutil 2.5.3 -> 2.6.0
py 1.4.31 -> 1.4.32
coverage 4.0.3 -> 4.3.1