Skip to main content

twine

Twine is a utility for interacting with PyPI.

Currently it only supports uploading distributions.

Why Should I Use This?

The biggest reason to use twine is that python setup.py upload uploads files over plaintext. This means anytime you use it you expose your username and password to a MITM attack. Twine uses only verified TLS to upload to PyPI protecting your credentials from theft.

Secondly it allows you to precreate your distribution files. python setup.py upload only allows you to upload something that you’ve created in the same command invocation. This means that you cannot test the exact file you’re going to upload to PyPI to ensure that it works before uploading it.

Finally it allows you to pre-sign your files and pass the .asc files into the command line invocation (twine upload twine-1.0.1.tar.gz twine-1.0.1.tar.gz.asc). This enables you to be assured that you’re typing your gpg passphrase into gpg itself and not anything else since you will be the one directly executing gpg --detach-sign -a <filename>.

Features

  • Verified HTTPS Connections

  • Uploading doesn’t require executing setup.py

  • Uploading files that have already been created, allowing testing of distributions before release

  • Supports uploading any packaging format (including wheels).

Installation

$ pip install twine

Usage

  1. Create some distributions in the normal way:

$ python setup.py sdist bdist_wheel
  1. Upload with twine:

$ twine upload dist/*
  1. Done!

Options

$ twine upload -h
usage: twine upload [-h] [-r REPOSITORY] [-s] [-i IDENTITY] [-u USERNAME]
                    [-p PASSWORD] [-c COMMENT]
                    dist [dist ...]

positional arguments:
  dist                  The distribution files to upload to the repository,
                        may additionally contain a .asc file to include an
                        existing signature with the file upload

optional arguments:
  -h, --help            show this help message and exit
  -r REPOSITORY, --repository REPOSITORY
                        The repository to upload the files to
  -s, --sign            Sign files to upload using gpg
  -i IDENTITY, --identity IDENTITY
                        GPG identity used to sign files
  -u USERNAME, --username USERNAME
                        The username to authenticate to the repository as
  -p PASSWORD, --password PASSWORD
                        The password to authenticate to the repository with
  -c COMMENT, --comment COMMENT
                        The comment to include with the distribution file

Resources

Contributing

  1. Fork the repository on GitHub.

  2. Make a branch off of master and commit your changes to it.

  3. Ensure that your name is added to the end of the AUTHORS file using the format Name <email@domain.com> (url), where the (url) portion is optional.

  4. Submit a Pull Request to the master branch on GitHub.

Metadata

Release files for twine 1.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for twine 1.2.3
File Size Uploaded Provenance Actions
twine-1.2.3.tar.gz 17.9 kB Without provenance Details for twine-1.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for twine 1.2.3
File Interpreter ABI Platform Actions
twine-1.2.3-py2.py3-none-any.whl Python 3, Python 2 none any Details for twine-1.2.3-py2.py3-none-any.whl

Total release size: 31.9 kB

Release files / twine-1.2.3.tar.gz

Download URL twine-1.2.3.tar.gz
Size 17.9 kB
Tags Source
SHA-256 checksum
How to use checksums
3601c07869e3a02a674d3b0ec6da97108fa040e5dfa84dea1ec1579c4e09e275
BLAKE2b-256 checksum
How to use checksums
54c91538847c7e71cd8bea78b590c9f184c5660306950acb625558abafd156c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / twine-1.2.3-py2.py3-none-any.whl

Download URL twine-1.2.3-py2.py3-none-any.whl
Size 14.1 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
1a90a090dfb580bcb61884f09290c7e8b152e5e289825c29f8a7426540e82891
BLAKE2b-256 checksum
How to use checksums
21c8976298a9f7abd014fdf5eaf34c25894896b76f0864de8a224e4fe06a9d0e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for twine 1.2.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.2.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page