Load Environment Variables From .env Files in Python 

How does that function?

The choice of a configuration format for storing environment variables (or other configuration settings) depends on various factors, including ease of use, readability, and the specific needs of your application. .ini: Pros: Simple and Human-Readable: .ini files are straightforward to read and write. They use a plain text format with a simple key-value structure. Widely Supported: .ini files are supported by a wide range of programming languages and libraries, making them versatile for configuration. Cons: Limited Structure: .ini files lack complex data types, which can be a limitation for more advanced configuration needs. No Nested Structures: .ini files do not support nested structures, making it harder to organize complex configurations. .env (Environment Variables): Pros: Security: .env files are a secure way to store sensitive environment variables since they are typically not committed to version control. Platform-Agnostic: .env files are compatible with most platforms and languages, and they can be used in different development and deployment environments. Cons: Limited to Key-Value Pairs: .env files are limited to key-value pairs and don't support complex data structures. No Comments or Metadata: .env files lack the ability to add comments or metadata, making it harder to provide context for each variable. .toml: Pros: Rich Data Types: TOML supports a wide range of data types, including arrays, tables, and nested structures. Human-Readable: TOML is designed to be easy to read and write for humans. Comments: TOML allows comments, which can provide valuable context for each variable. Cons: Complexity: The richer data types in TOML can add complexity to the configuration, which may not be necessary for simple settings. .yaml (YAML): Pros: Highly Readable: YAML is known for its high readability and is often used for configuration files. Rich Data Types: YAML supports complex data structures, including lists and dictionaries, making it suitable for more complex configurations. Comments: Some YAML implementations support comments, providing context for variables. Cons: Indentation Sensitive: YAML relies on indentation for structure, which can be a source of issues when formatting is inconsistent. Potential Security Risks: Be cautious when using YAML for sensitive data, as it's not designed for security like .env files. In summary, the choice of format depends on your specific requirements. If you need a simple, human-readable format, .ini or .env might be suitable. If you need richer data types and nesting, TOML and YAML are better choices. Additionally, consider security, compatibility with your development stack, and whether comments and metadata are important for providing context in your configuration files.

I also did the same as in video but getting error like " Unresolved reference 'dotenv' "

I had a similar issue because I was trying to install: dotenv instead of python-dotenv

Nevermind I forgot to save the .env file

So do I, but I have to say that they are incredibly useful if your application can be run in a docker container because it's the easiest way to provide configuration in that situation

It's industry standard, especially when deploying workloads in containers/serverless

Yes, just like hello, hi, etc. are used by a lot of people. Does that mean that we should stop using those?