keyring

And also, when possible, try to use a key manager over environment variables. Using a library like keyring [1] is a significant step up from a .env file sitting in your dev environment. In other words: - Store secrets in settings.py (bad) - Store secrets in .env file (better) - Store secrets in OS-level key vault (even better) When the secrets are in a plaintext .env file, that file can get leaked in many non-obvious ways. Your antivirus uploads a copy, your IT department runs backups, someone on the team clones your git repo to a OneDrive/Dropbox folder and puts the .env file there. Then any of those services that has a leak, or any of the services those services use has a leak (improperly configured S3 bucket, etc), your secrets are leaked. [1] https://github.com/jaraco/keyring

There were 3 major pain points for me: * USB access is more difficult than just plugging something in. * Debugging tools like perf, RR, etc were either unsupported because they needed hardware counters or required custom builds (no system headers in apt to help either). * The VM takes a lot of disk space. The rest of the experience was fairly smooth. WSL2 can access the entire filesystem through /mnt/<drive letter>/. Windows -> WSL is a bit janky, but it works. GPU access is supported. Network access works. You can use a remote X session to get GUIs working, though you need to be comfortable with linux. Unfortunately having DISPLAY set caused pip to hang for long periods due to [1], but apparently that's been resolved. All in all, it mostly replaced my windows usage by the end. It's also a great workaround for legacy IT environments where