Django 1.7 support

[Stephen McDonald]

If anyone's looking to help, there appears to only be one outstanding issue remaining as described here:

https://github.com/stephenmcd/mezzanine/issues/987#issuecomment-47728024

--
Stephen McDonald
http://jupo.org

[Eduardo Rivas]

Hey, so Django 1.7 has just been officially released. From what I gather from the GitHub issue linked by Steve, all works fine in Mezzanine. I wanted to ask how are migrations going to work now. Since we are supporting Django 1.5 and 1.6, does that mean we will support both South and the new built-in migrations? Also, is Mezzanine making use of the new App loading features?

For a quick overview of what's new in Django 1.7: official announcement.

[Eduardo Rivas]

Just noticed Django supports having both types of migrations coexist.
Apparently all that needs to be done is renaming migrations to
south_migrations.
https://docs.djangoproject.com/en/1.7/topics/migrations/#libraries-third-party-apps

[Tom Lockhart]

On 2014-09-03, at 8:24 AM, Eduardo Rivas <jeriva...@gmail.com> wrote:

> Just noticed Django supports having both types of migrations coexist. Apparently all that needs to be done is renaming migrations to south_migrations. https://docs.djangoproject.com/en/1.7/topics/migrations/#libraries-third-party-apps

Yup. Just heard a talk on this from Andrew Godwin at DjangoCon here in Portland. Native migrations will re-use the migrations/ directory and if you want to maintain a South history then move previous migrations over to south_migrations/. Though once you are at 1.7 I'm not sure why you would need to go back; Andrew indicated that most of the code for migrations is new but they have been testing and bugfixing for several months already.

hth

- Tom

[Eduardo Rivas]

Thanks for your answer, Thomas. I'll try to migrate some of my sites to 1.7 and report back how it goes.

[Stephen McDonald]

Would love some concrete guidance on this if anyone can work out exactly what needs to happen. It sounds like all that's left to do for 1.7 support is to move all our south migrations into different directories and create new 1.7 style initial migrations, but I've not had the time to work this out properly.

If anyone could work this out definitively and create a pull request, you'd really be helping out.

--
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 mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen McDonald]

Hi all,

Support for migrations using either South + Django<1.7, or Django 1.7's migrations has just been merged in thanks to Baylee Feore. 

It works as follows:

- Each app.migrations package now houses a single new initial migration for Django 1.7

- Each app now houses its old south migrations under the app.migrations.south package

- In mezzanine.utils.conf.set_dynamic_settings (called at the end of a project's settings.py module), for South + Django<1.7 we configure the SOUTH_MIGRATION_MODULES setting to point to the new custom migration packages per app: http://south.readthedocs.org/en/latest/settings.html#south-migration-modules

This is a final call for help in testing Mezzanine and Cartridge against Django 1.7 before new official releases get pushed out supporting it, thanks a lot!

[Eduardo Rivas]

Hey Stephen, I tried the latest version of Mezzanine with one of my sites and all went smoothly. It just required following Django's instructions for the new built-in migrations. After that, the database was up to date with Mezzanine's models and my own.

[Eduardo Rivas]

Just to clarify, I followed Django's instructions in my own project, didn't have to touch Mezzanine at all.

[elguavas]

so is mezz django 1.7 ready to go yet? pip install mezzanine still seems to be pulling in django 1.6.x .

[Eduardo Rivas]

Currently only the development version. You'll need to clone from the repo to get Django 1.7 support.

[Stephen McDonald]

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 <elgu...@gmail.com> wrote:

so is mezz django 1.7 ready to go yet? pip install mezzanine still seems to be pulling in django 1.6.x .

[Radek Svarz]

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 

[Stephen McDonald]

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.

--

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 mezzanine-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Radek Svarz]

Can we consider the dev HEAD to be stable enough? 

I would rather propagate the tagged commit for the requirements management reasons (e.g. https://requires.io notifications ).

If you could tag the 3.1.11 with the Django 1.7 support it would make it a lot easier.

Radek

--
You received this message because you are subscribed to a topic in the Google Groups "Mezzanine Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mezzanine-users/GmcPsZZtKzQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mezzanine-use...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Radek Švarz

https://www.linkedin.com/in/radeksvarz

[eric.a...@gmail.com]

We need a release on PyPI that officially supports Django 1.7 in order to bundle our application into pex format for deployment. Do you have any idea when a release supporting Django 1.7 may be made available on PyPI?