e211d6fe2a
Merge pull request #6488 from blueyed/typing-fix-reportinfo
...
typing: Node.reportinfo: might return py.path.local via fspath
2020-01-17 11:52:01 +01:00
544b4a14d5
Fix Hugo van Kemenade name in release announcement
...
Co-Authored-By: Hugo van Kemenade <hugovk@users.noreply.github.com>
2020-01-17 07:18:57 -03:00
4a42deee7e
typing: Node.reportinfo: might return py.path.local via fspath
2020-01-17 11:05:46 +01:00
2cce026766
Merge pull request #6476 from blueyed/fix-test_config
...
Fix test_config: wrong assertions, lint, unused fixtures
2020-01-17 10:31:41 +01:00
e16cb2fdd0
Merge pull request #6444 from blueyed/fix-test_xfail_handling
...
tests: test_xfail_handling: use sys.dont_write_bytecode
2020-01-17 10:28:23 +01:00
dcb94d8f31
Merge pull request #6485 from blueyed/lint-fix-f999
...
scripts/release.py: lint: fix F999
2020-01-17 09:13:04 +01:00
19f66cb824
Merge pull request #6434 from blueyed/pytester-typing-spawn
...
pytester: typing for `spawn`/`spawn_pytest`
2020-01-17 06:57:40 +01:00
36944157f8
pytester: typing for `spawn`/`spawn_pytest`
2020-01-17 05:58:25 +01:00
2cfee583db
scripts/release.py: lint: fix F999
2020-01-17 05:54:17 +01:00
56dc301c50
Preparing release version 5.3.3
2020-01-16 18:55:41 -05:00
aa05334984
Remove broken link for user @jgsonesen
2020-01-16 18:51:33 -05:00
4806878a7f
Drop deploy from Travis in favor of GitHub actions ( #6480 )
...
Drop deploy from Travis in favor of GitHub actions
2020-01-16 18:34:44 -03:00
d1d7e5d41b
Drop deploy from Travis in favor of GitHub actions
...
GitHub actions already should deploy.
This is a stop gap while we figure out why coverage dropped
when removing Travis builds in #6470
2020-01-16 18:12:47 -03:00
5b0e255e85
Merge pull request #6465 from blueyed/doc-rootdir
...
doc: revisit section about rootdir
2020-01-16 21:55:12 +01:00
f0fdafeddc
Merge pull request #6477 from blueyed/tests-cleanup-unused-fixtures
...
tests: cleanup unused fixtures
2020-01-16 21:53:56 +01:00
5049e25a6a
tests: cleanup unused fixtures
2020-01-16 21:12:48 +01:00
d36c712bb0
Merge pull request #6479 from blueyed/tests-fix-master
...
[master] Use a dummy RemoteTraceback for test in Python 3.5 Windows
2020-01-16 21:12:04 +01:00
7a0d1b387d
Use a dummy RemoteTraceback for test in Python 3.5 Windows
...
Somehow in Python 3.5 on Windows this test fails with:
File "c:\hostedtoolcache\windows\python\3.5.4\x64\Lib\multiprocessing\connection.py", line 302, in _recv_bytes
overlapped=True)
OSError: [WinError 6] The handle is invalid
This only happens in this platform and Python version, decided to use
a dummy traceback as originally done in #6412 .
(cherry picked from commit b9c136b809
2020-01-16 20:03:16 +01:00
749752d440
Merge pull request #6435 from blueyed/type_checking
...
Use TYPE_CHECKING instead of False
2020-01-16 19:45:00 +01:00
118cb3d3be
Fix test_config: wrong assertions, lint, unused fixtures
2020-01-16 19:27:46 +01:00
b91c721262
ci: github actions: only deploy pytest-dev/pytest ( #6474 )
...
ci: github actions: only deploy pytest-dev/pytest
2020-01-16 12:48:29 -03:00
4630e2725e
Use `TYPE_CHECKING` instead of `False`
...
This allows for e.g. Jedi to infer types (it checks the name).
It was only used to support Python 3.5.0/3.5.1, where this is is not
available in the `typing` module.
Ref: https://github.com/davidhalter/jedi/issues/1472
Uses `TYPE_CHECKING = False` in `_pytest.outcomes` to avoid having to
work around circular import.
2020-01-16 16:11:39 +01:00
ea31649062
ci: github actions: only deploy pytest-dev/pytest
2020-01-16 13:57:46 +01:00
715f56dfbc
Fixtures now register finalizers with all fixtures before them… ( #6438 )
...
Fixtures now register finalizers with all fixtures before them in the stack
2020-01-16 07:33:55 -03:00
99180939fe
fixtures register finalizers with all fixtures before them in the stack
2020-01-15 11:00:42 -05:00
1ec5befdb7
Merge pull request #6468 from nicoddemus/deploy-release-notes-6369
...
Add deploy step: publish package and release notes
2020-01-15 09:05:23 -03:00
1d3f27cef0
Add deploy step: publish package and release notes
...
Fix #6369
2020-01-15 08:11:35 -03:00
29703a5f51
Merge pull request #6466 from blueyed/cover-safe_getattr
...
tests: cover safe_getattr
2020-01-15 11:20:42 +01:00
6f7a95c32e
tests: cover safe_getattr
2020-01-15 11:20:00 +01:00
bebfd28da3
doc: revisit section about rootdir
...
Ref: https://github.com/pytest-dev/pytest/issues/6376
2020-01-15 09:43:35 +01:00
f5844449a8
Merge pull request #6442 from blueyed/rP
...
terminal: summary_passes: handle teardown sections
2020-01-15 03:02:09 +01:00
4a265ba38b
Merge pull request #6446 from blueyed/tox-mypy
...
tox: add mypy toxenv
2020-01-14 18:26:35 +01:00
910d5df6a8
Merge pull request #6456 from blueyed/fix-doc-_splitnode
...
minor: fix doc/example for _pytest.nodes._splitnode
2020-01-14 15:22:01 +01:00
00adb4e42f
Implement code coverage in GitHub actions ( #6441 )
...
Implement code coverage in GitHub actions
2020-01-14 09:14:57 -03:00
b2cb87fae6
Merge pull request #6440 from blueyed/py351
...
ci: Travis: Python 3.5.1 via Trusty
2020-01-14 12:41:16 +01:00
189fe3ba1d
minor: fix doc/example for _pytest.nodes._splitnode
2020-01-14 12:40:36 +01:00
d291905825
Append token to codecov.yml instead of duplicating the file
2020-01-14 07:47:21 -03:00
f0c7f21312
Remove "pragma: no cover" comments
2020-01-14 09:15:36 +01:00
4ff7453b48
ci: Travis: Python 3.5.1 via Trusty
...
Python 3.5.0 caused flaky failures before
(https://github.com/pytest-dev/pytest/issues/5795 ).
This is pulled out of https://github.com/pytest-dev/pytest/pull/6435 ,
which adds code specific for Python < 3.5.2.
It only runs a specific test, while collecting everything to get
coverage of the version specific code around typing.
2020-01-14 09:15:36 +01:00
0e70acab79
tox: add mypy toxenv
...
This is different from what pre-commit (in "linting") runs in that it
uses stubs from (test) dependencies.
It would make sense to run this on CI additionally (since there is no
"pre-commit --skip mypy", and a separate config is not worth it).
But currently it triggers a false positive though anyway
(https://github.com/erikrose/more-itertools/pull/374 ).
2020-01-14 08:59:48 +01:00
8eec42f040
Merge pull request #6455 from blueyed/mypy-master
...
master: update mypy 0.740 -> 0.761
2020-01-14 08:56:51 +01:00
3adaa3d87b
Merge pull request #6447 from blueyed/fix-determine_setup
...
typing: fix _pytest.config.findpaths.determine_setup
2020-01-14 08:56:28 +01:00
090e260517
master: update mypy 0.740 -> 0.761
...
(cherry picked from commit 16ff9f591e4848bbdf9a
2020-01-14 06:31:41 +01:00
117072d64c
typing: fix _pytest.config.findpaths.determine_setup
2020-01-13 11:45:20 +01:00
90740007a8
Merge pull request #6445 from blueyed/tox-pre-commit-posargs
...
tox: linting: pass posargs
2020-01-12 21:17:14 +01:00
5e1c6ce630
tox: linting: pass posargs
2020-01-12 20:09:51 +01:00
a136111dcc
tests: test_xfail_handling: use sys.dont_write_bytecode
2020-01-11 23:05:12 +01:00
61d04d3084
terminal: summary_passes: handle teardown sections
...
Fixes https://github.com/pytest-dev/pytest/issues/2780 .
2020-01-11 21:58:19 +01:00
a3bc6df950
Implement code coverage in GitHub actions
...
This overwrites the `codecov.yml` file in the root of the repository with
`codecov-upstream.yml` file (which contains the code-cov token)´, so PRs
and branches on the repository can upload coverage.
Suggestion from here:
https://github.com/pytest-dev/pytest/pull/6421#issuecomment-571934112
Security concerns: the token might be misused, but only to upload bogus coverage
to `codecov.io`, so the team believe this is harmless. If we decide to fallback
from this decision , we just need to revoke the token.
Related to #6369
2020-01-11 12:21:20 -03:00
622995a501
Fix grammar in README ( #6427 )
...
Fix grammar in README
2020-01-09 20:22:05 -03:00
Daniel Hahler
Bruno Oliveira
Bruno Oliveira
Chris NeJame
Ran Benita