We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead of only running Rust tests, we should also add jobs for running RustPythons (and Ruffs if there's the desire?) tests with every PR.
This will result in a larger wait time but should catch some confusing bugs, i.e RustPython/RustPython#4995
The text was updated successfully, but these errors were encountered:
I'd like to suggest to create tests using this test https://github.com/RustPython/Parser/blob/main/ast-pyo3/test_ast.py We don't need to run RustPython but still can test if the parser result is same as CPython.
Sorry, something went wrong.
Was thinking more along the lines of a subset, i.e test_grammar.py etc. Anything basically related to parsing would be nice to have.
test_grammar.py
If it's too much of a hassle, having at least something would definitely be good.
No branches or pull requests
Instead of only running Rust tests, we should also add jobs for running RustPythons (and Ruffs if there's the desire?) tests with every PR.
This will result in a larger wait time but should catch some confusing bugs, i.e RustPython/RustPython#4995
The text was updated successfully, but these errors were encountered: