<p>仓库文档解释了这个令人困惑的术语。以下引文来自<a href="https://warehouse.pypa.io/" rel="nofollow noreferrer">front page</a>和关于<a href="https://warehouse.pypa.io/api-reference/legacy/" rel="nofollow noreferrer">Legacy API</a>的页面:</p>
<blockquote>
<p>Warehouse is a <a href="https://github.com/pypa/warehouse" rel="nofollow noreferrer">web application</a> that implements the canonical <a href="https://packaging.python.org/glossary/#term-package-index" rel="nofollow noreferrer">Python package index (repository)</a>; its production deployment is <a href="https://pypi.org/" rel="nofollow noreferrer">PyPI</a>. It replaces an older code base that powered pypi.python.org.</p>
</blockquote>
<p/>
<blockquote>
<h1>Legacy API</h1>
<p>The “Legacy API” provides feature parity with <a href="https://pypi.python.org/" rel="nofollow noreferrer">pypi-legacy</a>, hence the term “legacy”.</p>
<p>...</p>
<h2>Upload API</h2>
<p>The API endpoint served at upload.pypi.org/legacy/ is Warehouse’s emulation of the legacy PyPI upload API. This is the endpoint that tools such as <a href="https://twine.readthedocs.io/" rel="nofollow noreferrer">twine</a> and <a href="https://docs.python.org/3.7/distutils/packageindex.html#the-upload-command" rel="nofollow noreferrer">distutils</a> use to <a href="https://packaging.python.org/tutorials/distributing-packages/" rel="nofollow noreferrer">upload distributions to PyPI</a>.</p>
</blockquote>
<p>换句话说,据我所知:</p>
<ul>
<li>PyPI曾经是托管在pypi.python.org. 这个不再运行的旧应用程序现在被命名为<em>pypilegacy</em>。在</li>
<li>PyPI现在是托管在pypi.org网站. 这个新的应用程序名为<em>Warehouse</em>。旧的pypi.python.org现在只是重定向到pypi.org网站. 在</li>
<li>除了一些新的端点之外,<em>Warehouse</em>仍然公开了一些<em>pypi legacy</em>曾经拥有的API端点。因为这些端点是从<em>pypi legacy</em>复制的,所以它们一起被称为“遗留API”。在</li>
<li>除此之外,<em>Warehouse</em>的遗留API中的上载端点是通过URL路径<code>/legacy</code>提供的,这一命名选择再次反映了这样一个事实:它是用于<em>pypi Legacy</em>中上载的端点的(部分)重新实现。在</li>
</ul>
<p>这一切看起来比实际情况更令人困惑,但事实就是如此。在</p>