happy-kitchen-89482
12/13/2019, 8:49 PMcomponent
, e.g., pants.component.python
, or unit
, e.g., pants.unit.python
? This helps avoid code confusion with existing v1 backends. Note that all these words are somewhat overloaded.hundreds-father-404
12/13/2019, 8:49 PMpants.python
, pants.node
?happy-kitchen-89482
12/13/2019, 8:53 PMpants.foo
is the foo plugin or some random core code relating to foo.hundreds-father-404
12/13/2019, 8:56 PMpants.backend.python
, pants.unit.python
, and python.component.python
all seem like a leaky abstraction to me as a user - the fact that it’s implemented in the backend is an implementation detailpantsbuild.python
, pantsbuild.node
?happy-kitchen-89482
12/13/2019, 9:38 PMsrc/python/pants
and src/python/pantsbuild
hundreds-father-404
12/13/2019, 9:40 PMpants.core
or pants_core
?
Your every day user who just wants to turn on functionality and not write new plugins would be able to active pants.python
, pants.node
Us Pants devs and any plugin authors would import pants.core
when adding new functionality
(I do realize this would be a majorly breaking change. Ignoring that for the moment to think about what design we’d use if we had zero legacy to support)happy-kitchen-89482
12/13/2019, 9:50 PMpants.backend
to pants.backendv1
hundreds-father-404
12/13/2019, 9:51 PMpants.backend.python
?happy-kitchen-89482
12/13/2019, 10:32 PMpants.backendv1.python
, which would be disruptivehundreds-father-404
12/13/2019, 10:32 PMpants.backendv1.python
happy-kitchen-89482
12/13/2019, 10:32 PMpants.backend.python