Package: twine Version: 1.8.1-2 Severity: important Dear Maintainer,
Trying to upload a package to TestPyPI [1]: $ twine upload --repository-url https://test.pypi.org/legacy/ dist/* results in twine uploading it to the *regular* PyPI. There's a bug in the --repository-url handling, which is fixed upstream [2]. For now, using: $ twine upload --repository pypitest dist/* works. It'd be nice to get the upstream fix though. Someone might accidentally upload a package to PyPI instead of TestPyPI if they use the same credentials for both. Thanks. - Felix [1] https://packaging.python.org/guides/using-testpypi/ [2] https://github.com/pypa/twine/commit/7ddbaf40951ae49a1e686b0a3456bf84e93ea004 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages twine depends on: ii python3 3.6.4~rc1-2 ii python3-clint 0.5.1-1 ii python3-pkg-resources 38.2.4-2 ii python3-pkginfo 1.2.1-1 ii python3-requests 2.18.1-1 ii python3-requests-toolbelt 0.8.0-1 ii python3-setuptools 38.2.4-2 twine recommends no packages. twine suggests no packages. -- debconf-show failed