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

Introduce pytest command as recommended entry point #1629

Closed
davehunt opened this issue Jun 21, 2016 · 3 comments
Closed

Introduce pytest command as recommended entry point #1629

davehunt opened this issue Jun 21, 2016 · 3 comments

Comments

@davehunt
Copy link
Contributor

@davehunt davehunt commented Jun 21, 2016

It should be possible to run pytest using pytest command in addition to the existing py.test. This resolves a naming confusion that has existed for many years.

Explanation of py.test vs pytest from FAQ:

Some of the reasons are historic, others are practical. pytest used to be part of the py package which provided several developer utilities, all starting with py.<TAB>, thus providing nice TAB-completion. If you install pip install pycmd you get these tools from a separate package. These days the command line tool could be called pytest but since many people have gotten used to the old name and there is another tool named “pytest” we just decided to stick with py.test for now.

The issue with the 'other tool' has been resolved for some time now, so from pytest 3.0 we will supported and recommend use of pytest as the main command instead of py.test. It's possible that in future we will deprecate py.test and potentially even remove it.

@davehunt
Copy link
Contributor Author

@davehunt davehunt commented Jun 22, 2016

This was fixed in ef9dd14

@davehunt davehunt closed this Jun 22, 2016
RonnyPfannschmidt added a commit that referenced this issue Jun 22, 2016
Add tests for entry points (#1629 )
scop added a commit to scop/async_upnp_client that referenced this issue Mar 10, 2019
scop added a commit to scop/async_upnp_client that referenced this issue Mar 10, 2019
StevenLooman added a commit to StevenLooman/async_upnp_client that referenced this issue Mar 10, 2019
* Use pytest instead of py.test, #dropthedot

pytest-dev/pytest#1629 (comment)

* Run tests with warnings enabled
Mattwmaster58 added a commit to Mattwmaster58/pytest-timeout that referenced this issue Apr 10, 2020
bovee added a commit to bovee/Aston that referenced this issue Apr 17, 2020
Anthchirp added a commit to Anthchirp/bokeh that referenced this issue Jul 11, 2020
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629
Anthchirp added a commit to Anthchirp/bokeh that referenced this issue Jul 11, 2020
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629

Resolves bokeh#10284
bryevdv pushed a commit to bokeh/bokeh that referenced this issue Jul 11, 2020
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629

Resolves #10284
jleveque added a commit to Azure/sonic-mgmt that referenced this issue Aug 14, 2020
The `pytest` command has supplanted `py.test` as the recommended entry point since pytest 3.0. Replace all references in the repo.

Refer to: pytest-dev/pytest#1629
dashed added a commit to getsentry/snuba that referenced this issue Sep 28, 2020
dashed added a commit to getsentry/snuba that referenced this issue Sep 28, 2020
xordoquy added a commit to pass-culture/pass-culture-api that referenced this issue Sep 30, 2020
BoboTiG added a commit to BoboTiG/httpie that referenced this issue May 3, 2021
`py.test` was chosen over `pytest` but it is not planned for removal yet [1].
Anyway, it is a good thing to ensure we are using the correct Python version
with the right `pytest` installed, so using `python -m pytest` is recommended.

[1] pytest-dev/pytest#1629
jakubroztocil pushed a commit to httpie/httpie that referenced this issue May 3, 2021
`py.test` was chosen over `pytest` but it is not planned for removal yet [1].
Anyway, it is a good thing to ensure we are using the correct Python version
with the right `pytest` installed, so using `python -m pytest` is recommended.

[1] pytest-dev/pytest#1629
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants