You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We used to be able to twine upload -r pypi-local dist/* (pypi-local is an internal artifactory server, configured according to the artifactory manaul https://www.jfrog.com/confluence/display/RTF/PyPI+Repositories). Starting July 5th (the 1.7.2 release) it began to fail with the below error. Can you confirm that 1.7.x introduced this new SSL requirement for twine, or is there a fix/workaround we could use? Currently dropped back to twine 1.6.5 and that fixed us.
/home/user/python_env/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py:318:
SNIMissingWarning: An HTTPS request has been made, but the SNI
(Subject Name Indication) extension to TLS is not available on
this platform. This may cause the server to present an incorrect
TLS certificate, which can cause validation failures. You can
upgrade to a newer version of Python to solve this. For more
information, see
https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.
SNIMissingWarning
/home/user/python_env/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py:122:
InsecurePlatformWarning: A true SSLContext object is not
available. This prevents urllib3 from configuring SSL
appropriately and may cause certain SSL connections to fail. You
can upgrade to a newer version of Python to solve this. For more
information, see
https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
ValueError: No JSON object could be decoded
The text was updated successfully, but these errors were encountered:
This is not a new SSL requirement. We updated to a newer minimum version of requests that warns you when you're making an HTTPS requests without good OpenSSL support in your version of Python.
It looks like our pre-check to see if a package has already been uploaded (to support --skip-existing) is what's actually causing this to break.
We used to be able to
twine upload -r pypi-local dist/*
(pypi-local is an internal artifactory server, configured according to the artifactory manaul https://www.jfrog.com/confluence/display/RTF/PyPI+Repositories). Starting July 5th (the 1.7.2 release) it began to fail with the below error. Can you confirm that 1.7.x introduced this new SSL requirement for twine, or is there a fix/workaround we could use? Currently dropped back to twine 1.6.5 and that fixed us.The text was updated successfully, but these errors were encountered: