Daniel Hahler
|
bfda2a0050
|
setup.cfg: use existing [tool:pytest] (ignoring [pytest])
|
2019-03-29 10:59:27 +01:00 |
Bruno Oliveira
|
9138419379
|
Remove support for '[pytest]' section in setup.cfg file
Fix #3086
|
2018-12-19 17:43:17 -02:00 |
|
Bruno Oliveira
|
fd48cd57f9
|
Remove config.warn, Node.warn; pytest_logwarning issues a warning when implemented
Fix #3078
|
2018-12-14 12:50:18 -02:00 |
|
Bruno Oliveira
|
33b877cc01
|
Merge remote-tracking branch 'upstream/master' into merge-master-into-features
|
2018-11-23 23:27:41 -02:00 |
|
Bruno Oliveira
|
aa765cf8c2
|
Adjust stacklevel of "config" warnings
Related to #4439
|
2018-11-22 14:44:01 -02:00 |
|
Daniel Hahler
|
ba457f5feb
|
Optimize/revisit determine_setup
|
2018-11-13 20:14:24 +01:00 |
Anthony Sottile
|
2368fbb63c
|
Apply reorder-python-imports to all files
|
2018-10-25 00:01:29 -07:00 |
|
Bruno Oliveira
|
da6830f19b
|
Introduce UnformattedWarning to keep warning types and messages in _pytest.deprecated
|
2018-09-14 14:49:05 -03:00 |
|
Bruno Oliveira
|
0fffa6ba2f
|
Implement hack to issue warnings during config
Once we can capture warnings during the config stage, we can
then get rid of this function
Related to #2891
|
2018-09-04 11:35:34 -03:00 |
|
Bruno Oliveira
|
78ac7d99f5
|
Deprecate Config.warn and Node.warn, replaced by standard warnings
|
2018-09-04 11:35:34 -03:00 |
|
Anthony Sottile
|
cbaa7dd56a
|
Upgrade pre-commit hooks except pyupgrade
|
2018-06-26 06:35:27 -07:00 |
Ronny Pfannschmidt
|
1459cbe01f
|
put config path finding and exceptions into own modules
|
2018-06-05 10:07:02 +02:00 |