<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Environment on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/environment/</link><description>Recent content in Environment on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 10 Apr 2022 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/environment/index.xml" rel="self" type="application/rss+xml"/><item><title>Python Engineering (1): Environment Setup — pyenv, venv, and Dependency Hell</title><link>https://www.chenk.top/en/python-engineering/01-environment-and-toolchain/</link><pubDate>Sun, 10 Apr 2022 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/python-engineering/01-environment-and-toolchain/</guid><description>&lt;p>Every Python developer has lived through this moment: you run a script on your colleague&amp;rsquo;s machine and it crashes because they have Python 3.8 while you wrote it on 3.11. Or worse, you &lt;code>pip install&lt;/code> something globally and break a completely unrelated project. Python&amp;rsquo;s environment story is powerful once you understand it, but the default experience is a minefield.&lt;/p>
&lt;p>This article walks through the entire toolchain from scratch. By the end, you&amp;rsquo;ll have a reproducible, isolated, and version-pinned setup that works the same way on every machine.&lt;/p></description></item></channel></rss>