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.

Sign up for GitHub

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

Jump to bottom

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

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 davehunt mentioned this issue Jun 21, 2016
Closed
davehunt added a commit to davehunt/pytest that referenced this issue Jun 21, 2016
@davehunt
Introduce pytest command as recommended entry point
ef9dd14 
Fixes pytest-dev#1629
@davehunt davehunt mentioned this issue Jun 21, 2016
Merged
@davehunt
Copy link
Contributor Author

This was fixed in ef9dd14

RonnyPfannschmidt added a commit that referenced this issue Jun 22, 2016
@RonnyPfannschmidt
Merge pull request #1640 from Avira/features
a2420ce 
Add tests for entry points (#1629 )
This was referenced Aug 24, 2016
Closed
Closed
Merged
Merged
Closed
Closed
Closed
Merged
Closed
Merged
Closed
Closed
Merged
Closed
Merged
Closed
Merged
This was referenced Aug 31, 2016
Merged
Open
Open
Merged
Closed
Closed
Closed
@domdfcoding domdfcoding mentioned this issue Apr 15, 2020
Merged
bovee pushed a commit to bovee/Aston that referenced this issue Apr 17, 2020
@domdfcoding @bovee
Amend .travis.yml to test against Python 3.8, and to use the new 'pyt…
ffe3e37 
…est' syntax rather than 'py.test', as per pytest-dev/pytest#1629
Anthchirp added a commit to Anthchirp/bokeh that referenced this issue Jul 11, 2020
@Anthchirp
Change all occurrences of py.test to pytest
28fc636 
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629
@Anthchirp Anthchirp mentioned this issue Jul 11, 2020
Closed
Anthchirp added a commit to Anthchirp/bokeh that referenced this issue Jul 11, 2020
@Anthchirp
Change all occurrences of py.test to pytest
141717a 
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629

Resolves bokeh#10284
@Anthchirp Anthchirp mentioned this issue Jul 11, 2020
Merged
3 tasks
bryevdv pushed a commit to bokeh/bokeh that referenced this issue Jul 11, 2020
@Anthchirp
Change all occurrences of py.test to pytest (#10285)
eb1c210 
The 'pytest' command has been the recommended entry point since pytest 3.0,
cf. pytest-dev/pytest#1629

Resolves #10284
@afrubin afrubin mentioned this issue Jul 14, 2020
Merged
@jleveque jleveque mentioned this issue Aug 14, 2020
Merged
jleveque added a commit to sonic-net/sonic-mgmt that referenced this issue Aug 14, 2020
@jleveque
Replace all references of 'py.test' with 'pytest' (#2105)
00f36b5 
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
fix: Prefer pytest instead of py.test
655d950 
See pytest-dev/pytest#1629
@dashed dashed mentioned this issue Sep 28, 2020
Merged
dashed added a commit to getsentry/snuba that referenced this issue Sep 28, 2020
@dashed
fix: Prefer pytest instead of py.test (#1370)
808ce5b 
See pytest-dev/pytest#1629
xordoquy added a commit to pass-culture/pass-culture-api that referenced this issue Sep 30, 2020
@xordoquy
(PC-4518) : use pytest instead of py.test
4b1199d 
See pytest-dev/pytest#1629 (comment)
for details
@ydcjeff ydcjeff mentioned this issue Nov 28, 2020
Merged
@BoboTiG BoboTiG mentioned this issue May 3, 2021
Merged
jkbrzt pushed a commit to httpie/cli that referenced this issue May 3, 2021
Prefer usage of pytest rather than py.test (#1058)
7cbdf2c 
`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
@azzamsa azzamsa mentioned this issue Oct 24, 2021
Merged
@alvii147 alvii147 mentioned this issue Jan 31, 2022
Closed
@Kirade Kirade mentioned this issue Feb 3, 2022
Merged
corneliusroemer added a commit to corneliusroemer/cvxopt-feedstock that referenced this issue Nov 1, 2022
@corneliusroemer
MNT: py.test -> pytest
6d26ae9 
See pytest-dev/pytest#1629
Resolves conda-forge#65
@corneliusroemer corneliusroemer mentioned this issue Nov 1, 2022
Merged
5 tasks
martinandersen pushed a commit to conda-forge/cvxopt-feedstock that referenced this issue Nov 3, 2022
@corneliusroemer
MNT: py.test -> pytest (#67)
995e5c4 
* 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>
@xmatthias xmatthias mentioned this issue Nov 22, 2022
Closed
sean-reed added a commit to sean-reed/Django-Styleguide-Example that referenced this issue Feb 2, 2023
@sean-reed
Updated command to run pytest
ec896b5 
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
@sean-reed sean-reed mentioned this issue Feb 2, 2023
Merged
landonb added a commit to landonb/easy-as-pypi that referenced this issue May 20, 2023
@landonb
Improve: Convert py.test calls to pytest (Makefile, tox.ini)
0e90acf 
- Long time coming: `pytest` was introduced as recommended
  entry point on 2016-06-21:

    pytest-dev/pytest#1629
@rod-glover rod-glover mentioned this issue Dec 14, 2023
Merged
@cclauss cclauss mentioned this issue Dec 23, 2023
Merged
@itslychee itslychee mentioned this issue Feb 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@davehunt @The-Compiler @swiesend