Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix compatibility with psycopg #6666

Open
FinalAngel opened this issue Apr 4, 2019 · 6 comments

Comments

Projects
None yet
6 participants
@FinalAngel
Copy link
Member

commented Apr 4, 2019

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.

@jrief

This comment has been minimized.

Copy link
Contributor

commented Apr 5, 2019

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'
@JustDevZero

This comment has been minimized.

Copy link

commented Apr 5, 2019

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.

@DmytroLitvinov

This comment has been minimized.

Copy link

commented Apr 8, 2019

The same behaviour.
Thanks for submitting issue.

@v582ijay

This comment has been minimized.

Copy link

commented Apr 11, 2019

Same here too. Is there any workaround ?

@JustDevZero

This comment has been minimized.

Copy link

commented Apr 11, 2019

@MARUTHESH

This comment has been minimized.

Copy link

commented Apr 19, 2019

Same here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.