Update README.rst to recommend pipx run or install #30
Conversation
This `pipx` approach is recommended in: * pytest-dev#28
README.rst
Outdated
|
|
||
| This puts an executable file in ``<python-root>/Scripts`` with *python-root* being the root folder of the | ||
| Python installation from which ``pip`` was run. | ||
| pipx install --python 3.11 nose2pytest@git+https://github.com/pytest-dev/nose2pytest |
There was a problem hiding this comment.
The reason I used the install from GitHub was to ensure that the issue I was encountering was not fixed at HEAD. Probably you still want to stick with installing from PyPI and just make sure releases are published there with any updates.
| pipx install --python 3.11 nose2pytest@git+https://github.com/pytest-dev/nose2pytest | |
| pipx install --python 3.11 nose2pytest |
There was a problem hiding this comment.
As discussed on #26, should we encourage pipx run instead of pipx install given the transitory nature of using this tool?
There was a problem hiding this comment.
Updated for pipx run --python 3.11 nose2pytest path/to/dir/with/python_files.
We will need to ensure there is a new release to PyPI. https://pypi.org/project/nose2pytest/
cclauss
changed the title
|
@schollii @nicoddemus Your reviews, please. |
There was a problem hiding this comment.
Thanks @cclauss!
The PR mentions a release to pypi, this is as simple as tagging the commit that is mentioned in github release page with "vVER" where is eg 3.10. Do you want to do this for 1.09, 1.10 and 1.11? I'm swamped between work and other projects so that would be hugely appreciated.
|
Btw @cclauss the "tag" step is meant to push the tag to |
|
Can someone without write permissions push a tag I am not a maintainer of this repo. |
This
pipxapproach is recommended in:Given that
fissixruns on Py3.12...Should
nose2pytestrun on Python 3.12?Should
nose2pytestrun on Python 3.13?Should the GitHub Actions tests for Python 3.6 and 3.7 be removed?
Can there be a new release to PyPI? https://pypi.org/project/nose2pytest/