Re: Infinite loop in migration code

2014-11-27 Thread Luke Plant
Hi Markus, It was basically this: == app camps == class Camp: invited_officers = M2M(auth.User, through='officers.Invitation') == app officers == class Invitation: timestamp = models.DateTimeField(default=datetime.now) camp = FK(camps.Camp) user = FK(auth.User) = I ran makemi

Re: Infinite loop in migration code

2014-11-27 Thread Markus Holtermann
Hey Luke, I cannot reproduce your problem on neither master nor stable/1.7.x. When I run "python manage.py makemigrations camps" the migrations for the "officers" app are also generated (as I expect it). "testapp" is your "camps" app, "otherapp" is your "officers" app: https://gist.github.com/

Re: DB Migrations: Proposed fix for "Index name collisions after objects are renamed then re-created"

2014-11-27 Thread Shai Berger
Hi, Just noted this thread, and I have two points: 1) Using the migration name in the index isn't really "predictable", and isn't even completely stable (the name changes when migrations are squashed), unless I'm missing something. 2) The current practice of identifying indexes by the columns

Adding hard dependencies to Django's test suite

2014-11-27 Thread Tim Graham
There have been some proposals to add new dependencies in Django's test suite: 1. #23289 - unittest.mock (included in Python 3.3+; a backport version would need be installed when testing on Python 2.7 and 3.2) 2. #23792

Re: Adding hard dependencies to Django's test suite

2014-11-27 Thread Fabio Caritas Barrionuevo da Luz
python 2.7.9 rc1 include a backported version of python3 ensurepip see: https://hg.python.org/cpython/rev/592a5414fabd https://docs.python.org/2/library/ensurepip.html -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django its

Re: DB Migrations: Proposed fix for "Index name collisions after objects are renamed then re-created"

2014-11-27 Thread Florian Apolloner
On Thursday, November 27, 2014 9:44:28 PM UTC+1, Shai Berger wrote: > > 1) Using the migration name in the index isn't really "predictable", and > isn't > even completely stable (the name changes when migrations are squashed), > unless > I'm missing something. > I think squashing isn't an i