Parents (Total: 11)

The searched file hash is included in 11 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	57584
MD5	31B1BEE87D4E18DF063A75112232DD23
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	twine
PackageSection	utils
PackageVersion	3.1.1-1
SHA-1	2E8B4CE28D00C5AB3DBE44EB1D143AED2BD2F185
SHA-256	4BF39BC086906882B1DF4427251C61D0EB29AFDCC57790676D03CC1DD400BA43

Key	Value
FileSize	37034
MD5	407692CF5AA429BB4D812BB377782432
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
PackageName	twine
PackageSection	utils
PackageVersion	1.8.1-2
SHA-1	0BFDE72B3D27C8DCD1A3CC6CB3566C923E3C8929
SHA-256	5D4B601608CDE8DB4B8C4675419DD9664126A52C599D6105BDB1BCD27A9004D3

Key	Value
FileSize	56492
MD5	C712A58782390E7B86FD6C58AA44E5BB
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	twine
PackageSection	utils
PackageVersion	3.3.0-1
SHA-1	3DF2C3D00EEB87CB7DABB7BEF9308476DF0F6C42
SHA-256	F1551D36609517253EB74A1BDA44D5E182297A49BD8958147EC4E4BD6750C0F9

Key	Value
FileSize	71436
MD5	0FE96DD941E28DB5FA2E3B5F34AFF926
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Debian Python Team <team+python@tracker.debian.org>
PackageName	twine
PackageSection	utils
PackageVersion	3.4.2-2
SHA-1	A8FCEEE3DFF0A3FD4402D3863E8FD52CE431ED69
SHA-256	5A400CE6C9BE70C3AF7114D7F025C6E9DFEE4AA07E7F4BA1BB135D5EAD791162

Key	Value
FileSize	70168
MD5	149C979B9B139B52D6146C43C5FE51E8
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
PackageName	twine
PackageSection	utils
PackageVersion	1.13.0-1
SHA-1	C78E5302DFEE7D1982982A1CC04BEC5AA1545029
SHA-256	56B66489D76F20CA31441CEAE4DA6D233469459CDBDEF7B2472B2690644B222C

Key	Value
FileSize	25678
MD5	0D1BDE8F630B92096A35B22285464DA3
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the python meaning) to PyPi. . 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).
PackageMaintainer	Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
PackageName	twine
PackageSection	utils
PackageVersion	1.3.1-1
SHA-1	056863C3B06A09285B558CDDA1D0E98CA2542958
SHA-256	43284AB9D59733D27B2C9D9F7587E60293B3EF97E69AAAFC56F531BEBE6A729D

Key	Value
FileSize	55576
MD5	ABA617FDA8B124D625547436C2BEF5CC
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	twine
PackageSection	utils
PackageVersion	3.2.0-1
SHA-1	11E3A284776830875EF1EA823A80EE8FA3A04360
SHA-256	4EBA2C548FA0A11594248A1A32802FCB9F6E0434B9FA40FB06C5BDBF7A26576D

Key	Value
FileSize	21510
MD5	36E0FA5B6EAAB1265F95E5175DEF21C2
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
PackageName	twine
PackageSection	utils
PackageVersion	1.5.0-1
SHA-1	A583F031B00B3A39F2ECBEFD634E861192C66312
SHA-256	082BDE111553EF2CDDEA209C16186AEE15AAAA6E585F06E7FF8768D7EB7EDE95

Key	Value
FileSize	70280
MD5	2E9798CE244FC783EDED2AD07EDC5F49
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Debian Python Team <team+python@tracker.debian.org>
PackageName	twine
PackageSection	utils
PackageVersion	3.3.0-1
SHA-1	7FAC65974B1376969174A717BC033D4E05C8C2E9
SHA-256	F0BE66878DBE26BE387D2B70F9B09034D527F3374D1DB9368721615D718AC16A

Key	Value
FileSize	42244
MD5	CF8D6A0DE8E0665BFF1A5B7984BA760C
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . 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).
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	twine
PackageSection	utils
PackageVersion	1.10.0-1
SHA-1	2071A361E2A87D14BE9EE165B830DB5D179ABD8B
SHA-256	911E496F36B24FD3C98318D1022D02D37976AE9E818500893AB297F1DA4DF999

Key	Value
FileSize	20154
MD5	70F742742A8F1EF5455E7067BA1E2AF4
PackageDescription	utility for interacting with PyPI Twine is a tool for uploading distributions (in the python meaning) to PyPi. . 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).
PackageMaintainer	Zygmunt Krynicki <zygmunt.krynicki@canonical.com>
PackageName	twine
PackageSection	utils
PackageVersion	1.3.1-1~ubuntu14.04.1
SHA-1	E40DA4E183A6BF229F8C5DB933728F73CDA8A32B
SHA-256	4159B76FA7551CD0138D3F2A1031B4D34225C394A8BE851CD5457014018A1B02