Python venv en múltiples ventanas: Windows o Linux?

Have you ever wondered if Python virtual environments could run in parallel across multiple command windows on Windows? The answer is yes, but it opens up a much larger discussion about how operating systems handle file locking and user control.

The Philosophy of File Locking

This conversation reveals a fundamental clash between two operating system philosophies. Windows is fundamentally paternalistic; it operates on the premise that if a file is in use, no one else should touch it.

In contrast, Linux adopts an extreme libertarian approach. In Linux, you are allowed to delete or replace files even while they are being executed by another process. This isn’t negligence—it’s a conscious design choice that puts the responsibility on the user.

Why Windows Didn’t Parameterize Itself

The most revealing part of this discussion is why Microsoft never offered an option to change this behavior. The strong file locking in Windows isn’t a configurable policy; it’s embedded directly into the system contract, the API, and the filesystem design.

Windows didn’t parameterize itself because its primary users wanted predictability over power. Instead of trying to ‘loosen’ Windows without breaking its ecosystem, Microsoft made an honest decision: if you want Linux-like behavior, they give you a real Linux kernel in WSL2.

Conclusion

This isn’t just a technical debate; it’s about who is granted adulthood within the system. Windows protects against involuntary errors by locking files, while Linux respects conscious decisions to modify them. Both philosophies have their place, but neither would dominate both desktop and server environments simultaneously.