Re-open ticket 25192

Hello, Ticket #25192[1] is about a problem that only affects Python 2 users: If you write a migration with a `RunPython` operation, and you use the documented `RunPython.noop` as the reverse action (or forward action, but that is much less likely...), then all looks well, until you try to squas

Django 1.11 indexes

Hi Everyone, Do I understand this correctly - now there are 2 ways to make a single field indexed in database: - FieldClass(db_index=True) - Model.Meta.indexes will it stay like this for future release or 1st approach will be deprecated/removed later ? -- You received this message because

Django shell on django admin site

Hi everyone. I created small application which can execute python code in django project environment. Maybe someone will be interested and has any suggestions. django-admin-shell: https://github.com/djk2/django-admin-shell -- You received this message because you are subscribed to the Google Gr

Fellow Report - January 28, 2017

There were more cleanups for the removal of Python 2 this week: https://code.djangoproject.com/ticket/23919. I think it’s mostly done now. Triaged --- https://code.djangoproject.com/ticket/27765 - Migration to delete child model (multi-table inheritance) results in an error when using SQ

Re: Default custom reverse manager

Did you check if the manager changes in Django 1.10 could help? (By the way, usage questions should be asked on the django-users list). https://docs.djangoproject.com/en/stable/releases/1.10/#manager-use-for-related-fields-and-inheritance-changes On Wednesday, January 25, 2017 at 10:36:58 AM UTC-