Skip to content
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

Use unittest for testing instead of pytest #935

Merged
merged 2 commits into from
Nov 11, 2021

Conversation

srittau
Copy link
Collaborator

@srittau srittau commented Nov 11, 2021

No description provided.

Copy link
Collaborator

@hauntsaninja hauntsaninja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, can we leave a comment about being careful about doing any pip installs, just in case?

@srittau
Copy link
Collaborator Author

srittau commented Nov 11, 2021

Sure, where do you want the comment. In the yaml file?

Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>
@srittau srittau mentioned this pull request Nov 11, 2021
@hauntsaninja hauntsaninja merged commit 8fd49b5 into python:master Nov 11, 2021
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to also have an assertion in the unit test file to make sure we're picking up the right copy of the file (something like assert dirname(typing_extensions.__file__) == dirname(__file__).

It's going to be tricky for people testing the module locally to avoid picking up an installed copy, so it would be useful to provide this check and guidance like using an empty venv.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants