Django-cities

Latest version: v0.6.2

Safety actively analyzes 681844 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 10

3.5.0

Fix lack of support of Django 2.0 by django_autoslug 174 by wswld
Changes dependency from django-autoslug to django-autoslug-iplweb, that
works with Django 2.0, and which is maintained by mpasternak

3.4.0

- Drop support for django<1.8 and django-rest-framework<3.4
- Fix memory widget units on OS X
- Remove support for django-autocomplete-light v1 (157)
- Update django-rest-framework and django-ajax-selects
- Use custom Django>=1.7 lookup to remove spaces from search query string
- Update model customization docs for Django 1.9
- Add timezone support
- Compatibility with Django 2.0
- Compatibility with Django 1.11
- Move name field to Base model, make not unique
- 136: Creating a ModelSerializer
- 127: Adds the possibility to customize the alternate_names separator
- Fix unidecode warning and add unit test for to_ascii
- Switch Country/Region/City lists to sets (speedup)
- Call connection.close() only for MySQL (speedup)
- Disable progressbar by default (speedup)
- Call reset_queries only in DEBUG mode (speedup)
- Make dump_fixture APP_NAME aware
- Adds migration step in README.rst
- improve help text formatting for management commands
- fix positional argument handling on django 1.10 for cities_light_fixtures command

3.3.0

- 118: Add Django 1.10 support, drop Django 1.7 support by jpic
- 113: Fix DeprecationWarning by mbaragiola
- 106: New management command to work with fixtures by max-arnold
- 108: translation_items_pre_import_signal by FaBay89
- 106: New management command feature by greeday2

3.2.0

- 105: Drop LazyProgressBar, patch was accepted upstream by max-arnold,
- 104: Better feature code filtering by max-arnold,
- 100, 96: The mistery about migrations appearing in some
environments but not others has been solved: it was due to the
presence of b'' in migration files. A new test was added to fail if
django wants to create new migrations in any environment.
- Phone number was required to create a country, it's not anymore.
- Support Django 1.7 to 1.9, thanks suquant for helping,
- Support for 1.7 will drop when 1.10 is released, unless someone
contributes compatibility in cities_light options declaration,
- Bugfix in import: some search names would not be generated in some
cases due to unpredictability of the iteration order on
translation_data.items()
- Test with django-dbdiff are much faster than importing the whole data
- Tox for testing, coverage

3.1.2

Django 1.8 compatibility by suquant

3.1.1

Use named indexes for geonames data contributed by Alexey Evseev.

Page 2 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.