local-flavor NL: add model fields, renaming, testing, deprecating. about django-localflavor HOT 10 CLOSED

Point 1: Some users may actually still want to store the old Dutch bank numbers but I don't know for sure. I suppose the question is really about whether localflavor should keep historical fields or not. If we were to remove the NLBankAccountNumber* fields, they would need to be depreciated first and I think it would be better to file a separate issue to solve this generally for all the SEPA bank fields in localflavor.

Point 2 and Point 3: You would need to provide South and native Django migrations for anything you want to rename. Although I don't know off hand what the localflavor policy for renaming fields is.

@jezdez @erikr @claudep Are any of you guys able to provide more information here? Thanks.

from django-localflavor.

On point 1: I think we should deprecate all local bank account fields, in countries where IBAN has become mandatory. By mandatory I mean that in the Netherlands, I can no longer enter an old form account number in a bank transfer, and the conversion service has shut down. So there is no possible use for an old form account number anymore. I believe this is part of SEPA, and therefore required in all SEPA countries. For non-SEPA IBAN countries we should then keep the existing field. Also, special territories of some countries are excluded from SEPA, like Greenland or Sint Maarten, so if they still use the Danish/Dutch old formats, we need to keep the fields of that country.

Point 2: I'm not sure whether wikipedia is (still) correct regarding the edge case: it seems there is (now) a special registration for niet-ingezetenen which does get you a BSN. I do think we should rename the field, but with a deprecation step for the old name. I'm not sure how this fits in with migrations (perhaps it'll just work).

Point 3: I like consistency, but I don't think the benefits outweigh the inconvenience for all the users. So I'm not inclined to rename them.

from django-localflavor.

@benkonrath @erikr Thanks for your comments on this. I'll look into it later this week and propose a change we can discuss after that.

from django-localflavor.

@jieter Is it safe to assume that you closed this issue because you're not planning to work on this any more? I'm planning to setup a deprecation policy for localflavor. Would you be interested in doing the SofiNumber -> BSN rename in the Dutch localflavor after my work has landed?

from django-localflavor.

Hmm, I was to quick in closing this. Might be better to create a new issue of the rename though, I'm willing to work on it then

from django-localflavor.

@jieter If you're still interested in working on this, now would be a good time. There are a few examples of deprecations in the code base that you can use to help you get started. Just search for RemovedInLocalflavor20Warning.

from django-localflavor.

I can invest some time in about two weeks.

from django-localflavor.

#307.

Regarding the comment of @erikr about special terratories of The Netherlands: I don't think that applies as they have a different country code, so it doesn't make sense to save it in a NLBankAccountNumberField.

For example, Sint Maarten

from django-localflavor.

@jieter I deprecated the SoFiNumber fields and added BSN fields in #314. Are you still interested in renaming the form fields? If not, this issue can be closed. Renaming the NL form fields would need to happen in the django-localflavor 2.x release cycle.

from django-localflavor.

Hmm, I think it's not worth the effort, lets keep them like they are...

from django-localflavor.