PyPI lets you submit any number of versions of your distribution to the index.
If you alter the meta-data for a particular version, you can submit it again
and the index will be updated.

PyPI holds a record for each (name, version) combination submitted. The first
user to submit information for a given name is designated the Owner of that
name. Changes can be submitted through the register command or
through the web interface. Owners can designate other users as Owners or
Maintainers. Maintainers can edit the package information, but not designate
new Owners or Maintainers.

By default PyPI displays only the newest version of a given package. The web
interface lets one change this default behavior and manually select which
versions to display and hide.

For each version, PyPI displays a home page. The home page is created from
the long_description which can be submitted via the register
command. See PyPI package display for more information.

Distutils exposes two commands for submitting package data to PyPI: the
register command for submitting meta-data to PyPI
and the upload command for submitting distribution
files. Both commands read configuration data from a special file called a
.pypirc file.

Note: if your username and password are saved locally, you will not see this
menu. Also, refer to The .pypirc file for how to store your credentials in a
.pypirc file.

If you have not registered with PyPI, then you will need to do so now. You
should choose option 2, and enter your details as required. Soon after
submitting your details, you will receive an email which will be used to confirm
your registration.

Once you are registered, you may choose option 1 from the menu. You will be
prompted for your PyPI username and password, and register will then
submit your meta-data to the index.

The command is invoked immediately after building one or more distribution
files. For example, the command

pythonsetup.pysdistbdist_wininstupload

will cause the source distribution and the Windows installer to be uploaded to
PyPI. Note that these will be uploaded even if they are built using an earlier
invocation of setup.py, but that only distributions named on the command
line for the invocation including the upload command are uploaded.

If a register command was previously called in the same command,
and if the password was entered in the prompt, upload will reuse the
entered password. This is useful if you do not want to store a password in
clear text in a .pypirc file.

You can use the --sign option to tell upload to sign each
uploaded file using GPG (GNU Privacy Guard). The gpg program must
be available for execution on the system PATH. You can also specify
which key to use for signing using the --identity=name option.

The register and upload commands both check for the
existence of a .pypirc file at the location $HOME/.pypirc.
If this file exists, the command uses the username, password, and repository
URL configured in the file. The format of a .pypirc file is as
follows:

In that case, README.txt is a regular reStructuredText text file located
in the root of the package besides setup.py.

To prevent registering broken reStructuredText content, you can use the
rst2html program that is provided by the docutils package and
check the long_description from the command line:

$ python setup.py --long-description | rst2html.py > output.html

docutils will display a warning if there’s something wrong with your
syntax. Because PyPI applies additional checks (e.g. by passing --no-raw
to rst2html.py in the command above), being able to run the command above
without warnings does not guarantee that PyPI will convert the content
successfully.