|
3 | 3 | Migrating to PyPI.org |
4 | 4 | ===================== |
5 | 5 |
|
6 | | -:term:`PyPI.org` is a new, rewritten version of PyPI that is replacing the |
7 | | -legacy code base located at `pypi.python.org`. As it becomes the default, and |
8 | | -eventually only, version of PyPI people are expected to interact with, there |
9 | | -will be a transition period where tooling and processes are expected to need to |
10 | | -update to deal with the new location. |
11 | | - |
12 | | -This section covers how to migrate to the new PyPI.org for different tasks. |
13 | | - |
| 6 | +:term:`PyPI.org` is the new, rewritten version of PyPI that has replaced the |
| 7 | +legacy PyPI code base. It is the default version of PyPI that people are |
| 8 | +expected to use. These are the tools and processes that people will need to |
| 9 | +interact with ``PyPI.org``. |
14 | 10 |
|
15 | 11 | Publishing releases |
16 | 12 | ------------------- |
17 | 13 |
|
18 | | -``pypi.org`` became the default upload platform in September 2016. |
| 14 | +``pypi.org`` is the default upload platform as of September 2016. |
19 | 15 |
|
20 | 16 | Uploads through ``pypi.python.org`` were *switched off* on **July 3, 2017**. |
| 17 | +As of April 13th, 2018,``pypi.org`` is the URL for PyPI. |
21 | 18 |
|
22 | 19 | The recommended way to migrate to PyPI.org for uploading is to ensure that you |
23 | 20 | are using a new enough version of your upload tool. |
@@ -112,45 +109,26 @@ Registering new user accounts |
112 | 109 |
|
113 | 110 | In order to help mitigate spam attacks against PyPI, new user registration |
114 | 111 | through ``pypi.python.org`` was *switched off* on **February 20, 2018**. |
| 112 | +New user registrations at ``pypi.org`` are open. |
115 | 113 |
|
116 | 114 |
|
117 | 115 | Browsing packages |
118 | 116 | ----------------- |
119 | 117 |
|
120 | | -``pypi.python.org`` is currently still the default interface for browsing packages |
121 | | -(used in links from other PyPA documentation, etc). |
122 | | - |
123 | | -``pypi.org`` is fully functional for purposes of browsing available packages, and |
124 | | -some users may choose to opt in to using it. |
125 | | - |
126 | | -``pypi.org`` is expected to become the default recommended interface for browsing |
127 | | -once the limitations in the next section are addressed (at which point |
128 | | -attempts to access ``pypi.python.org`` will automatically be redirected to |
129 | | -``pypi.org``). |
| 118 | +While ``pypi.python.org`` is may still be used in links from other PyPA |
| 119 | +documentation, etc, the default interface for browsing packages is |
| 120 | +``pypi.org``. The domain pypi.python.org now redirects to pypi.org, |
| 121 | +and may be disabled sometime in the future. |
130 | 122 |
|
131 | 123 |
|
132 | 124 | Downloading packages |
133 | 125 | -------------------- |
134 | 126 |
|
135 | | -``pypi.python.org`` is currently still the default host for downloading packages. |
136 | | - |
137 | | -``pypi.org`` is fully functional for purposes of downloading packages, and some users |
138 | | -may choose to opt in to using it, but its current hosting setup isn't capable of |
139 | | -handling the full bandwidth requirements of being the default download source (even |
140 | | -after accounting for the Fastly CDN). |
141 | | - |
142 | | -``pypi.org`` is expected to become the default host for downloading |
143 | | -packages once it has been redeployed into an environment capable of |
144 | | -handling the associated network load. The setup work is being tracked |
145 | | -as part of the `Launch milestone |
146 | | -<https://github.com/pypa/warehouse/milestone/1>`_. |
147 | | - |
| 127 | +``pypi.org`` is the default host for downloading packages. |
148 | 128 |
|
149 | 129 | Managing published packages and releases |
150 | 130 | ---------------------------------------- |
151 | 131 |
|
152 | | -``pypi.python.org`` provides an interface for logged in users to manage their |
153 | | -published packages and releases. |
| 132 | +``pypi.org`` provides a fully functional interface for logged in users to |
| 133 | +manage their published packages and releases. |
154 | 134 |
|
155 | | -``pypi.org`` also provides such an interface which is fully functional, and |
156 | | -some users may choose to opt in to using it. |
0 commit comments