snapcraft 3.9.7+ ignores the petname Python package when referred to as a requirement in my Python part

[Pen Gale]

One of the Python tools that we build as part of the MicroStack path specifies petname in its requirements.txt.

When building with snapcraft 3.9.7+, petname is not added to the built snap. The part in question (launch) has not changed, and other Python packages specified in other parts' requirements do get added.

This is kind of an odd one, because I'm able to build a much simpler snap that contains petname, and I know that the snapcraft snap uses petname. Per today's conversations, I am working on getting more logging and info on this, and will post it at my earliest opportunity.

[Sergio Schvezov (sergiusens)]

This seems to be related to LP: #1860884 but nothing has changed in snapcraft for this to be triggered only now since our sitecustomize logic has remained static pretty much since 2017

[Pen Gale (pengale)]

Following up on this: I uploaded a build to latest/edge/missing-petname.

If you unsquashfs it, you'll note that petname is note in site packages, despite being called out in the requirements.txt for the tools/launch part (https://opendev.org/x/microstack/src/branch/master/tools/launch/requirements.txt)

[Sergio Schvezov (sergiusens)]

ok, seems that in the end https://github.com/snapcore/snapcraft/pull/2901 fixes this:

sergiusens@central-city:~/projects/snaps/microstack$ snapcraft --use-lxd --shell-after
...
Snapped microstack_stein_amd64.snap
snapcraft-microstack # find prime -name '*petname*'
prime/lib/python3.6/site-packages/petname
prime/lib/python3.6/site-packages/petname-2.6.dist-info
prime/bin/petname
snapcraft-microstack #

[Sergio Schvezov (sergiusens)]

Marking as dupe of the other bug. Suspicion is that reordering of how parts were built made python from the stage directory to be picked up which already had the sitecustomize which made it omit the petname from the part.