PEP 771: Default Extras for Python Software Packages (Round 2)

[zanie (Zanie Blue)]

@ncoghlan

Continuing the default-extras vs default-optional-dependencies-keys topic from the previous thread: the optional-dependencies table is defined in the specification as " For optional-dependencies, it is a table where each key specifies an extra and whose value is an array of strings." (emphasis added).

While I agree that default-optional-dependencies-keys probably isn’t the final name we should use, I worry that default-extras is a step backwards.

I strongly agree with Pradyun’s comment, it’s well said.

While extras occurs in the documentation, the fact that it doesn’t occur in the configuration file itself is problematic. It will definitely be confusing to new users that default-extras controls the optional-dependencies.

I would really like for us to remain consistent here, unless there’s another way we can somehow emphasize the relationship between these fields to assuage these concerns.