django-1.7

I have two tables called Post and Reply . The users can create just one Response for each Post . The models look like this: class Post(models.Model): name = models.CharField(max_length = 100) class Reply(models.Model): post = models.ForeignKey(Post, related_name = 'replies') Now, I have a view that returns the posts, like this: class PostList(generics.ListAPIView): permission_classes = (permissions.IsAuthenticated,) queryset = Post.objects.all() serializer_class = PostSerializer And a serializer for the posts: class PostSerializer(serializers.ModelSerializer): class Meta: fields = ('id', 'name

I'm trying to translate a Django third-party app ( django-recurrence ) within my Django 1.7 project. Despite all the answers I've been reading here about the same problem, I'm still being unable to have Django generate the django.po for this app. These are my current settings: settings.py LANGUAGE_CODE = 'it-IT' gettext = lambda s: s LANGUAGES = ( ('en-us', gettext('English')), ('it-it', gettext('Italian')), ) LOCALE_PATHS = ( '/home/seether/.virtualenvs/mytime/lib/python2.7/site-packages/recurrence/locale',) TIME_ZONE = 'Europe/Rome' USE_I18N = True USE_L10N = True I've tried modifying LOCALE

I want to increase the length of the username in django from 30 to around 80, I know it may be duplicate question but the previous answers are not working, for example https://kfalck.net/2010/12/30/longer-usernames-for-django this is for Django 1.2. Did anyone try similar hack for Django>1.5 Thanks in advance In Django 1.5 and above, the recommended approach would be to create a custom user model . Then you can make the username field exactly as you want. I had the same problem few days ago. Finally, I ended just with cutting off first 30 characters of the (old) username (into the new database

I have inherited some code for an app that was written for Django 1.4. We need to update the codebase to work with Django 1.7, and eventually 1.8 as the next Long Term Support release. In a few places it uses the old style @transaction.commit_manually and with transaction.commit_manually: I do not know enough about transactions in general but I am trying to understand what they are used for, so I can either remove them (if unnecessary) or upgrade them to the newer set_autocommit(False) or equivalent. I have understood that transaction management in Django < 1.5 was not ideal, and too

I'm finally upgrading from Django 1.6 to 1.7, and removing South in the process. I followed the official Django instructions and removed all my old numbered migrations. Now I'm trying to run python manage.py makemigrations to get the new migrations to continue moving forward with 1.7's migrations module, but it completely hangs and the only output I get is the following: bash -cl "/Users/me/.virtualenvs/mysite-Dj17/bin/python /Applications/PyCharm.app/Contents/helpers/pycharm/django_manage.py makemigrations /Users/me/Coding/mysite" /Users/me/.virtualenvs/mysite-Dj17/lib/python2.7/site-packages

I'm trying to port my project to use Django 1.7. Everything is fine except 1 thing. Models inside tests folders. Django 1.7 new migrations run migrate command internally. Before syncdb was ran. That means if a model is not included in migrations - it won't be populated to DB (and also to test DB). That's exactly what I'm experiencing right now. What I do is: In my /app/tests/models.py I have dummy model: class TestBaseImage(BaseImage): pass All it does is to inherit from an abstract BaseImage model. Then in tests I create instances of that dummy model to test it. The problem is that it doesn't