2016-06-07 22:45:59 +02:00
|
|
|
# This file is automatically generated by scripts/dev/recompile_requirements.py
|
|
|
|
|
|
2016-08-03 09:27:24 +02:00
|
|
|
beautifulsoup4==4.5.1
|
2016-07-25 22:59:28 +02:00
|
|
|
CherryPy==7.1.0
|
codeov/test requirements: Update coverage to 4.2
Version 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'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ä.
Version 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 "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.
- 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.
- A new configuration option, report:sort, controls what column of the
text report is used to sort the rows.
- The HTML report has a more-visible indicator for which column is being
sorted.
- 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.
- When reports are ignoring errors, there's now a warning if a file
cannot be parsed, rather than being silently ignored.
- A new option for coverage debug is available: coverage debug config
shows the current configuration.
- Running coverage as a module (python -m coverage) no longer shows the
program name as __main__.py.
- The test_helpers module has been moved into a separate pip-installable
package: unittest-mixins.
2016-07-27 06:37:02 +02:00
|
|
|
coverage==4.2
|
2016-06-07 08:24:53 +02:00
|
|
|
decorator==4.0.10
|
2016-06-07 23:26:04 +02:00
|
|
|
Flask==0.10.1 # rq.filter: < 0.11.0
|
2016-05-29 16:53:54 +02:00
|
|
|
glob2==0.4.1
|
|
|
|
|
httpbin==0.4.1
|
2016-07-13 20:21:20 +02:00
|
|
|
hypothesis==3.4.2
|
2016-05-29 16:53:54 +02:00
|
|
|
itsdangerous==0.24
|
2016-06-07 22:52:44 +02:00
|
|
|
# Jinja2==2.8
|
2016-05-29 16:53:54 +02:00
|
|
|
Mako==1.0.4
|
2016-06-07 23:10:33 +02:00
|
|
|
# MarkupSafe==0.23
|
2016-05-29 16:53:54 +02:00
|
|
|
parse==1.6.6
|
|
|
|
|
parse-type==0.3.4
|
|
|
|
|
py==1.4.31
|
2016-05-31 23:41:24 +02:00
|
|
|
pytest==2.9.2
|
2016-06-30 14:02:30 +02:00
|
|
|
pytest-bdd==2.17.0
|
2016-05-29 16:53:54 +02:00
|
|
|
pytest-catchlog==1.2.2
|
2016-08-08 15:20:04 +02:00
|
|
|
pytest-cov==2.3.1
|
2016-05-29 16:53:54 +02:00
|
|
|
pytest-faulthandler==1.3.0
|
|
|
|
|
pytest-instafail==0.3.0
|
2016-08-03 09:27:50 +02:00
|
|
|
pytest-mock==1.2
|
tox: Update pytest-qt to 2.0.0
See #1702.
Breaking Changes
With pytest-qt 2.0, we changed some defaults to values we think are much
better, however this required some backwards-incompatible changes:
- pytest-qt now defaults to using PyQt5 if PYTEST_QT_API is not set.
Before, it preferred PySide which is using the discontinued Qt4.
- Python 3 versions prior to 3.4 are no longer supported.
- The @pytest.mark.qt_log_ignore mark now defaults to extend=True, i.e.
extends the patterns defined in the config file rather than overriding
them. You can pass extend=False to get the old behaviour of overriding
the patterns.
- qtbot.waitSignal now defaults to raising=True and raises an exception
on timeouts. You can set qt_wait_signal_raising = false in your config
to get back the old behaviour.
- PYTEST_QT_FORCE_PYQT environment variable is no longer supported. Set
PYTEST_QT_API to the appropriate value instead or the new qt_api
configuration option in your pytest.ini file.
New Features
- From this version onward, pytest-qt is licensed under the MIT license.
- New qtmodeltester fixture to test QAbstractItemModel subclasses.
- waitSignal and waitSignals can receive an optional callback that can
evaluate if the arguments of emitted signals should resume execution
or not.
- Now which Qt binding pytest-qt will use can be configured by the
qt_api config option.
- While pytestqt.qt_compat is an internal module and shouldn't be
imported directly, it is known that some test suites did import it.
This module now uses a lazy-load mechanism to load Qt classes and
objects, so the old symbols (QtCore, QApplication, etc.) are no longer
available from it.
Other Changes
- Exceptions caught by pytest-qt in sys.excepthook are now also printed
to stderr, making debugging them easier from within an IDE.
2016-07-29 07:06:47 +02:00
|
|
|
pytest-qt==2.0.0
|
2016-08-09 20:53:37 +02:00
|
|
|
pytest-repeat==0.4.0
|
2016-05-29 16:53:54 +02:00
|
|
|
pytest-rerunfailures==2.0.0
|
2016-05-29 17:27:58 +02:00
|
|
|
pytest-travis-fold==1.2.0
|
2016-07-27 18:27:32 +02:00
|
|
|
pytest-warnings==0.1.0
|
2016-05-29 16:53:54 +02:00
|
|
|
pytest-xvfb==0.2.0
|
|
|
|
|
six==1.10.0
|
2016-07-14 23:17:39 +02:00
|
|
|
vulture==0.10
|
2016-05-29 16:53:54 +02:00
|
|
|
Werkzeug==0.11.10
|