You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
README says: $ python3 setup.py test but when this command is run it says:
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
running egg_info
writing python_gist.egg-info/PKG-INFO
writing dependency_links to python_gist.egg-info/dependency_links.txt
writing entry points to python_gist.egg-info/entry_points.txt
writing requirements to python_gist.egg-info/requires.txt
writing top-level names to python_gist.egg-info/top_level.txt
reading manifest file 'python_gist.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'python_gist.egg-info/SOURCES.txt'
running build_ext
----------------------------------------------------------------------
Ran 0 tests in 0.000s
OK
The text was updated successfully, but these errors were encountered:
Sorry, that should be updated. To run the unit tests you need to have poetry installed and run,
make test
whoops! nope, that isn't the case in master. As the warning above indicates, using python setup.py test is deprecated, so going forward that is not something that is going to be supported. At the moment, in master, you can need to create a virtual environment, install the test dependencies, and invoke the test via make,
python3 -m venv venv
source venv/bin/activate
pip install -r requirements-test.txt
make test
However, this is temporary because I am transitioning to using poetry to manage the dependencies in the future. Then it won't be necessary to explicitly create the virtual environment.
README says:
$ python3 setup.py test
but when this command is run it says:The text was updated successfully, but these errors were encountered: