Closed nealmcb closed 2 years ago
Thanks for the feedback! I have implemented your solution now so at least the system won't stumble over having no dependencies.
I agree that things should be made to work with only a pyproject.toml
instead of a setup.py
, especially as that's the recommended way for the future. I'm currently investigating if I can get importlib.metadata
to get to that info, without necessarily installing the entire package and all dependencies. I'd rather not reinvent the wheel and parse the toml manually.
I released v2.0.1 with the fix, closing this issue, the support for pyproject.toml is tracked separately in #17 now.
I'm trying to run codemetapy on my
rlacalc
Python package, and ran into two problems. Here they are, with workarounds for both of them.Based on this from the README:
I just tried running it in the root directory, which didn't work:
Since modern Python development often doesn't involve the dangerous process of running
setup.py
, I suggest adding the ability to parse apyproject.toml
file, and in the meantime, changing the README to say something more like "If you are in the current working directory of a python project with a setup.py, ..."So I switched to adding a package name, and that also failed:
That seems to be because I don't have a requirements file, nor any requirements beyond Python....
It works to guard the for loop in line 121 like this:
But I also wonder if
importlib
shouldn't make that an empty array instead ofNone
. So I'll leave the fix up to you.