#30483: Switch test requirements from psycopg2-binary package to pscyopg2
------------------------------------------------+------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
The psycopg2 project recommends **not** using the psycopg2-binary package.
Here are the relevant warnings:
http://initd.org/psycopg/docs/install.html#binary-install-from-pypi
> Note: The psycopg2-binary package is meant for beginners to start
playing with Python and PostgreSQL without the need to meet the build
requirements.
>
> If you are the maintainer of a publish package depending on psycopg2 you
shouldn’t use ‘psycopg2-binary’ as a module dependency. For production use
you are advised to use the source distribution.
>
> Note: The binary packages come with their own versions of a few C
libraries, among which libpq and libssl, which will be used regardless of
other libraries available on the client: upgrading the system libraries
will not upgrade the libraries used by psycopg2. Please build psycopg2
from source if you want to maintain binary upgradeability.
>
> Warning: The psycopg2 wheel package comes packaged, among the others,
with its own libssl binary. This may create conflicts with other extension
modules binding with libssl as well, for instance with the Python ssl
module: in some cases, under concurrency, the interaction between the two
libraries may result in a segfault. In case of doubts you are advised to
use a package built from source.
We should follow the advice and use the pscyopg2 package and used stop
using the binary package.
--
Ticket URL: <https://code.djangoproject.com/ticket/30483>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.4f0afecfa23798ec721305ec701f8b2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
