Django-countries

Latest version: v7.6.1

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

Scan your dependencies

Page 6 of 10

5.0

=====================

* No longer allow ``multiple=True`` and ``null=True`` together. This causes
problems saving the field, and ``null`` shouldn't really be used anyway
because the country field is a subclass of ``CharField``.

4.6.2

-----

* Use transparency layer for flag sprites.

4.6.1

-----

* Fix invalid reStructuredText in CHANGES.

4.6

==================

* Add a ``CountryFieldMixin`` Django Rest Framework serializer mixin that
automatically picks the right field type for a ``CountryField`` (both single
and multi-choice).

* Validation for Django Rest Framework field (thanks Simon Meers).

* Allow case-insensitive ``.by_name()`` matching (thanks again, Simon).

* Ensure a multiple-choice ``CountryField.max_length`` is enough to hold all
countries.

* Fix inefficient pickling of countries (thanks Craig de Stigter for the report
and tests).

* Stop adding a blank choice when dealing with a multi-choice ``CountryField``.

* Tests now cover multiple Django Rest Framework versions (back to 3.3).

4.5

===================

* Change rest framework field to be based on ``ChoiceField``.

* Allow for the rest framework field to deserialize by full country name
(specifically the English name for now).

4.4

==================

* Fix for broken CountryField on certain models in Django 1.11.
Thanks aktiur for the test case.

* Update tests to cover Django 1.11

Page 6 of 10

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.