Hi, Storing your files in dropbox _should_ be fine, unless it's a problem with *.pyc or __pycache__ files.
Collin On Tuesday, December 9, 2014 2:38:31 PM UTC-5, Tobias Dacoir wrote: > > Hi, > > I'm afraid I don't have them. Apparently after deleting my database file > and then just running manage.py makemigrations, it deleted the old > migration files and started anew. Right now I'm also unable to re-produce > it on purpose :( But it happened a couple of times for me since I regularly > make multiple changes to my model (I'm still at the beginning of > development) but if I just add a single new field now it works as expected. > > Maybe sometimes Django can't detect changes to my file because I store my > project in my dropbox folder and maybe this might be messing it up? > > On Monday, December 8, 2014 1:04:37 PM UTC+1, Markus Holtermann wrote: >> >> I tried to reproduce the problem with the steps you explained, but it >> works fine for me. Can you post your existing migration files for that app >> too, please. This will then hopefully give us some hints to solve your >> problem. >> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/edad6a10-8d84-4513-8074-05a94650d014%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
