Closed sethb0 closed 4 years ago
This should resolve #48 and #46. Plus psycopg2 tells you to use psycopg2-binary.
Given that builds and wheels are cached on Heroku, there's little counterproductive here. The wheels for psycopg2-binary include openssl which means any updates made to the stack images openssl libraries would bypass your application's security. The fact that psycogp2 warns to use -binary
in all situations is unfortunate.
In the future please read previously opened (and closed) issues prior to opening new ones.
The fact that build issues with psycopg2
on the development host make it impossible to deploy an app is also "unfortunate." Would you suggest taking the wrapped openssl issue up with that team?
I agree that this is pretty obnoxious. This means the default howto instructions for Django on Heroku result in headaches on some platforms and warnings on all of them.
The latest
psycopg2
package always builds from source, which is counterproductive on Heroku.psycopg2-binary
contains prebuilt drivers for supported architectures and should be used instead.