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

Pants

What does the backend `pants.backend.experimental` signify? Does it mean the features provided by this backend are in “experimental” stage and may be removed in future?

We've been discussing a better name for that this week. Thus far, we haven't removed any functionality and don't really plan to. Instead, it more means "some features may be missing and we may have to make some API changes"

For example, we have `pants.backend.experimental.python.fmt.pyupgrade`, which currently runs with the `fmt` goal but we realize should be a new `fix` goal. Once we make that change, it will be stabilized

Which backends in particular are you curious about? I'm happy to explain what's not yet stable about them. (One idea we have is to create tracking issues for each backend, like what Rust does)

`pants.backend.experimental.python`
`pants.backend.experimental.python.lint.autoflake`

Autoflake is going to soon move from `fmt` to `fix`. Otherwise it's stable

`experimental.python` has 2 features it looks like: the `publish` goal with Twine and the `vcs_version` target from <https://www.pantsbuild.org/v2.13/docs/generating-version-tags>