Closed djmitche closed 1 year ago
Ah, using a newer tox
helps with that error. Now, on both the system where I'm trying to do this work, and on a system where I've hacked on bugwarrior before, I see
py39-jira200: install_package> python -I -m pip install --force-reinstall --no-deps /usr/local/google/home/djmitche/tmp/bugwarrior/.tox/.tmp/package/2/bugwarrior-1.8.0.tar.gz
Processing ./.tox/.tmp/package/2/bugwarrior-1.8.0.tar.gz
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Traceback (most recent call last):
File "<string>", line 2, in <module>
File "<pip-setuptools-caller>", line 34, in <module>
File "/tmp/pip-req-build-neojrg5g/setup.py", line 4, in <module>
with open('VERSION') as version_file:
FileNotFoundError: [Errno 2] No such file or directory: 'VERSION'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
I suspect this is because something newer is doing a better job of isolating the build, and VERSION is not being included. Adding VERSION to MANIFEST.in
seems to fix that, and the tests run. However, they all fail because none of the test dependencies are installed.
Clearly something in the world has changed since September 2022, when things last landed in this repo -- and certainly since September 2021, when I last contributed. Is there someone with a more recent familiarity with Python who can update things to get them working again?
We have a tox.ini
so tox ought to work. But why use tox rather than just pytest? If it's just about testing the matrix, I say let CI catch those rare cases where it makes a difference.
Hm, that's true.
There are no actual test instructions that I saw, and I started with the old python setup.py test
, which suggested tox
. I see that the most recent commits include some more info in the contributing/getting-started.rst
file, including the all-important pip install -e .[all]
which gets all of the optional dependencies. I'll make a PR.
Maybe we should also have a CONTRIBUTING.md pointing to the contributing section of the docs?
I can add that in the PR..
Setup:
Result:
This is happening for all envs -- I've only included this one for brevity.
I've been away from Python packaging for a while, so this one has me stumped. Is this maybe a too-new version of setuptools or something like that? Are others seeing this, or is it likely something local to my environment?