<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title>Strive2Code</title><subtitle>Blog author</subtitle><rights>© 2025</rights><updated>2026-03-07T06:46:00Z</updated><generator uri="https://strive2code.com">Moonglade v14.20.0</generator><entry><id>144ec63b-ba72-4d27-9e5f-8c04601e9192</id><title>Managing Python virtual environments</title><updated>2023-10-12T09:05:32Z</updated><published>2023-10-12T09:05:32Z</published><link href="https://strive2code.com/post/2023/10/12/managing-python-virtual-environments" hreflang="en-us" /><author><name>Alex K.</name><email>alex@strive2code.com</email></author><category term="Python" /><content>As a Python developer, managing multiple versions of Python and their associated packages can quickly become a headache, especially when working on different projects with varying dependencies. This is where virtual environments come into play, allowing you to create isolated Python environments for each project and ensuring smooth development without conflicts. In this post, we'll explore how</content></entry></feed>