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

This was fixed in ef9dd14

RonnyPfannschmidt added a commit that referenced this issue Jun 22, 2016
Add tests for entry points (#1629 )
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
jkbrzt pushed a commit to httpie/cli 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
corneliusroemer added a commit to corneliusroemer/cvxopt-feedstock that referenced this issue Nov 1, 2022
martinandersen pushed a commit to conda-forge/cvxopt-feedstock that referenced this issue Nov 3, 2022
* MNT: py.test -> pytest

See pytest-dev/pytest#1629
Resolves #65

* Bump build number

* MNT: Re-rendered with conda-build 3.22.0, conda-smithy 3.21.3, and conda-forge-pinning 2022.11.01.22.10.41

Co-authored-by: conda-forge-webservices[bot] <91080706+conda-forge-webservices[bot]@users.noreply.github.com>
sean-reed added a commit to sean-reed/Django-Styleguide-Example that referenced this issue Feb 2, 2023
pytest is the recommended way to run pytest since version 3.0, the old command of py.test may be deprecated in the future. See here: pytest-dev/pytest#1629
landonb added a commit to landonb/easy-as-pypi that referenced this issue May 20, 2023
- Long time coming: `pytest` was introduced as recommended
  entry point on 2016-06-21:

    pytest-dev/pytest#1629
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 8, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecetead
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 9, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecetead
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 13, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecetead
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 14, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecated
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 15, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecated
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 21, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecated
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 21, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecated
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 27, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test
It's possible that in future py.test will be deprecated
or potentially even removed [1]

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
slimreaper35 added a commit to slimreaper35/cachi2 that referenced this issue Aug 27, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test.

It's possible that in future py.test will be deprecated
or potentially even removed [1].

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
github-merge-queue bot pushed a commit to containerbuildsystem/cachi2 that referenced this issue Aug 27, 2024
From pytest 3.0 supported and recommended way is to use of pytest
as the main command instead of py.test.

It's possible that in future py.test will be deprecated
or potentially even removed [1].

---

[1]: pytest-dev/pytest#1629

Signed-off-by: Michal Šoltis <msoltis@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants