Migrating Model Fields to django-localflavor
Add localflavor to your INSTALLED_APPS and then change the model fields IBANField and``SWIFTBICField`` to the versions from django-localflavor.
For example, the django-iban model fields should be changed from this:
from django_iban.fields import IBANField, SWIFTBICField
class CustomerModel(models.Model):
iban = IBANField()
bic = SWIFTBICField()
to the django-localflavor model field versions:
from localflavor.generic.models import IBANField, BICField
class CustomerModel(models.Model):
iban = IBANField()
bic = BICField()
For Django < 1.7, you will need to use South to migrate your database. Use schemamigration to create a migration and then run migrate alter your database. For example:
% ./manage.py schemamigration myapp --auto convert_django_iban_to_django_localflavor ~ Changed field iban on myapp.CustomerModel ~ Changed field bic on myapp.CustomerModel Created 0002_convert_django_iban_to_django_localflavor.py. You can now apply this migration with: ./manage.py migrate myapp % ./manage.py migrate myapp Running migrations for myapp: - Migrating forwards to 0002_convert_django_iban_to_django_localflavor. > myapp:0002_convert_django_iban_to_django_localflavor - Loading initial data for myapp. Installed 0 object(s) from 0 fixture(s)
For Django >= 1.7, run makemigrations to create a migration and then run migrate alter your database. For example:
% ./manage.py makemigrations myapp
Migrations for 'myapp':
0002_auto_20150210_1004.py:
- Alter field bic on customermodel
- Alter field iban on customermodel
% ./manage.py migrate myapp
Operations to perform:
Apply all migrations: myapp
Running migrations:
Applying myapp.0002_auto_20150210_1004... OK
Migrating Form Fields to django-localflavor
Change the form fields IBANFormField and SWIFTBICFormField to the versions from django-localflavor.
For example, the django-iban form fields should be changed from this:
from django_iban.forms import IBANFormField, SWIFTBICFormField
class CustomerForm(forms.Form):
iban = IBANFormField()
swift_bic = SWIFTBICFormField()
to the django-localflavor form field versions:
from localflavor.generic.forms import IBANFormField, BICFormField
class CustomerForm(forms.Form):
iban = IBANFormField()
bic = BICFormField()
1 maintainer
Metadata
1 maintainer
Release files for django-iban 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-iban-0.3.1.tar.gz | 14.4 kB | Without provenance | Details |
Release files / django-iban-0.3.1.tar.gz
| Download URL | django-iban-0.3.1.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26a2d623ccf876f70f273bd2a24ddf72e601045d89d759d4062dcd0bd0a8a874
|
|
BLAKE2b-256 checksum How to use checksums |
cdab3722c41fc79ca78b9f3f9addf43bcd876f7e8e4fdbf0ae1392b528e42d6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-iban 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
