<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipenv on Alex_Tech_Blog</title><link>https://alex.dinnouti.com/tags/pipenv/</link><description>Recent content in Pipenv on Alex_Tech_Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 12:00:00 -0400</lastBuildDate><atom:link href="https://alex.dinnouti.com/tags/pipenv/index.xml" rel="self" type="application/rss+xml"/><item><title>Python environments</title><link>https://alex.dinnouti.com/posts/2020-12-02_09-23-25_python/</link><pubDate>Wed, 02 Dec 2020 09:23:25 -0500</pubDate><guid>https://alex.dinnouti.com/posts/2020-12-02_09-23-25_python/</guid><description>&lt;p&gt;This post is a self-service cheat sheet for Python environment and version management. One of the biggest problems with virtual environments in Python is the multiple tools available and how they play together.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Updated October 2026.&lt;/strong&gt; I wrote the first version in 2020 using pyenv and venv. I reviewed it because my usage changed: today I use &lt;strong&gt;uv&lt;/strong&gt; for new work and &lt;strong&gt;pipenv&lt;/strong&gt; for the older projects, and I do not mix them in the same project. Some of the old content was also outdated, for example pipenv no longer installs Python by itself. The old pyenv + venv setup is kept at the end.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>