Using django-mptt instead of shipping it with the CMS

[Jonas Obrist]

As proposed several times it is probably better to use django-mptt as a
dependency instead of actually shipping it in the CMS.

Benjamin Wohlwend has already started work on this [1].

What are everyone's thoughts on (assuming the branch is stable and
everything) merging it into 2.2 (2.1 is out of question)?

Jonas

[Franck Bret]

It seems that things are moving on the mptt side, the new model 0.4 is
retrocompatible 0.3.
https://github.com/django-mptt/django-mptt/issues/closed#issue/21
https://github.com/django-mptt/django-mptt/blob/11109e5f2430ec5511085994691ff425ddf3530c/docs/upgrade.txt

[Samuel Luescher]

This bundled MPTT is a total showstopper. It prevents me (and possibly other developers) from developing my app together with Django CMS. 

What's the status on removing the bundled MPTT? I looked into the 2.2 release candidate and it's still there.

[Ionel Cristian Mărieș]

There's no mptt in 2.2. See https://github.com/divio/django-cms/tree/2.2rc2

Maybe you need to cleanup your site-packages ?

Thanks,
-- Ionel