Re: Major features for 1.9

That one has already landed On 17 July 2015 at 18:43, Christian Schmitt wrote: > Didn't you missed jsonb from Marc Tamlyn aswell? It's one of the greatest > features for Postgresql > > Am Freitag, 17. Juli 2015 19:19:38 UTC+2 schrieb Tim Graham: >> >> Currently we have two items on the roadmap:

Re: Major features for 1.9

Didn't you missed jsonb from Marc Tamlyn aswell? It's one of the greatest features for Postgresql Am Freitag, 17. Juli 2015 19:19:38 UTC+2 schrieb Tim Graham: > > Currently we have two items on the roadmap: > https://code.djangoproject.com/wiki/Version1.9Roadmap > > PostgreSQL Full Text Search <

Major features for 1.9

Currently we have two items on the roadmap: https://code.djangoproject.com/wiki/Version1.9Roadmap PostgreSQL Full Text Search (Marc Tamlyn) Custom indexes (Marc Tamlyn) Hopefully we can add Marten's URLs GSoC p

Re: Why Django is making migrations for external apps?

On 07/17/2015 10:38 AM, Marcin Nowak wrote: > Sounds enough good. One important thing for me is that I have many of > external apps and few in project managed by me. Reconfiguring most of > apps just to tell Django "leave them alone" sounds like an overhead. > That's why I would like to tell Django

Re: Why Django is making migrations for external apps?

Sounds enough good. One important thing for me is that I have many of external apps and few in project managed by me. Reconfiguring most of apps just to tell Django "leave them alone" sounds like an overhead. That's why I would like to tell Django "here are my apps, manage them please". BR Marcin

Re: Why Django is making migrations for external apps?

On Friday, July 17, 2015 at 6:31:20 PM UTC+2, Andrew Godwin wrote: > > > > On Fri, Jul 17, 2015 at 11:19 AM, James Bennett > wrote: > >> One option for declaring an app "unmanaged" could be via AppConfig. >> That's fairly clean, mirrors the way you can already set a model as >> unmanaged in it

Re: Why Django is making migrations for external apps?

+1! Loïc > On Jul 17, 2015, at 23:30, Andrew Godwin wrote: > > > > On Fri, Jul 17, 2015 at 11:19 AM, James Bennett wrote: > One option for declaring an app "unmanaged" could be via AppConfig. That's > fairly clean, mirrors the way you can already set a model as unmanaged in its > Meta decl

Re: Why Django is making migrations for external apps?

On Fri, Jul 17, 2015 at 11:19 AM, James Bennett wrote: > One option for declaring an app "unmanaged" could be via AppConfig. That's > fairly clean, mirrors the way you can already set a model as unmanaged in > its Meta declaration, and allows for the end user of the app to override by > supplying

Re: Why Django is making migrations for external apps?

One option for declaring an app "unmanaged" could be via AppConfig. That's fairly clean, mirrors the way you can already set a model as unmanaged in its Meta declaration, and allows for the end user of the app to override by supplying an AppConfig which will generate migrations (should they, for so

Re: Why Django is making migrations for external apps?

If we're going to introduce another setting, which I'm not super-keen on, then let's made it exclusionary, something like MIGRATION_UNMANAGED_APPS. Or, we could do something with the existing MIGRATION_MODULES setting, but migrate needs that too so it might be confusing things. Andrew On Fri, Ju

Re: Why Django is making migrations for external apps?

I would like to set something like MIGRATION_MANAGED_APPS = (...) in my project`s settings. Every not listed app should not be inspected and should be excluded when calling `makemigrations` command. Setting MIGRATION_MANAGED_APPS to None (default) should enable backward compatibility. On 17 July

Re: Why Django is making migrations for external apps?

On Thursday 16 July 2015 02:10:12 Andrew Godwin wrote: > > Also, yes, Django doesn't see unpacked .egg files as any different than > anything else (they're just directories after all) - we have no way of > telling which apps are yours and which are external, really. In my experience, most project