I'm on my next step to extend

pants

usage at my client, publishing changed libraries automatically 🙂 I had in mind to use

--changed-since

and

package

for that. But I can't achieve to have

pants

build the changed libraries. Consider this example trying to build our

geometry

library: Here are the library's direct dependencies:

→ ./pants dependencies libs/geometry:kaiko-geometry-dist
libs/geometry/kaiko/geometry/__init__.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/_point_utils.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/geometry_box.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/geometry_point.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/geometry_polygon.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/geometry_size.py:../../kaiko-geometry
libs/geometry/kaiko/geometry/geometry_square.py:../../kaiko-geometry

I have modified a file of the library in the last commit (added a print):

→ git diff --name-only HEAD~1
libs/geometry/kaiko/geometry/geometry_polygon.py

The library has a

python_distribution

stanza:

→ grep -A 2 python_distribution libs/geometry/BUILD 
python_distribution(
    name="kaiko-geometry-dist",
    dependencies=[":kaiko-geometry"],

So I am expecting this command would create the library's wheel:

→ ./pants --changed-since=HEAD~2 --changed-dependees=direct --filter-target-type=python_distribution package

but it leaves

dist/

empty 😞 (whereas

./pants --filter-target-type=python_distribution package ::

does generate the concerned library's wheel). What am I misunderstanding/doing wrong?

Nothing wrong really, you just hit a tricky corner. See: + https://pantsbuild.slack.com/archives/C046T6T9U/p1670519542190369?thread_ts=1670519542.190369&cid=C046T6T9U + https://github.com/pantsbuild/pants/issues/14243