Djangonaut Diaries: Week 1 — Setting the Stage (and the machine)

I am officially a Djangonaut ! Joining the latest cohort (Session 6) of the Djangonaut Space program is very cool, and it means it's time to contribute back to the framework that I love and have been working with daily for the last 3.5 years: Django. But, before I can start contributing with code, I need to get it running locally, setup a working local development environment and get its unit tests passing, to ensure that any future changes I make don't break something that I may not be aware of :D While doing this, I encountered a few issues that I had to figure out, and this blog post is to discuss a bit how I overcame these issues on my machine which runs Fedora 43. If you're using another Linux-based distro, like Ubuntu, most of the tips here will help as well, you will just have to replace the dnf command with apt . Step 0: Fork, clone and venv To send code back to Django as future Pull Requests, first I need to create a "fork" of Django, which is a copy of its repository at https