–expect is specified, those numbers match your stated expectations). If run without any arguments, check-python-versions will look for a setup.py inĮxit status is 0 if all Python packages had consistent version numbers (and, if dry-run verify proposed changes without writing them to disk update VERSIONS update the set of supported versions, e.g. drop VERSIONS drop these versions from supported ones, e.g -drop add VERSIONS add these versions to supported ones, e.g -add 3.9 Updating supported version lists (EXPERIMENTAL): only FILES check only the specified files (comma-separated list, skip-non-packages skip arguments that are not Python packages without expect VERSIONS expect these versions to be supported, e.g. version show program's version number and exit h, -help show this help message and exit Where directory where a Python package with a setup.py and Verify that supported Python versions are the same in setup.py, tox.ini, Install it with python3 -m pip install check-python-versions Usage $ check-python-versions -help You need Python 3.6 or newer (f-strings!) to run check-python-versions. You if they don’t match $ check-python-versions ~/projects/* The solution: check-python-versions will compare these lists and warn Keeping all these lists consistent is a pain. Python_requires=”>= 2.7, !=3.0.* …” because AFAIU PyPI classifiers are You probably also want to tell pip which versions you support by specifying Trove classifiers like “Programming Language :: Python :: 2.7” You have to tell the users which Python versions you support by specifying If you’re building manylinux wheels you need to … you get the idea If you support Windows, you need an appveyor.yml with %PYTHON% set to You need a tox.ini with envlist = py27, p圓6, p圓7, p圓8, p圓9 Currently I do not know why, but maybe it is different on your system.This is a tool for Python package maintainers who want to explicitly state What's strange in my answer is that package 'wsgiref' is visible inside the virtualenv. Running setup.py install for commandlineapp Installing collected packages: commandlineapp Running setup.py egg_info for package commandlineapp ~/Projects/demoenv2.7$ bin/pip install commandlineappĭownloading CommandLineApp-3.0.7.tar.gz (142kB): 142kB downloaded New python executable in demoenv2.7/bin/python2.7Īlso creating executable in demoenv2.7/bin/python Running virtualenv with interpreter /usr/bin/python2.7 ~/Projects$ virtualenv -p /usr/bin/python2.7 demoenv2.7 Or just activate the virtualenv (source YOUR_ENV/bin/activate) as a convenient way to call the proper commands for python interpreter or pip ~/Projects$ virtualenv -version Next, make sure you use pip command provided inside the virtualenv ( YOUR_ENV/bin/pip). This way the purpose of using virtualenv is to create a python environment without access to packages installed in system python. Make sure to use a recent version of virtualenv that uses option -no-site-packages by default. Calling pip command inside a virtualenv should list the packages visible/available in the isolated environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |