OK, how do people feel about v2 backends being named

component

, 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.

we can’t name it

pants.python

,

pants.node

?

We could, but it's harder to avoid collisions with internal core code.

pants.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 detail

Seems arbitrary, but we could

Could we move all the core code into

pants.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)

If we were willing to make big breaking changes, I'd move existing

pants.backend

to

pants.backendv1

and keep it as

pants.backend.python

?

No

No, I’m asking what would the V2 name be if we used

pants.backendv1.python

but the v2 plugin could then reuse the name

pants.backend.python