Show user in password prompt (fixing regression)

[rolandwalker]

Description

It would seem that there was a regression in #1436, and we need to redo #1291.

In order to do this, we have to lose some special DSN logic. There is just no way under the current setup, since for instance the SSL params get parsed out of the DSN before calling connect().

Once solution could be to do all configuration parsing early, a long-term goal.

Here we replace the DSN fallthrough with a warning message.

The password_from_file logic is incidentally improved.

Checklist

• I've added this contribution to the changelog.md.
• I've added my name to the AUTHORS file (or it's already there).
• I ran uv run ruff check && uv run ruff format && uv run mypy --install-types . to lint and format the code.

[scottnemes]

I removed it on purpose because when prompting the user for a password at the start, the username is not yet known unless the --user/-u option is passed. So you'd have to move the config checks up higher, or it just shows None. But if that's what you want, then works as-is then anyway.

uv run mycli --password
Enter password for None:

uv run mycli -u scottn --password
Enter password for scottn:

mycli/mycli/main.py

Line 507 in a237ee9

user = user or cnf["user"] or os.getenv("USER")

[rolandwalker]

I see. We don't have cnf yet.

[scottnemes]

@rolandwalker Apologies for the back and forth on this. After working for a while to try and re-add the original password related functionality back into your change (while keeping the user in the prompt), I realized it could be done in a much simpler way (as far as I can tell anyway). I created a new PR with what I believe works, and included your updated password file logic. I believe that was the only other thing that you added (other than the import re-organization, I added that as well). But if I missed something let me know:

#1502

[rolandwalker]

Closing in favor of #1502 .