Django-hordak

Latest version: v1.17.0

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

Scan your dependencies

Page 2 of 6

1.14.0

===============================
* ``transfer_to()`` on ``Account`` is now deprecated and raises a warning
in favor of ``accounting_transfer_to()``. It performed transfers differently
than expected when comparing it to Dr/Cr double entry accounting, see function notes.

This function will raise an error in Hordak 2.0.
* Now using Django's locale to ``Balance.__str__``'s ``format_money`` allowing better formatting and specs.
* Changed ``Account.currencies`` from ``ArrayField => JSONField`` to allow database agnostic work.

* **Breaking Change**

* ``Account.currencies`` input must be valid JSON now.
* This is mostly important in 2 areas

* ``Forms``, but also if you performed a ``", ".join(currencies_str_arr)``.
* ``Fixtures``

* Previous: ``EUR, USD`` => ``["EUR", "USD"]``
* Form complains if it is not valid JSON and returns an explanation.

* MySQL support

* Migrations and triggers modified to target MySQL whilst maintaining compatibility with postgres

1.13.0

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

* CURRENCIES can be also defined as HORDAK_CURRENCIES to allow to
get rid of Django warning and to avoid name collision with django-money.
The value can be function.

1.12.0

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

* fixes of treating unknown currencies

1.11.1

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

* Fix for django-import-export 3.0.0 and remove hold back version in requirements

1.11.0

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

* Quicker admin listings (especially when installed with ``pip install hordak[subqueries]``
* More informations and filters in admin views
* Test also in Django 4.1

1.10.2

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

* Fix AccountTransactionsView

Page 2 of 6

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.