Alex and I have worked out most of the remaining issues: https://github.com/stephenmcd/mezzanine/pull/1635
There's one major issue outstanding which is slightly laborious but should be relatively straightforward, noted in the Django 1.10 release notes (https://docs.djangoproject.com/en/dev/releases/1.10/#features-removed-in-1-10) "Support for optparse is dropped for custom management commands." Most of the management commands in Mezzanine are broken against 1.10 due to this, and need to be updated to use ArgumentParser - I couldn't find any pointers on what needs to happen here, but presumably that can be worked out but studying some of the existing commands in Django itself. If anyone has time to work on this it'd be a huge help. On Wednesday, 22 June 2016 15:39:02 UTC+10, Stephen McDonald wrote: > > Hi all, > > Django just announced a 1.10 beta: > https://docs.djangoproject.com/en/1.10/releases/1.10/ > > I've been testing Mezzanine against it and have been pleasantly surprised > at how much works, as historically this hasn't been the case. I've created > a task list to track all issues that have been found and fixed: > https://github.com/stephenmcd/mezzanine/issues/1619 > > Please try it out yourself, and report anything you come across in the > above issue. If you do find anything, please make an effort to work out a > resolution too. > > While I've unfortunately dropped the ball again on getting a release out > since Mezzanine 4.1 earlier this year, hopefully we can get any > compatibility issues with Django 1.10 ironed out quickly, and put a new > Mezzanine release out that coincides with that. > > > -- > Stephen McDonald > http://jupo.org > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
