Changelog

v2.0.0 (2022-05-03)

Breaking

• Dropped support for Python 3.5 and 3.6 (both have reached EOL).

New

• Add support for Python 3.9, 3.10, and added 3.11 pre-releases to test-suite.
• Fully annotated the project and added a py.typed to make the package PEP 561-compliant.
• Added a get_minimum_due_date utility function for retrieving the earliest valid due date for a payment request.
• Added a validate_due_date kwarg to the add_payment_request Assignment method, to optionally perform due date validation. When enabled, due dates less than the minimum (4 calendar days in the future, offset by holidays) or more than the maximum (12 months in the future) will raise an exception.

Internal

• Switched CI pipeline from CircleCI to Github actions.
• Added isort, black, pyupgrade, and pre-commit for linting.
• Switched to Poetry for package and dependency management.

v1.3.0 (2020-06-10)

• Drop support for Python 3.4, which has reached end of life.
• Python 3.8 is now explicitly supported. No changes was required to the library, but the test suite now runs on Python 3.4, 3.5, 3.6, 3.7 and 3.8.

v1.2.0 (2018-11-22)

• Python 3.7 is now explicitly supported. No changes was required to the library, but the test suite now runs on Python 3.4, 3.5, 3.6, and 3.7.
• Require attrs >= 17.4, and replace all use of the deprecated keyword argument convert with converter so that netsgiro can continue working with attrs relases after January 2019.
• Format code with Black.

v1.1.0 (2017-10-23)

Record parsing and writing are now tested with an additional suite of property based tests, using the Hypothesis library. This testing effort identified a number of issues, all of which are fixed by this release.

• Fixed exception in netsgiro.records.TransactionAmountItem2.to_ocr() if payer_name was None.

• Fixed exception in netsgiro.records.TransactionAmountItem3.to_ocr() if text was None.

• Raise a ValueError if a too long string is used for any of:

  • netsgiro.records.TransactionAmountItem1.kid (max 25 chars)
  • netsgiro.records.TransactionAmountItem3.text (max 40 chars)
  • netsgiro.records.TransactionSpecification.text (max 40 chars)
  • netsgiro.records.AvtaleGiroAgreement.kid (max 25 chars)

  Previously the string was accepted and the record generated invalid OCR data.

• Strip newline characters (\n and \r) from record strings, like netsgiro.records.TransactionAmountItem2.payer_name.

  Previously the newline characters were accepted and the record generated invalid OCR data.

• Automatically pad netsgiro.records.TransactionSpecification.text to 40 chars, so that a manually created record and a record parsed from OCR are identical.

v1.0.0 (2017-05-20)

No changes from v1.0.0a3, which has been used in production for a few weeks without any issues.

v1.0.0a3 (2017-05-03)

• Rename netsgiro.TransactionType.AVTALEGIRO_AGREEMENTS (plural) to netsgiro.TransactionType.AVTALEGIRO_AGREEMENT (singular).
• When writing record to OCR, cut netsgiro.records.TransactionAmountItem2.payer_name to 10 first chars, as that is all the field has room for.

v1.0.0a2 (2017-04-26)

Major improvements and changes.

• The objects API now supports parsing all known file variants with netsgiro.parse() and can recreate the parsed OCR data perfectly with netsgiro.Transmission.to_ocr().
• The objects API now does all the bookkeeping necessary for building payment requests. With this improvement, the code necessary to produce a payment request is cut to from around 100 to 25 lines of code.
• New quickstart guide shows how to parse files and build payment requests.
• All public methods and fields of both the objects API and records API are now documented.
• The low-level records API has been moved to the netsgiro.records module.

v1.0.0a1 (2017-04-17)

Initial alpha release. No promises about backwards compatibility.