8000 Running Python test suite with checkout build requires command line. · Issue #280 · python/devguide · GitHub
[go: up one dir, main page]

Skip to content

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

Closed
Mariatta opened this issue Oct 12, 2017 · 4 comments · Fixed by #700
Closed

Running Python test suite with checkout build requires command line. #280

Mariatta opened this issue Oct 12, 2017 · 4 comments · Fixed by #700

Comments

@Mariatta
Copy link
Member
Mariatta commented Oct 12, 2017

In https://devguide.python.org/runtests/, it says:

If you don’t have easy access to a command line, you can run the test suite from a Python or IDLE shell

According to @Haypo in https://bugs.python.org/issue31761#msg304225 this is wrong, it should only be run in command line.

@Mariatta
Copy link
Member Author

@serhiy-storchaka mentioned that running tests from IDLE used to work, but not anymore since 2015.
I'm thinking that we should still update the devguide saying it doesn't work at the moment.
And then we should remember to update it again once bpo-25588 has been resolved..

@terryjreedy
Copy link
Member

'from test import autotest' also fails in a python shell, so merely removing 'or IDLE' may not be the right fix.
I will post to https://bugs.python.org/issue31761 when the already failing control run finishes.

@terryjreedy terryjreedy changed the title Python test suite should not be run from IDLE Running Python test suite with checkout build requires command line. Oct 19, 2017
@terryjreedy
Copy link
Member

'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.

@Mariatta
Copy link
Member Author

'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?

Added in 2011:

f3f0b7b#diff-c04a615d0a3d3ced3419675de9c0f66a

kumiDa added a commit to kumiDa/devguide that referenced this issue May 17, 2021
AA-Turner pushed a commit to AA-Turner/devguide that referenced this issue Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0