Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compatibility with django-reversion 2.0

See original GitHub issue

It seems the new version of django-reversion (since 2.0) breaks django-cms while calling migrate:

lib/python3.4/site-packages/cms/utils/reversion_hacks.py", line 18, in <module>
    from reversion.models import Revision, Version, post_revision_commit  # NOQA  # nopyflakes
ImportError: cannot import name 'post_revision_commit'

According to their release notes, this signal got removed.

My first idea was to suggest adding version pinning to setup.py until compatibility is achieved, but it seems django-reversion isn’t a hard dependency at all. Though, having the user deal with this problem also isn’t nice.

Issue Analytics

State:
Created 7 years ago
Comments:11 (6 by maintainers)

Top GitHub Comments

4reactions

czpythoncommented, Sep 2, 2016

Closing as a won’t fix for the core of djangoCMS. Instead, we’ll release a third party app which will re-introduce revision support

2reactions

czpythoncommented, Jun 21, 2016

Hello, We’re aware of the issue, unfortunately it caught us at an unfortunate time as we’re doing multiple refactors of the codebase in preparation for 3.4 and 3.5 and so are currently maxed out. That said, any PR that fixes this is welcome and will be given priority.