hey folks, I'm monkeying around with the `export` ...
# development
c
hey folks, I'm monkeying around with the
export
goal. I'm trying to use common machinery with
generate-lockfiles
for things like resolve detection and selection. A problem I hit is that the python lockfile rules are actually pretty far-reaching to many other backends. Does it make sense to also have export rules follow that? I think it does, in my head every resolve (even default ones for tools) should be exportable. The basic chain is
src/python/pants/backend/python/goals/lockfile.py
->
src/python/pants/backend/python/subsystems/setuptools.py
->
src/python/pants/backend/python/util_rules/
-> lots of stuff (dockerfile parser, helm k8s parser, awslambda rules, ...). So the lockfile rules are included mostly for pants-internal tools, but also semi-accidentally by being necessary to run setuptools which is used by everything.
(the problem is that putting the lockfiles in scope also puts the idea of a python export in scope and prevents the rule graph from closing unless the export rules are also registered. see https://github.com/pantsbuild/pants/pull/20487 for the WIP)