Open rrthomas opened 2 months ago
Just to check that it's not the particularity of one project, I tried with https://github.com/rrthomas/rpl and had the same problem. (I appreciate that this is another of my projects, so it could still be something I'm doing wrong!)
Thank you for the report. Indeed, this seems like something everyone wants to do when using pyproject+argparse-manpage.. but I don't understand why this is happening.
It seems that psutils
is not on the PYTHONPATH. Could setup.py
implicitly add the current working directory there, but that's not done by pyproject?
How do you execute the build?
I use python -m build
. My diagnosis of the immediate problem is the same as yours, and like you I speculated that the path was being set up differently in the two cases; I've not yet had time to probe further.
I am trying to switch from an old
setup.py
setup to purepyproject.toml
(thanks for making this possible!) for PSPDFUtils.The commands I'm trying to make man pages for are standard entry points in my package. With
setup.py
this works fine; with purepyproject.toml
, I get this error:As we can see, it's not finding
psutils
. I'm not sure why it works with thesetup.py
setup but notpyproject.toml
.I'm sorry if this isn't an argparse problem, but it seemed to me that it would be a fairly common problem (that is, wanting to use argparse to make man pages for scripts that require the current package), and I can't see anything in the argparse documentation about it.