By all accounts the current state of Mezzanine on both Github and BitBucket works wonderfully with Django 1.7. You can actually specify a commit on either of these sites as an explicit dependency for your project, so using Django 1.7 is possible right now.
On Sat, Nov 29, 2014 at 8:06 AM, Radek Svarz <[email protected]> wrote: > Hi, > > how can we help to make the new release (Mezzanine v 3.1.11?) with the > setup.py listing Django 1.7.x? > > Radek > > On Wednesday, October 8, 2014 8:49:00 PM UTC+2, Stephen McDonald wrote: >> >> There's an outstanding issue here: >> >> https://github.com/stephenmcd/mezzanine/issues/1123 >> >> It only affects test data with new projects, so not a real blocker for >> anyone building a project. >> >> On Wed, Oct 8, 2014 at 5:54 PM, elguavas <[email protected]> wrote: >> >>> >>> so is mezz django 1.7 ready to go yet? pip install mezzanine still seems >>> to be pulling in django 1.6.x . >>> >>>> >> >> >> -- >> 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. > -- 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.
