|
93 | 93 |
|
94 | 94 | [pypi] |
95 | 95 | username:__token__ |
96 | | - password:pypi-the_gibberish_generated_in_create_api_token_at_the_bottom_of_account_settings |
| 96 | + password:pypi-API_TOKEN |
97 | 97 |
|
98 | | - The "password" is under "Account Settings" -> "API Token" -> "Options" -> "View Unique |
99 | | - Identifier" -- the Copy button doesn't work at least on Mac. |
100 | | - (or you can use the "password" field in the [pypi] section, but that's not recommended)') |
| 98 | + The "password" is the API token you've just created -- if you lose the file you |
| 99 | + will also lose the API token. and have to create it again. This is all very |
| 100 | + poorly documented. This is Not the "Unique identifier" that you see in the |
| 101 | + "API Tokens" tab on the "Your Account" page -- super confusing. |
101 | 102 |
|
102 | | - FYI -- PyPI is apparently uninterested in having contributions from smaller projects |
103 | | - which haven't been following their internal security discussions for years. All of this |
104 | | - is super mysterious and not well documented. sigh. But they did mail out USB sticks to |
105 | | - the top 1% of projects in Python! |
| 103 | +20. Delete the two .tar.gz files and .whl file in dist. (and the docs) |
106 | 104 |
|
107 | | -20. Delete the two .tar.gz files and .whl file in dist. |
108 | | -
|
109 | | -21. For starting a new major release create a GitHub branch for the old one. |
| 105 | +21. For starting a new major release create a GitHub branch to preserve the old one |
| 106 | + for patches, etc. esp. during beta releases. |
110 | 107 |
|
111 | 108 | 22. Immediately increment the number in _version.py and run tests on it here |
112 | 109 | to prepare for next release. |
113 | 110 |
|
114 | | -23. Announce on the blog, to the list, and twitter. |
| 111 | +23. Announce on the blog and to the list. |
115 | 112 | ''' |
116 | 113 | import os |
117 | 114 | import shutil |
|
0 commit comments