Skip to content

Merge the features branch to master, before deleting features #6642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 128 commits into from

Conversation

bluetech
Copy link
Member

Part of #6571 transition plan. This step merges features into master, after which the features branch will be deleted.

blueyed and others added 30 commits November 10, 2019 00:21
Fixes pytest-dev#5991
Fixes pytest-dev#3823

Ref: pytest-dev/pytest-django#772
Ref: pytest-dev#1890
Ref: pytest-dev/pytest-django#782

- inject wrapped testMethod

- adjust test_trial_error

- add test for `--trace` with unittests
- Isolate logic for getting expected exceptions
- Use original method name, as users see it when entering the debugger
Otherwise 'normal' failures won't call teardown explicitly
This feature was added in commit
007a77c, but was never used in pytest
itself. A GitHub code search doesn't find any users either (only pytest
repo copies). It seems safe to clean up.
minor: move internal _pformat_dispatch function
testing/python/metafunc.py: import _idval once
Fixes pytest-dev#759

- Adjust test_parametrized_ids_invalid_type, create list to convert tuples
  Ref: pytest-dev#1857 (comment)

- Changelog for int to str conversion
  Ref: pytest-dev#1857 (comment)
Respect --fulltrace with collection errors
parametrized: ids: support generator/iterator
Add type annotations to _pytest.config.argparsing and corresponding Config code
Resolves pytest-dev#4445 and pytest-dev#5928 (thanks to allanlewis)

Add CHANGELOG for location parameter
pytester: remove special handling of env during inner runs
…st-dev/pytest/pytest-dev#4445

Add acceptance tests for "config warnings" stacklevel (pytest-dev#4445)
_idval: remove trailing newline from exception
Sets `PY_COLORS=0` in the environment by default, which is used by pylib.

Via blueyed#58

(initially cherry picked from commit f153ad3)
pytester: use no colors with inline runs by default
blueyed and others added 23 commits January 22, 2020 19:32
Clear node collection cache after collection is done
Conflicts:
	src/_pytest/_code/code.py
	src/_pytest/main.py
Previously, _initialparts was a list whose first item was a
`py.path.local` and the rest were `str`s. This is not something that
mypy is capable of modeling. The type `List[Union[str, py.path.local]]`
is too broad and would require asserts for every access.

Instead, make each item a `Tuple[py.path.local, List[str]]`. This way
the structure is clear and the types are accurate.

To make sure any users who might have been accessing this (private)
field will not break silently, change the name to _initial_parts.
Refactor Session._initialparts to have a more explicit type
Previously, this cache was used with 3 different and mutually exclusive
key-type -> value-type combinations. Mypy can't properly type this. It's
also quite confusing.

Split to 3 different dicts instead.
Split Session._collection_node_cache to 3 mutually exclusive parts
Adds handling of `N` to reset `reportchars`, which can be used to get
the old behavior (`-rN`), and also allows for an alternative to
`--disable-warnings` (pytest-dev#5066),
since `w` was included by default (without `--disable-warnings`).

Fixes pytest-dev#6454
terminal: default to `fE` with `-r` (reportchars)
…rize_nodeid

Fix node ids which contain a parametrized empty-string variable
Fix 6341 disallow session config in fromparent
Merge master to features - one last time
@bluetech
Copy link
Member Author

Pending decision on @blueyed's concern in #6571 (comment).

Copy link
Contributor

@blueyed blueyed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to express my concern I am requesting changes (#6571 (comment)).
This can be overruled of course, but I will certainly not approve it myself.

@blueyed
Copy link
Contributor

blueyed commented Jan 31, 2020

@bluetech I think this is not really necessary for the transition anyway, but only before the next release, isn't it?
We need to decide also still if "features" or another branch gets used then, with node-from-parent removed/replaced.
See #6571 (comment).
Let's close this here for now.

@bluetech bluetech closed this Jan 31, 2020
@bluetech bluetech deleted the features-to-master branch February 28, 2020 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants