Jacek Tomaszewski

Can you be more verbose, please? You have something like `fields = ['a', 'b']` and then you added two new fields, so that it now reads `fields = ['a', 'b',...

I'm puzzled. Some debugging is needed and I'm sorry that you're running out of time. Can you try to run `sync_translation_fields` command without new fields added and test if it...

You're bloody right. We haven't concerned unregistration much, but it should unpatch models.

It's something to think about. For me nulling is proper - there are some types of fields (like IntegerFIeld) where there is no 'empty value' other than null.

Of course, if we make #143, we won't set `null=True` on the required fields. But I think it's necessary on non-required ones. And we may change behaviour to not set...

Working with #122 made me change my mind - there are situations when nulling may not be appropriate. There is a fine looking field property called `empty_strings_allowed`. Maybe we could...

So... Shall we make a revolution?

#163 is related, but it doesn't present different approach to the same problem, but rather different problem. So to say, revolution wouldn't affect that problem, because in #163 there is...

How referenced issue is connected with this?

As you noticed, things are not going anyhow. :( I'm very busy right now, and I suspect that @deschler too. However, look at the https://github.com/deschler/django-modeltranslation/blob/master/modeltranslation/fields.py#L215. If default value is set...