https://pantsbuild.org/ logo
#general
Title
# general
h

happy-kitchen-89482

12/13/2019, 7:16 PM
Hi all, quick bikeshed about where v2 plugins should live in the pants repo. See for context: https://docs.google.com/document/d/1E6a7nKq5Lf1G-VRS987ZT77KYkR5DT8JNxb9x4I4xEA/edit?usp=sharing
A logical place is
src/python/pants/backend
, which allows us to have a single source root, and use the obvious package prefix
pants.backend.
for v2 backends. However this ends up entangling the v1 and v2 backends at least in some cases (e.g., Python).
We could create a new source root
backends/src/python/pants/backend
, which is maybe a bit clunky.
Or we could come up with a new synonym for backend.
component
?
Renaming the existing
pants.backend
to
pants.backendv1
is possible, but requires deprecation and stuff. And seems like a hassle.
Or we could call these
pants.backend2
or something
Anyway, let the bikeshedding begin...
h

hundreds-father-404

12/13/2019, 7:25 PM
There’s also the problem of subsystems overlapping between V1 and V2, e.g. Isort and Pytest. If we want total isolation between the two, then we’d need to name one of them either
pytest1
or
pytest2
h

happy-kitchen-89482

12/13/2019, 7:44 PM
We can share subsystems via code imports, I think
We can allow v1 backends to depend on v2 backends
See discussion in doc
3 Views