Re: Django 1.8 Migrations: AlterField Migration calls default callable for ForeignKey even when no Model Instances Exist

Hi, I think the issue is described in https://code.djangoproject.com/ticket/24182. On Tuesday, March 14, 2017 at 12:50:52 PM UTC-4, Dylan Young wrote: > > Steps to reproduce: > > Create Model > Make migrations > Add FK to model with a callable default that has some side effect (e.g. > creating

Re: Opportunity to contribute in Django

Hi Jainesh, Have a look at this page which should give you an idea about where to start: https://docs.djangoproject.com/en/1.10/intro/contributing/#finding-your-first-real-ticket On Monday, 13 March 2017 13:52:34 UTC, Jainesh Patel wrote: > > Hello, > > I am a final year CSE student from PICT,

Re: Feature idea: forms signals

I've put together a brief proof of concept here: https://github.com/seddonym/formsignals It demonstrates what you could do with post_init, post_clean and post_save signals, which I've also implemented in a fork of Django (no test coverage or documentation yet though). The concept it

Django 1.8 Migrations: AlterField Migration calls default callable for ForeignKey even when no Model Instances Exist

Steps to reproduce: Create Model Make migrations Add FK to model with a callable default that has some side effect (e.g. creating the default instance in the database) Make migrations Migrate (or run tests on clean db) Observe the side effect I couldn't find this on the Bug Tracker. Is this