Open amotta opened 5 years ago
Does it work if you run python setup.py install
?
Yes, that works.
Isn't that the idiomatic way to install Python packages locally? The readme also references that.
Hmm, I don't really know. But the documentation of Python 3.8 doesn't even mention python setup.py install
.
In fact, it says that "pip
is the preferred installer program. Starting with Python 3.4, it is included by default with the Python binary installers."
And pip install .
is listed for "installing from local source tree:
https://packaging.python.org/tutorials/installing-packages/#installing-from-a-local-src-tree
This is a bug in setuptools-scm
, see https://github.com/pypa/setuptools_scm/issues/357
The Python ecosystem is a bit foreign to me. So, all of the following could be wrong.
It seems that python setup.py install
and pip install .
are not equivalent:
python setup.py install
seems to delegates to easy_install, which does not properly handle pre-release versions on PyPI. Right now, the latest version of NumPy available via PyPI is 1.20.0rc1, which is a pre-release version that requires at least Python 3.7. When calling python setup.py install
in an environment with Python 3.6, this fails with a RuntimeError: Python version >= 3.7 required.
.
This seems wrong:
If I understand correctly (see link above), then pip install .
would not pull in the pre-release version. But pip install .
throws an error because of the bug linked by Norman.
As a result, it is impossible to locally install the the wkw package, right now.
Should we
python setup.py install
from pulling in pre-release versions), orpip install .
by getting rid of setuptools-scm
?With my limited knowledge of the Python ecosystem, I'd be in favor of the last option.
What do you think?
CC @valentin-pinkau
Running
fails with
when run from within a clean Conda environment based on Python 3.7.
Assigning to @normanrz and @philippotto based on the changelog of
setup.py
.