Could not install packages due to an EnvironmentError: Could not find a suitable TLS CA certificate bundle,

[metinjakupi]

Could not find a suitable TLS CA certificate bundle, invalid path: .heroku/python/lib/python3.7/ensurepip/_bundled/pip-10.0.1-py2.py3-none-any.whl/pip/_vendor/certifi/cacert.pem

[edmorley]

@metinjakupi Please could you post the full build log? The error would suggest the build was using a very old (and unsupported) Python 3.7 version, however, such old versions are not available on supported Heroku stacks, so something strange must be going on (is this being run outside of Heroku?).

[metinjakupi]

@edmorley, I've been deploying applications on DigitalOcean's App Platform for the past couple of weeks without any issues. However, starting this week, I've been encountering challenges and can't successfully deploy anymore. Here is my build log:

Could you assist me in resolving this? Thank you.

[edmorley]

From the build log I can see that the build is:

• Being run on Digitalocean rather than Heroku
• Using CNBs (specifically the Python classic buildpack shimmed into a CNB), which is not something we use on Heroku yet
• Ubuntu 18.04 (which is EOL and no longer supported by Heroku)
• Python 3.7.0 (which is both not the latest Python 3.7.x release and so insecure to use, plus Python 3.7 is also EOL)

The reported error can only occur when using Python <3.7.2 (that doesn't have https://github.com/python/cpython/commit/c743a6ac360cfa1d9de7e6fad98b68fca39367d5). Such Python versions aren't available on supported Heroku stacks, so this is a Digitalocean-specific problem, since they've chosen to continue to support the end of life and insecure Ubuntu 18.04.

Please report the issue to Digitalocean support.

In the meantime updating either Python version or Digitalocean stack will fix the issue you are seeing.

[edmorley]

Closing since this isn't an issue with this buildpack.