We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
as shown in #14, we should cross-check that our tests agree with some reference CPython version (presumably, CPython-3.)
so we should probably put some wiring so that each test.py script is run with both gpython and cpython.
test.py
gpython
cpython
The text was updated successfully, but these errors were encountered:
That is what the py3test.py binary does.
It currently requires python 3.4 though maybe that should be relaxed to python3?
We should probably fix it and plumb it into the CI!
Sorry, something went wrong.
ah! :)
yes, we should probably do that.
I've implemented this in eaa7d28 (oops forgot the link to the issue).
No branches or pull requests
as shown in #14, we should cross-check that our tests agree with some reference CPython version (presumably, CPython-3.)
so we should probably put some wiring so that each
test.py
script is run with bothgpython
andcpython
.The text was updated successfully, but these errors were encountered: