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
In case of the wheel file there's no problem as it's compiled binary with specified dependencies. Setup.py has been already evaluated while building a wheel.
However when pip falls back to sdist file due to incompatible binary file. setup.py will be dynamically evaluated and you can't assume a user to have pipfile installed in order to parse the pipfile.lock. btw Pipfile.lock isn't packaged into your distribution either.
This is what happens:
computer:~$ python3 -m pip install ./mutapath-0.9.0.tar.gz
Processing ./mutapath-0.9.0.tar.gz
ERROR: Complete output from command python setup.py egg_info:
ERROR: Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-req-build-6trezlyr/setup.py", line 34, in <module>
install_requires=get_dependencies(),
File "/tmp/pip-req-build-6trezlyr/setup.py", line 11, in get_dependencies
lock_data = json.load(pipfile_lock.open())
File "/usr/lib/python3.7/pathlib.py", line 1186, in open
opener=self._opener)
File "/usr/lib/python3.7/pathlib.py", line 1039, in _opener
return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: 'Pipfile.lock'
----------------------------------------
ERROR: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-6trezlyr/
The only way to resolve this is to write pipfile parsing code with built-in dependencies and add Pipfile to your package_data keyword in setup.py
Or you can use my pipenv-setup and give me some feature requests if you have any ;)
The text was updated successfully, but these errors were encountered:
Hi @Madoshakalaka
Thank you for your feedback, I also noticed that the CI didn't build.
I tried various approaches to make it work and decided to read the Pipfile.lock in the setup.py.
After all, I also needed Dependabot to be compatible and even though Dependabot is able to recognize the setup.py, it doesn't accept both Pipfile and setup.py. It only pushes updates for one of both. Pre-commit hooks don't help there either.
Feel free to check, if you still see any issues with the setup.
Hi I'm the author of pipenv-setup. I checked who's been using my thing and I got nosy :)
Have to say your current
setup.py
has problems with it.https://pypi.org/project/mutapath/#files
You're building sdist (.tar.gz) and wheels.
In case of the wheel file there's no problem as it's compiled binary with specified dependencies. Setup.py has been already evaluated while building a wheel.
However when pip falls back to sdist file due to incompatible binary file. setup.py will be dynamically evaluated and you can't assume a user to have
pipfile
installed in order to parse thepipfile.lock
. btwPipfile.lock
isn't packaged into your distribution either.This is what happens:
The only way to resolve this is to write pipfile parsing code with built-in dependencies and add Pipfile to your
package_data
keyword in setup.pyOr you can use my pipenv-setup and give me some feature requests if you have any ;)
The text was updated successfully, but these errors were encountered: