admin管理员组文章数量:1389871
I have a Python/Django app which uses Pipfile
and Pipfile.lock
running on Heroku-22 stack with classic buildpacks.
requirements.txt
is not part of the code base, thus e.g. Heroku: ModuleNotFoundError :No module named 'requests' and similar issues are not relevant.
Pipfile
and Pipfile.lock
contain psycopg2
(not psycopg2-binary
). Testing env has expected packages installed, however, production env has an extra package, psycopg
, installed.
$ heroku run bash -a my-app-production
~ $ pip freeze | grep -i psyco
psycopg==3.2.4
psycopg2==2.9.10
vs
$ heroku run bash -a my-app-testing
~ $ pip freeze | grep -i psyco
psycopg2==2.9.10
Testing and production envs are the same with one exception - server side Pgbouncer runs on production. Pgbouncer () lists psycopg
as one of its dependencies. Though according to Heroku' docs, Pgbouncer's connection pool exists on the database server, not on app' dyno.
Also, installing app' dependencies locally in a Docker container with pipenv install --deploy
(Heroku runs the same command) works as expected.
Any idea where is this extra psycopg
package coming from? Is it installed because of Pgbouncer (unlikely, in my opinion)?
本文标签: djangoHeroku installs extra Python packageStack Overflow
版权声明:本文标题:django - Heroku installs extra Python package - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744740111a2622557.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论