-
-
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
deprecate resultlog #830
Comments
Hmm I have never used it... could you explain the motivation for the plugin to exist in the first place and what pypy has to do with it? I kind of agree about it being difficult to parse... perhaps it would be better to produce the contents in something easier to parse, like JSON perhaps? Thanks! |
resultog is basically the first variant of semi-structured output of test results for later consumption it was created years before json was as well known as today pypy uses it for its execution result analysis these days a format like subunit or a general stream of json objects (one per line) seems far more helpful such a format could also be used for more detailed pytest debugging, (since trace items could be part of sucha stream without creating unwanted intersection) |
I see, thanks for the explanation! 😄 |
Should this be updated to |
Should we do this for 3.0 as it's backwards-incompatible but probably relatively straightforward? |
yes please |
Fixed in #1812 |
the format is incomplete and tricky to parse,
i propose deprecating it in 2.8 and scheduling full removal for when pypy uses something more modern
a more complete replacement will be proposed at a later point in time
The text was updated successfully, but these errors were encountered: