<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Uv Workspace on Han's XYZ</title><link>https://han8931.github.io/tags/uv-workspace/</link><description>Recent content in Uv Workspace on Han's XYZ</description><generator>Hugo</generator><language>en</language><managingEditor>tabularasa8931@gmail.com (Han)</managingEditor><webMaster>tabularasa8931@gmail.com (Han)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 08 Dec 2025 19:42:41 +0900</lastBuildDate><atom:link href="https://han8931.github.io/tags/uv-workspace/index.xml" rel="self" type="application/rss+xml"/><item><title>uv workspace: effective management of Python apps</title><link>https://han8931.github.io/uv-packages/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><author>tabularasa8931@gmail.com (Han)</author><guid>https://han8931.github.io/uv-packages/</guid><description>&lt;h2 id="understanding-uv-workspaces"&gt;Understanding uv Workspaces&lt;/h2&gt;
&lt;p&gt;The official uv website explains workspaces very clearly:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Inspired by Cargo, a &lt;em&gt;uv workspace&lt;/em&gt; is a collection of one or more Python packages (workspace members) managed together in a single repo. Each package has its own &lt;code&gt;pyproject.toml&lt;/code&gt;, but the workspace shares one &lt;code&gt;lockfile&lt;/code&gt;, keeping dependencies consistent across apps and libraries. Commands like &lt;code&gt;uv lock&lt;/code&gt; operate on the whole workspace, while &lt;code&gt;uv run&lt;/code&gt; and &lt;code&gt;uv sync&lt;/code&gt; default to the workspace root but can target a specific member via &lt;code&gt;--package&lt;/code&gt; &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description></item></channel></rss>