Revert unrolling of all()#5373
Revert unrolling of all()#5373asottile merged 3 commits intopytest-dev:masterfrom asottile:revert_all_handling
all()#5373Conversation
nicoddemus
left a comment
There was a problem hiding this comment.
Thanks!
@Tadaboody feel free to pick this up again at a later time if you are interested in introducing this again. 👍
|
I can handle backporting of this one as well 👍 (the revert didn't apply cleanly so I imagine it'll have similar issues in 4.6-maintenance) |
Codecov Report
@@ Coverage Diff @@
## master #5373 +/- ##
==========================================
- Coverage 93.43% 60.04% -33.4%
==========================================
Files 114 56 -58
Lines 25528 11072 -14456
Branches 2482 2048 -434
==========================================
- Hits 23853 6648 -17205
- Misses 1353 3775 +2422
- Partials 322 649 +327
Continue to review full report at Codecov.
|
|
Oh... I've thought you reverted this only for 4.6. |
|
I propose never bringing this back at the ast level, there should be a difference approach |
[4.6] Merge pull request #5373 from asottile/revert_all_handling
|
So sorry about the fallout this created 🙏 I'll go back to the drawing board to see if this can be reintroduced in a better way. Reverting this was definitely the right decision, sorry I couldn't be more readily available to help with this |
|
@Tadaboody still thanks for trying, we now know that the approach as is isn't viable since quite a while there si the idea of assertion helper objects around, perhpas we should elaborate on it and its rammifications |
|
@Tadaboody not at all, as @RonnyPfannschmidt said, we appreciate you taking the time to implement this anyways! We should also have caught this earlier during review, but those things happen. 👍 |
|
@nicoddemus @asottile It seems that the pytest/src/_pytest/assertion/rewrite.py Lines 920 to 921 in 4f57d40 Was there any other PR merged on features with this |
|
ah yeah it's a little confusing, for the 5.x release we're just going to release from |
|
Yep, sorry for the confusion! |
Resolves #5370
Resolves #5371
Resolves #5372