pydantic-cli VS python-dotenv

A comparison with https://github.com/mpkocher/pydantic-cli is welcome.

pydantic-cli

Also, the new type annotations/hints feature added to Python is an extremely useful mechanism to clearly communicate interfaces when leveraging functions as first class citizens. This can dramatically help readability and maintainability. Here's an example library designed leveraging functional centric concepts + type annotations.

Depending on the strictness level of adoption of mypy, this can sometimes (often?) requires changing how you write code. You can see some contortions here. However, having strict type analysis enables catching a lot of issues.

https://github.com/mpkocher/pydantic-cli#other-related-tools

I personally just use .env to keep api keys

similar to dotenv, I like this object oriented approach though.

Are you working on a Python project that uses pdm for dependency management and dotenv for local environment variable and secrets management? Do you find it frustrating when CLI tools like pgcli don't automatically pick up your .env file, forcing you to resort to npm install -g dotenv-cli? I've got a more convenient solution for you!

Similarly, I use python-dotenv which reads environment variables, or variables set in a .env file. Then in your settings.py file you can do things like:

Locally you may want to use a .env file that is also in .gitignore and python-dotenv to auto activate them. Also having an .env.template is also a good idea to help others working on the project know what they need to set in order for things to work.

But there's no web UI to set them for your local dev version. But there are various Python modules that will read environment variables from a file named .env. I like https://github.com/theskumar/python-dotenv myself. So try using that - create a .env file for your local dev site and use dotenv instead of os.getenv() to read the environment variables.

python-dotenv