WiP Django 1.6 support

[yakky]

While Django 1.6 is still unreleased, we can try to see what's going to happen.
Still a work in progress and only addresses python-level issues.
All dependencies should be 1.6 ready now.
Biggest issues at the moment are django-reversion (PR opened for 1.6 support) and django-mptt support.
djangocms-text-ckeditor (opened PR for support) and django-hvad looks more easy to fix. 1.6 support fixed in django-hvad.
ATM code is django 1.4 compatible.
Django 1.6 added to build matrix to track the progress.

[meshy]

1.6 is looming. Any news?

[yakky]

Adding awesomeness to django CMS 3.0 has higher priority at the moment; django 1.6 compatibility is mostly replacing deprecated functions / features with newer version, it will be easier to fix them with a stable codebase

[meshy]

Ok, cool. Thanks for getting back to me. :)

[meshy]

Django-reversion fixes here.

[yakky]

Wow, thanks! You're really chasing after all the dependencies.

[meshy]

My pleasure, it keeps me busy ;). It's been fun so far :).

I've not had any trouble running the django-mptt tests with python 3 on django 1.6 though. Could you elaborate on the issues you were having with it?

[yakky]

Great to hear that mptt has now full support. I ran this over two months ago, they may have fixed it in the meantime.
I'll rebase this code and let it run again to catch further issues.

[meshy]

FYI: django-reversion, djangocms-text-ckeditor and django-hvad, should all have 1.6 support now but I don't think they all have releases yet.

[yakky]

Yeah, great job!
Dependency wise we should be fine.
Now it's time to get my hand dirty and deal with the last failures

[meshy]

Thank you!

[yakky]

Yeah, all green :)
@digi604 would you want to merge this now or should we wait for other code to land and rebase this when everything else is settled?

[meshy]

Good news!... hang on, one is grey.

[yakky]

it's just travis gone crazy .... I'm trying to get that instance run properly, it doesn't look as test dependent. I'll try to make it run again properly before merging

[meshy]

That one (Django 1.6, Python 3.3, mySQL) seems to fail every time, I suspect that it's something wrong with the requirements setup.

[meshy]

Is there a reason we're passing -q to pip?

[meshy]

python setup.py egg_info failed with error code 1 in /home/charlie/venvs/django-cms/build/coverage

[meshy]

Changing the required version of coverage from 3.4 to 3.6 made it work locally for me.

[meshy]

Well it looks like I made a mistake there, eh :/. I guess the coverage problem was just me -- having looked at the previous logs it got past that on travis. It's actually failing on the line:

if [ $DB == 'mysql://root@127.0.0.1/djangocms_test' ]; then pip install -q mysql-python --use-mirrors; fi

Sorry.

[meshy]

FWIW I also get an error running that line (but in fairness I don't have mysql installed). My error is

/home/charlie/venvs/django-cms/build/mysql-python/distribute-0.6.28-py3.3.egg
Traceback (most recent call last):
  File "<string>", line 16, in <module>
  File "/home/charlie/venvs/django-cms/build/mysql-python/setup.py", line 14, in <module>
    from setup_posix import get_config
  File "./setup_posix.py", line 2, in <module>
    from ConfigParser import SafeConfigParser
ImportError: No module named 'ConfigParser'
----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in
        /home/charlie/venvs/django-cms/build/mysql-python

[meshy]

Oh dear http://stackoverflow.com/questions/14087598/python-3-3-importerror-no-module-named-configparser

Edit; summary: "MySQL-python does not currently support Python 3."

[yakky]

mysql-python doesn't support Python 3 ATM, thus is excluded from build matrix

[meshy]

Cool, well that looks like that's it for the moment, then. Good work! Good night, sleep well! ;)

[craigds]

Django 1.6 has been released. Any update on when this will get merged?

[yakky]

I need some time to test this in real projects before merging.
Can't really give an ETA but I am confident to handle this in the next few days.

[yakky]

@FinalAngel due to django switch to jQuery 1.9 how we can handle the compatibility between the two?
There is some jQuery 1.9 patches around but some code in them is incompatible with older jQuery version.
Would you like me to push them in this PR so you can later fix the JS part?

[coveralls]

Coverage increased (+0.06%) when pulling 4a6481e on yakky:feature/django_16 into 294fba4 on divio:develop.

[digi604]

Is this ready?

[yakky]

Yes, anything that should arise is fixable separately