I think this has something to do with “The removal of ContentType.name“, according to this. But somehow it doesnt work. By manually removing the column name from ‘django_content_type’ table. Eg. ‘ALTER TABLE django_content_type DROP COLUMN name’ I was able to apply the migrations. Maybe this can get you a little bit further at least.
I had the same exception with Django 1.7rc2. The solution was to add these lines at the beginning of my program: import django django.setup() Update: This is now documented for Django 1.8.
Set debug in OPTIONS dictionary of your templates settings. DEBUG = True TEMPLATES = [ { … ‘OPTIONS’: { ‘debug’: DEBUG, }, }, ] Then remove this line from your settings to stop the warnings TEMPLATE_DEBUG = DEBUG See the Django docs for detailed instructions how to update your template settings.
The function datetime.now() is currently executed as soon as your code is imported, i.e. when you (re)start your server. All subsequent model instances will have the same value. Instead, you should pass a callable function to default, that is executed each time a model instance needs a default value. The hint wants to convey that … Read more
If you run $ python manage.py createsuperuser Superuser creation skipped due to not running in a TTY. You can run manage.py createsuperuser in your project to create one manually. from Git Bash and face the above error message try to append winpty i.e. for example: $ winpty python manage.py createsuperuser Username (leave blank to use … Read more
You should first set your current state to 0003 with –fake (assuming 0003 is the last migration you really have applied): python manage.py migrate –fake core 0003 And then proceed as usual: python manage.py migrate core Relevant documentation: https://docs.djangoproject.com/en/dev/ref/django-admin/#migrate
I fix this by running auth first, then the rest of my migrations: python manage.py migrate auth python manage.py migrate
select_related should be use on the whole model, and then you can filter it more. This will work: Articles.objects.select_related(‘blog’).only(‘blog__name’, ‘title’, ‘create_time’)
syncdb is deprecated because of the migration system, introduced with django 1.7. Now you can track your changes using makemigrations. This transforms your model changes into python code to make them deployable to another databases. When you have further modifications you need applied to the database, you can use data migrations. After you created the … Read more
I believe the reason is that your setUpClass(cls) class method is not calling super. Because of that, django.tests.TestCase.setUpClass is not called and cls.cls_atomics = cls._enter_atomics() is not called, naturally causing cls_atomics to be undefined. You should add super(ATestTests, cls).setUpClass() to your setUpClass.