Re: Migrations and Reusable Apps

> Le 1 juil. 2014 à 04:46, Sebastian Vetter > a écrit : > > As far as I remember, the explicit import of models was discourage in > favour of get_model(). Is that no longer the case with the new app > registry? Do you see portential problems with explicit import and the > app registry initialis

Re: Migrations and Reusable Apps

Hey Aymeric, thanks a lot for your immediate feedback. I appreciate that a lot. I've added a few comments inline. On 30/06/14 23:55, Aymeric Augustin wrote: > 2014-06-30 14:32 GMT+02:00 Sebastian Vetter > >: > > 1) Creating a subclass of AppConfig fo

Re: Migrations and Reusable Apps

2014-06-30 14:32 GMT+02:00 Sebastian Vetter < sebast...@roadside-developer.com>: 1) Creating a subclass of AppConfig for a Django app is (according to > the docs) not required. If none is defined, Django falls back to AppConfig. > > For a pluggable app, is it recommended to always subclass AppCon

Re: Migrations and Reusable Apps

Hi Andrew, hi Trey, as part of the migration to Django 1.7 I just mentioned in my post about the AppConfig, I've obviously also looked into migrations and I am a big fan :) For reference, the project in question is django-fancypages [1]. The route the I have taken for now is the same one describe

Re: Migrations and Reusable Apps

Hey Aymeric, hey all, it took a little longer than I hoped but I eventually managed to put together a few questions that came up while porting a pluggable app to Django 1.7 with backward-compatibility through to 1.4. I hope all of these make sense and I am looking forward to the feedback: 1) Crea

Re: Migrations and Reusable Apps

On Tuesday, June 24, 2014 6:07:05 AM UTC+2, Sebastian Vetter wrote: > > I appreciate the offer and will gladly take it :) I'm currently in the > middle of a migration to Django 1.7 incl. backwards-compatibility. I'm > collecting questions about best practises right now and would love to > get

Re: Migrations and Reusable Apps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey Aymeric, > At this point, I think you're the only person who reached out for > help :-) well, not anymore ;) > So, if anyone else is maintaining a third-party app and could use > tips about how to deal with app-loading, let me know and I'll do m

Re: Migrations and Reusable Apps

2014-06-17 19:33 GMT+02:00 Trey Hunner : > +1 that. This has been the hardest recent release for my own apps > (mostly because of the app-loading refactor). > > I'm grateful for the help I received while migrating > django-simple-history to 1.7. > At this point, I think you're the only person wh

Re: Migrations and Reusable Apps

Support of south_migrations directory in South goes a long way to addressing this problem from my perspective so that's very good news to me. On Tuesday, June 17, 2014 1:34:02 PM UTC-4, Trey Hunner wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/17/2014 10:05 AM, Andrew God

Re: Migrations and Reusable Apps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/17/2014 10:05 AM, Andrew Godwin wrote: > 1.7 is not going to be a pretty release for third-party apps for a > number of reasons: this, the app-loading refactor, the changes to custom > fields, and a few other things. I might leave an open offer o

Re: Migrations and Reusable Apps

Trey is correct about south supporting south_migrations. I'm going to try and get that release out this week so people can start preparing. As for the dire warning about unmigrated apps not relying on migrated ones, it's true that converting auth does this, although the very existence of AUTH_USER

Re: Migrations and Reusable Apps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Mark, I've left replies inline below. Note that I am not heavily involved with South development nor the Django 1.7 release so my perspective may be skewed from reality. On 06/17/2014 06:18 AM, Mark Lavin wrote: > Given that contrib.auth now has

Re: Migrations and Reusable Apps

This might be a solution for projects which wish to upgrade in advance of their dependencies but as you note its implications for future app upgrades are unclear. This still doesn't provide an answer for app developers. The deprecation timeline says migrations aren't required until 2.0. But if

Re: Migrations and Reusable Apps

I'm sure Andrew will have more info, but you could use MIGRATION_MODULES and generate migrations for any 3rd party apps that don't have them. I'm not sure how the transition when the app starts shipping its own migrations will go. On Tuesday, June 17, 2014 9:18:57 AM UTC-4, Mark Lavin wrote: >

Migrations and Reusable Apps

Hello, I noticed some changes over the past few days to the migrations and I was concerned about how this could impact reusable applications planning to support 1.7. In particular there is a note in https://docs.djangoproject.com/en/1.7/topics/migrations/#dependencies Be aware, however, that u