8th Aug, 2019
- Regular PyPI user, maintains 3 or 4 personal projects.
- Updates his projects every 3 or 4 weeks
- Uses twine to update, does not log into PyPI often
- No problem at all logging in, finding and setting up API token
- Understood "token scope" well (created a token for a single project)
- Currently manually enters his username and password when uploading to PyPI via Twine. Does not use a
.pypircfile - Couldn't find the link to the help page from the API token page
- Wasn't sure how to create a
.pypircfile for a single project vs whole account? Should it be in his home folder? In the project root? This is not clear.
21st Aug, 2019
- Regular PyPI user, maintinaing 6 projects
- https://pypi.org/project/autopub/ maintainer
- Uses twine and poetry to upload to PyPI
- uses Travis CI and Circle CI. Will use GitHub actions when he gets access
- After logging into PyPI, Justin navigated to the projects settings page to generate a token
- After being directed to account settings, Justin effectively generated a token for 2 different projects
- Justin easily updated his Circle CI settings via the Circle CI UI
- When using travis encryption(via CLI), Justin got an error message that the token was too long to use that function
Add a new section to the API token confirmation page, which:
- Shows the username/password instructions
- Explains
.pypircfiles, and where to put them for "entire account" tokens vs "scoped to project" tokens - Shows an example (filled)
.pypircfile
Add a link on the "manage project > settings" page to the API token creation page.
- Do we need to document poetry, setuptools, travis CI, circle CI?