Django-cms: Fix compatibility with psycopg

Created on 4 Apr 2019 · 8Comments · Source: django-cms/django-cms

Summary

Psycopg 2.8 has just been released and breaks compatibility in django CMS.

Expected behaviour

When building a project with latest django CMS the build should succeed.

Actual behaviour

When building a project with latest django CMS the build is failing.

Other

The issue has been resolved for 3.4, 3.5 and 3.6 on Divio Cloud. Manually pinning psycopg<2.8 will fix the issue in a project.

Source

FinalAngel

👍8 😕1

Most helpful comment

Just FYI this is a Django bug solved in 2.2+ only (see https://code.djangoproject.com/ticket/30331)

The only solution (documented by django itself) for 2.1 and below is using psycopg2 2.7.x as reported here. There is no available fix in django CMS

yakky on 30 Jun 2019

👍7

All 8 comments

To be more precise, I stumbled across this error as well.

It happens during this migration:

Applying cms.0019_set_pagenode...
line 68, in apply
    connection.introspection.get_table_description(connection.cursor(), 'cms_page')
  File "lib/python3.6/site-packages/django/db/backends/postgresql/introspection.py", line 87, in get_table_description
    )) for line in cursor.description
  File "lib/python3.6/site-packages/django/db/backends/postgresql/introspection.py", line 87, in <listcomp>
    )) for line in cursor.description
TypeError: sequence index must be integer, not 'slice'

jrief on 5 Apr 2019

👍2

I confirm that this behaviour happens, pinning<2.8 'workarounds', but having 2 years after the last major release, I thing that the migrations should be fixed in order to support the new version.

JustDevZero on 5 Apr 2019

👍6

The same behaviour.
Thanks for submitting issue.

DmytroLitvinov on 8 Apr 2019

Same here too. Is there any workaround ?

v582ijay on 11 Apr 2019

As we already said:

Pin psycopg2==2.7.7 in your requirement.txt and run a pip install
psycopg2==2.7.7

El jue., 11 abr. 2019 20:02, v582ijay notifications@github.com escribió:

Same here too. Is there any workaround ?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/divio/django-cms/issues/6666#issuecomment-482229061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKi19fbXQ2LZCHVDaQnf5fYCjN48udfks5vf3iigaJpZM4cdE6A
.