Is there a way to see the generated `setup.py` fil...
# general
f
Is there a way to see the generated
setup.py
file from the
python_distribution
target? I tried
--keep-sandboxes=always
but nothing I saw had the
setup.py
in it. I’m just experimenting with some changes and it’d be easier to inspect the file than rebuild and reinstall
c
What I’ve done in the past is to
./pants package <dist target>
then unzip the wheel from the dist folder for inspection..
💯 2
f
I’m interested in generating a
pyproject.toml
file, instead of the
setup.py
, so I’d like to be able to see the generated file as I work through some changes in pants itself. That way I can get to understand what pants is doing by making sure I understand the changes 🙂
👍 2
find /private/var/folders/zj/p64fbz8d6nd6st_w625_cf7r0000gq/T -iname 'setup.py'
😄
find /private/var -regex '.*pants-sandbox.*setup\.py' 2>/dev/null || true
h
Hmm
--keep-sandboxes=always
should work
Pants prints out the path to every sandbox, it should be possible to see from that log which is the relevant one?
f
Sorry, that
find
incantation did … find… the file. I didn’t see that path in the output, but I’ll check again on Monday 🙂
OK, can confirm that the sandbox is listed, the task is
Run setuptools.build_meta for <target>