Re: Migrations, commands and syncdb

On Fri, May 31, 2013 at 2:03 AM, Andrew Godwin wrote: > Hi everyone, > > I'm starting to plan out the commands for the new migrations stuff in > Django, and I've hit something of an impasse trying to decide which option > to go for. > > Short background: South modified

Re: Migrations, commands and syncdb

I haven't used South as much as I should have (instead I have painful > manual scripts to do migrations). The biggest pain point about > database schemas for me is easily test database setup. That is, sync > from scratch. I do the following currently: > 1. load schema + a little bit of data from

Re: Migrations, commands and syncdb

On 30 touko, 21:03, Andrew Godwin wrote: > I prefer option 3, but getting rid of syncdb might be controversial, so I > want to ask for people's opinions. syncdb would continue to exist for at > least 3 versions if not forever; it would just be an alias to run "migrate" > in

Re: Migrations, commands and syncdb

Hi all, On Thursday 30 May 2013, Andrew Godwin wrote: > > The proposals are: > > 1. Change syncdb so that it both does the old behaviour (adds models for > unmigrated apps), and additionally runs any outstanding migrations. There > would be a separate "migrate" command for more complex

Re: Migrations, commands and syncdb

On 30.05.2013, at 20:03, Andrew Godwin wrote: > Hi everyone, > > I'm starting to plan out the commands for the new migrations stuff in Django, > and I've hit something of an impasse trying to decide which option to go for. > > Short background: South modified syncdb to

Re: Migrations, commands and syncdb

On 05/30/2013 12:03 PM, Andrew Godwin wrote: > The proposals are: > > 1. Change syncdb so that it both does the old behaviour (adds models > for unmigrated apps), and additionally runs any outstanding migrations. > There would be a separate "migrate" command for more complex operations, > such

Re: Migrations, commands and syncdb

I'm broadly +1 on deprecating syncbd, it's possibly the most inaccurately named thing in all of Django (hint: it doesn't sync anything). Alex On Thu, May 30, 2013 at 11:03 AM, Andrew Godwin wrote: > Hi everyone, > > I'm starting to plan out the commands for the new

Migrations, commands and syncdb

Hi everyone, I'm starting to plan out the commands for the new migrations stuff in Django, and I've hit something of an impasse trying to decide which option to go for. Short background: South modified syncdb to just sync non-migrated apps, and you had to go and run migrate separately to get

Re: Perception of attitude in tickets

Sorry I'm late back to the party boys and girls. Trivial as it may be, it's really just communication that's the only issue here, and I'm glad this has prompted a review. We all mean well and we're eager to help. The solutions Cal, Russ, Luke and co have discussed sound great. BTW- there

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

> > I must say that reading this into Russel (and other)'s replies is very > far fetched (language as well as content), uncalled for, and seems to > expose an assumption that the people here prefer the easy path of swatting > suggestions with a quick "nay". I 'd say the opposite is much

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

Hello Jorge, On Thu, 30 May 2013 12:42:20 +0300, Jorge C. Leitão wrote: Hi Russell Keith-Magee. Thanks for your criticisms. Let's see if I can answer some of them. I'd turn this question back onto you -- why *should* the search start locally? What collisions

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

Hi Russell Keith-Magee. Thanks for your criticisms. Let's see if I can answer some of them. > I'd turn this question back onto you -- why *should* the search start > locally? What collisions are you seeing between apps that makes a global > search impractical? Very good question! I think

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

On 30 May 2013 10:20, Jorge C. Leitão wrote: > > On Thursday, May 30, 2013 7:54:40 AM UTC+2, Shai Berger wrote: >> > > Why python allows nested apps? Python allows nested *modules* because namespaces are good. Also because without it you would have to wither write every

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

Hi Shai Berger and thanks for your quick response. Regarding your criticisms, On Thursday, May 30, 2013 7:54:40 AM UTC+2, Shai Berger wrote: > > Actually, Django doesn't. That is, an app is a Python package, and Python > packages can be nested, so you can have app 'b' within app 'a', and in >

Re: Proposal/Discussion: url and template search using the directory structure of apps within django sites

On Wed, May 29, 2013 at 4:04 PM, Jorge C. Leitão wrote: > Hi there. > > Django allows the possibility of putting apps within apps to improve > structure of the code and increase portability. I find this absolutely > genial. > > However, I find this feature quite limited