0006018: The python taler-util Amount class is unnecessarily hard to use

ID	Project	Category	View Status	Date Submitted	Last Update
0006018	Taler	other	public	2019-12-28 15:14	2020-03-31 14:04

Reporter	Florian Dold	Assigned To	Florian Dold	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed

Summary	0006018: The python taler-util Amount class is unnecessarily hard to use
Description	There is no reason for the Amount class to be mutable. It is difficult to even create a copy of an Amount.
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-12-28 15:14	Florian Dold	New Issue
2020-01-07 16:41	Florian Dold	Note Added: 0015238
2020-01-07 18:17	Florian Dold	Assigned To	=> Florian Dold
2020-01-07 18:17	Florian Dold	Status	new => assigned
2020-01-15 15:43	Florian Dold	Status	assigned => informing
2020-01-15 15:43	Florian Dold	Resolution	open => fixed
2020-01-15 15:43	Florian Dold	Note Added: 0015279
2020-03-31 14:04	Christian Grothoff	Status	informing => closed

Florian Dold 2020-01-07 16:41 manager ~0015238	Oh and we also need something to handle negative amounts, since currently "zero crossing" must be implemented manually, which is very error-prone.

Florian Dold 2020-01-15 15:43 manager ~0015279	We now have an immutable amount class, as well as an immutable SignedAmount class.