Open TomasTomecek opened 6 years ago
Maybe when this happens, the stderr of the subprocess shall be printed by default.
That would be really helpful.
(I also don't understand why's requirements.txt
mandatory, but that's probably a different issue)
You try to create list of install_requires by reading them from requirements.txt in setup.py script. pyp2rpm runs setup.py extract_dist command in a subprocess to extract the metadata, so get_requirements
function is executed but requirements.txt
is not included in tarball.
You will get the same error if you try to runpip install .
after tarball extraction. In my opinion install_requires
should be listed explicitly in setup.py
or the requirements.txt
file has to be added to MANIFEST
.
(giant facepalm, that traceback indeed comes from my setup.py and the issue really was that I had to add requirements.txt into MANIFEST.in)
relevant lines from the setup.py:
def get_requirements():
with open("./requirements.txt") as fd:
return fd.readlines()
...
setup(
install_requires=get_requirements()
...
I tough you know this and are only reporting to pyp2rpm that the error in such case is nonobvious, which still stands. I'm renaming the issue accordingly.
Yup, that's my point: pyp2rpm doesn't make it clear enough that the problem is indeed in the package and that I'm a fool.
Ehm, that's not helpful.
So I tried
-s
switch and it produced more logs:Would it be possible to either provide better error message or log more by default?