--test seems odd to me. I wonder if we should encourage naming their accounts, e.g.,

twine accounts add production --repository-url=https://pypi.org --username=username
password for {username}: ...

twine accounts add test --repository-url=https://test.pypi.org

twine accounts add work --repository-url=https://pypi.initrode.corp

I was trying to get to the minimal interface that wouldn't require changes to any other twine commands. Naming accounts would mean that twine upload would need to change to work with accounts instead of index URLs.

Naming accounts would mean that twine upload would need to change to work with accounts instead of index URLs.

Really? We couldn't just use the repository URL to index the accounts ... like we do today? .pypirc already has a way of managing accounts as it is.

I understand why labeling a endpoint/username pair with a short/descriptive name would be helpful. That said, because keyring uses endpoint/username pairs to lookup credentials, I don't know where the name of the account would exist. It seems that would require Twine to track that metadata.

This seems to have started though from adding a --test flag. There is discussion about turning down test in favor of staging on pypi.org so perhaps moving that out of the initial design, instead requiring a specific URL would make sense?

Closing this in favor of #216, but I think there are good ideas worth referencing here.