-
-
Notifications
You must be signed in to change notification settings - Fork 859
Running Python test suite with checkout build requires command line. #280
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
Comments
@serhiy-storchaka mentioned that running tests from IDLE used to work, but not anymore since 2015. |
'from test import autotest' also fails in a python shell, so merely removing 'or IDLE' may not be the right fix. |
'Running & Writing Tests' begins with "This document assumes you are working from an in-development checkout of Python". Can you tell from the git log when that was added, and by who? I wonder why it begins this section, rather than the document as a whole? If we take the statement as true, then the 'document' assumes that one works with a command line. Hence the alternative would be irrelevant and should be removed. The reason for its presence is that at one time, it was considered OK for someone with only installed Python, and in a restricted environment, to make contributions to Python on the tracker. Hence the alternative for running tests. Changing the contribution policy needs more discussion than us two. It is a somewhat separate issue that the alternative does not work. If the policy is that it should work, then we should try to fix it. If not, the statement, code snippet, and the module should all go. |
Added in 2011: |
Uh oh!
There was an error while loading. Please reload this page.
In https://devguide.python.org/runtests/, it says:
According to @Haypo in https://bugs.python.org/issue31761#msg304225 this is wrong, it should only be run in command line.
The text was updated successfully, but these errors were encountered: