docs: update links to relocated PyPI documentation

docs/cli.md

@@ -949,7 +949,7 @@ poetry search requests pendulum
 PyPI no longer allows for the search of packages without a browser. Please use https://pypi.org/search
 (via a browser) instead.
 
-For more information, please see [warehouse documentation](https://warehouse.pypa.io/api-reference/xml-rpc.html#deprecated-methods)
+For more information, please see [PyPI API documentation](https://docs.pypi.org/api/#api-preference)
 and this [discussion](https://discuss.python.org/t/fastly-interfering-with-pypi-search/73597/6).
 {{% /note %}}
 

docs/contributing.md

@@ -238,7 +238,7 @@ present), and the development branch.
 #### Multiple versions
 
 When trying to reproduce issues, you often want to use multiple versions of Poetry at the same time.
-[pipx](https://pypa.github.io/pipx/) makes this easy to do:
+[pipx](https://pipx.pypa.io/stable/) makes this easy to do:
 
 ```sh
 pipx install --suffix @1.2.1 'poetry==1.2.1'

docs/repositories.md

@@ -69,7 +69,7 @@ poetry add --source foo private-package
 
 Great, now all that is left is to publish your package. Assuming you'd want to share it privately
 with your team, you can configure the
-[Upload API](https://warehouse.pypa.io/api-reference/legacy.html#upload-api) endpoint for your
+[Upload API](https://docs.pypi.org/api/upload/) endpoint for your
 [publishable repository](#publishable-repositories).
 
 ```bash
@@ -332,7 +332,7 @@ to be provided only by one specific source to avoid dependency confusion attacks
 #### Python Package Index (PyPI)
 
 Poetry interacts with [PyPI](https://pypi.org) via its
-[JSON API](https://warehouse.pypa.io/api-reference/json.html). This is used to retrieve a requested
+[JSON API](https://docs.pypi.org/api/json/). This is used to retrieve a requested
 package's versions, metadata, files, etc.
 
 {{% note %}}
@@ -430,7 +430,7 @@ well.
 
 Poetry treats repositories to which you publish packages as user-specific and not project-specific
 configuration unlike [package sources](#package-sources). Poetry, today, only supports the
-[Legacy Upload API](https://warehouse.pypa.io/api-reference/legacy.html#upload-api) when publishing
+[Legacy Upload API](https://docs.pypi.org/api/upload/) when publishing
 your project.
 
 These are configured using the [`config`]({{< relref "cli#config" >}}) command, under the
@@ -442,7 +442,7 @@ poetry config repositories.testpypi https://test.pypi.org/legacy/
 
 {{% note %}}
 
-[Legacy Upload API](https://warehouse.pypa.io/api-reference/legacy.html#upload-api) URLs are
+[Legacy Upload API](https://docs.pypi.org/api/upload/) URLs are
 typically different to the same one provided by the repository for the simple API. You'll note that
 in the example of [Test PyPI](https://test.pypi.org/), both the host (`test.pypi.org`) as
 well as the path (`/legacy`) are different to its simple API (`https://test.pypi.org/simple`).