pip install django y fijación de versiones

With your environment active, installing Django is one command. pip downloads it and every dependency it needs to run. 📦

After installing, check which version you got. Knowing the exact version helps you match docs and avoid surprises later.

Django evolves, and APIs change between releases. Pinning a version means your code runs the same way everywhere, today and next year.

You can ask pip for a specific release using double equals. This locks Django to exactly the version you tested with.

A requirements.txt file lists every package your project needs. Anyone can recreate your exact setup from this one file.

Let pip write the file for you. pip freeze lists installed packages with their exact versions, ready to save.

Inside, each line pins a package to a version. This pin guarantees the same install on every machine and server.

On a new machine, recreate everything at once. The -r flag tells pip to install each package listed in the file.

The ~= operator allows safe patch updates while blocking breaking ones, so you get fixes without nasty surprises.

Unlike the venv folder, you do commit requirements.txt to Git. It is small and lets teammates rebuild the exact environment.

Bump versions on purpose, then test. Edit the pin, reinstall, and run your app so upgrades never sneak in unnoticed.

Let's review pinning versions.

You installed Django, pinned an exact version, and froze it into requirements.txt for reproducible setups everywhere. Solid habits! 🎉