python-dotenv VS quote

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

A surprising source of slow compile times can be declarative macros in Rust [0].

I believe the core of the problem is that it has to reparse the code to pattern match for the macro.

One egregious patter is tt-munchers [1] where your macro is implemented recursively, requiring it to reparse the source on each call [2].

In one of my projects, someone decided to wrap a lot of core functions in simple macros (ie nt tt-munchers) to simplify the signatures. Unlike most macros which are used occasionally and have small inputs, this was a lot of input. When I refactored the code, I suspect dropping the macros is the reason CI times were cut in half and a clean `cargo check` went from 3s to 0.5s.

[0]: https://nnethercote.github.io/2022/04/12/how-to-speed-up-the...

[1]: https://veykril.github.io/tlborm/decl-macros/patterns/tt-mun...

[2]: https://github.com/dtolnay/quote/blob/31c3be473d0457e29c4f47...

In the build.rs, call your code generation function (probably in a separate crate added in build-dependencies). This function will read your input files, and use something like quote to generate code.

Or you can pair them with crates like syn, and quote for quasi-quoting, and then it's easy to make transformations on the AST of Rust input code. A lot of libraries do this for code-generation and hiding away a lot of complexity (example wasm-bindgen).