Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

hm what's the convention to follow when you want to have two plugins to access a shared piece of code?

```❯ tree pants-plugins           
pants-plugins
├── common
│   ├── configuration.py
│   ├── __init__.py
├── pluginA
│   ├── code.py
│   ├── __init__.py
├── pluginB
│   ├── code.py
│   ├── __init__.py```
I'd like to be able to do `from common.configuration import X` in the `pluginA/code.py`. I see that in Pants, there's a subpackage `internal_plugins` so that your imports become `from internal_plugins.common......`

```❯ tree pants-plugins -L 2 
pants-plugins
├── internal_plugins
│   ├── __init__.py
│   ├── __pycache__
│   ├── releases
│   ├── rules_for_testing
│   └── test_lockfile_fixtures
└── README.md

5 directories, 2 files```
Is it what everyone else is doing?