-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
django-localflavor 2.0 - release compatible with Django 2.0 #322
Comments
Do you know when 2.0 will be officially released? |
I'm hoping to release 2.0 before the end of the year. Our official target is within one month of the compatible Django release. Having my Django 2.0 PR at least merged in django-phonenumber-field is the only real blocker but I'm not planning to extend the one month target just for this. |
@claudep Could you update the translations to prepare for the 2.0 release if you have a chance in the next couple of days? Thanks! |
Done. |
Thanks Claude. I've just released django-localflavor 2.0. |
I'm filing this issue as a place to discuss the upcoming 2.0 release of django-localflavor.
I'd like to get this release out as soon as possible. The only thing blocking this release is django-phonenumber-field's missing support for Django 2.0. Since we're removing the phone number fields in localflavor, there should be an option for users to migrate to. I made a PR to fix this already but I'd like to have it merged into the django-phonenumber-field repo before cutting the release.
stefanfoulis/django-phonenumber-field#196
If you need to use django-localflavor with Django 2.0, you can use the master branch until this is released. If you need to use phone number fields with Django 2.0, you'll have to use the code in my PR to django-phonenumber-field until it's merged / released.
The text was updated successfully, but these errors were encountered: