Skip to content

Commit 4eb5655

Browse files
committed
Fix: edits from review
1 parent b3e6a42 commit 4eb5655

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

tutorials/publish-pypi.md

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -64,14 +64,6 @@ The steps for publishing on test PyPI vs. real PyPI are the same with the
6464
exception of a different url. Thus, in this lesson you will use test PyPI
6565
to practice and learn.
6666

67-
:::{todo}
68-
When this lesson is published -
69-
in xx lesson, you will learn how to setup an automated release workflow on GitHub
70-
using GitHub actions that will automate the PyPI publication process whenever
71-
you create a new software release.
72-
:::
73-
74-
7567
## 4 Steps for publishing a Python package on PyPI
7668

7769
There are 4 things that you need to do to publish your Python package
@@ -244,8 +236,7 @@ use a backup device that only you can access to validate that the person logging
244236

245237
This matters on PyPI because someone could login to your account and upload a version of your package that has security issues. These issues will then impact all of your users when they download and install that version of the package.
246238

247-
While you don't have to setup 2-factor authentication, we strongly
248-
suggest that you do so.
239+
2-factor authentication is now required for authentication on PyPI.
249240
:::
250241

251242
## Step 4. Create a package upload token

0 commit comments

Comments
 (0)