Merge branch 'bump-version'

Bump version number to 5.0a9
Upgrade django-postgres-extra to 1.21a16
2025-10-19 06:18:57 +03:00 · 2019-02-21 12:54:04 +02:00 · 2019-02-21 12:50:58 +02:00 · 2019-02-21 12:50:46 +02:00 · 2019-02-21 12:47:15 +02:00 · 2019-02-21 12:34:22 +02:00
3 changed files with 4 additions and 4 deletions
--- a/README.rst
+++ b/README.rst
@@ -279,7 +279,7 @@ Besides ``LocalizedField``, there's also:

    Allows storing integers in multiple languages. This works exactly like ``LocalizedField`` except that
    all values must be integers. Do note that values are stored as strings in your database because
-    the backing field type is ``hstore``, which only allows storing integers. The ``LocalizedIntegerField``
+    the backing field type is ``hstore``, which only allows storing strings. The ``LocalizedIntegerField``
    takes care of ensuring that all values are integers and converts the stored strings back to integers
    when retrieving them from the database. Do not expect to be able to do queries such as:

--- a/localized_fields/value.py
+++ b/localized_fields/value.py
@@ -233,4 +233,4 @@ class LocalizedIntegerValue(LocalizedValue):
        """Returns string representation of value"""

        value = self.translate()
-        return str(value) if value is not None else None
+        return str(value) if value is not None else ''
--- a/setup.py
+++ b/setup.py
@@ -33,7 +33,7 @@ with open(os.path.join(os.path.dirname(__file__), 'README.rst'), encoding='utf-8

 setup(
    name='django-localized-fields',
-    version='5.0a7',
+    version='5.0a9',
    packages=find_packages(exclude=['tests']),
    include_package_data=True,
    license='MIT License',
@@ -44,7 +44,7 @@ setup(
    author_email='open-source@sectorlabs.ro',
    keywords=['django', 'localized', 'language', 'models', 'fields'],
    install_requires=[
-        'django-postgres-extra>=1.21a15',
+        'django-postgres-extra>=1.21a16',
        'Django>=1.11',
        'deprecation==2.0.3'
    ],
Author	SHA1	Message	Date
Swen Kooij	f0ac0f7f25	Merge branch 'bump-version'	2019-02-21 12:54:04 +02:00
Swen Kooij	93ffce557c	Bump version number to 5.0a9	2019-02-21 12:50:58 +02:00
Swen Kooij	7c432baec7	Upgrade django-postgres-extra to 1.21a16	2019-02-21 12:50:46 +02:00
Swen Kooij	476a20ba88	Merge pull request #61 from SectorLabs/bump-version Bump version number to 5.0a8	2019-02-21 12:47:15 +02:00
Swen Kooij	ad99b77bcd	Bump version number to 5.0a8	2019-02-21 12:34:22 +02:00
Swen Kooij	151250505d	Merge pull request #60 from AdrianMuntean/error_on_empty_localized_integer_field Return empty string in case the LocalizedIntegerField is null	2019-02-21 12:31:50 +02:00
Adrian Muntean	d8b872758c	Return empty string in case of None	2019-02-20 12:26:04 +02:00
Adrian Muntean	a0ca977cab	Set None in case the LocalizedIntegerField is null In case the LocalizedIntegerField is null in the DB then it must explicitly be set to None, otherwise it will yield TypeError: __str__ returned non-string	2019-02-14 14:48:38 +02:00