-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Remove yield and compatprop #3898
Remove yield and compatprop #3898
Conversation
Codecov Report
@@ Coverage Diff @@
## features #3898 +/- ##
============================================
- Coverage 95.87% 95.82% -0.05%
============================================
Files 111 111
Lines 25258 25034 -224
Branches 2476 2462 -14
============================================
- Hits 24215 23990 -225
- Misses 733 735 +2
+ Partials 310 309 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, didn't even know yield tests were a thing -- I guess parametrize for the most part obsoletes them?
@asottile they where used for more than parameterization originally, but ever since collection and test running are not interleaved, they are severely broken wrt setupstate and no longer usable for anything that parameterize doesnt do better |
aedbe9f
to
085bd97
Compare
@RonnyPfannschmidt now that we have properly deprecated those, I believe it is easier to reject this PR and pick this up again after 4.1. 😁 |
i'll take a look in a bit wrt reenabling it - the warnings stuff has quite some conflicts but afterwards it should be clean to keep around |
Oh OK, sounds good! 👍 I will update the milestone to 4.1 then (which is when we will effectively remove the code). |
656f3a0
to
0b8c551
Compare
@nicoddemus ping |
94ac6e6
to
1875d59
Compare
1875d59
to
e8cc371
Compare
@nicoddemus i have no idea why the garbage collect test falls over |
Run test_request_garbage in a subprocess This test fails on occasion, and one suspicion is that some state from (Heh, my second commit today which changes a test to run in a subprocess 😁 ) |
py37 failed 😕 |
b8cd78c
to
e7b4b54
Compare
e7b4b54
to
5246f89
Compare
finally got around fixing - i missed that the test name change would change the filename below |
5246f89
to
7eb28f9
Compare
this pr removes a whole set of internal breakage by removing a broken feature as well as compat properties which are also deprecated since years, just impossibly hard to integrate with the warning system due to their bad_ structure