- Jan 05, 2019
-
-
-
-
-
-
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
-
hydrargyrum authored
Tags: - Projects list possible tags - Issues can have a list of tags - Query supports tags Custom fields: - Projects list custom fields - Query supports custom fields Other: - Issues can have a list of related issues - Query fields are not only StringField but support the relevant classes - iter_issues can be sorted
-
- Jan 03, 2019
-
-
- Jan 02, 2019
-
-
Romain Bignon authored
-
Romain Bignon authored
-
Romain Bignon authored
-
Romain Bignon authored
-
Romain Bignon authored
-
- Dec 31, 2018
-
-
- Dec 30, 2018
-
-
Currently, weboob commands still return 0 even when an exception is raised. Let bcall_errors_handler decide the return code instead of always 0. A good return code is hard because of several things: * there might be multiple exceptions in a BCallErrors, so values returned by bcall_error_handler (single exception) cannot easily be combined * the base implemententation of bcall_errors_handler cannot be polluted with a lot of exception subclasses So, any non-MoreResultsAvailable will cause a non-zero return code. Should fix https://git.weboob.org/weboob/devel/issues/74.
-
"boobank history" lacks an account argument but boobank returned 0 as if there was no error. Related to https://git.weboob.org/weboob/devel/issues/74. TODO: return error codes for BCallErrors
-
-
- Dec 29, 2018
-
-
-
-
It was used by the old bash completion, but otherwise not very useful to end-users. Moreover, it was giving wrong results! For example, weboobcfg is not the actual callable application, it is weboob-config.
-
Since we already generate the man pages automatically, we can generate the bash completions too. It is much faster and does not risk making any network requests. fixes #194
-
An unfortunate commit. I am not aware of anyone still using a N900 or similar. The Hildon library is not maintained anymore. Blame Sephen Elop.
-
- Dec 21, 2018
-
-
simplejson has an internal way of formatting Decimal so it bypasses our formatter. Since weboob often deals with money, floats are not a good idea. Previousl: Decimal('1.1') => 1.1 with simplejson+WeboobEncoder Decimal('1.1') => '1.1' with json+WeboobEncoder Now both give '1.1'. Under simplejson: Using dump(cls=...) always initialize the Encoder class with the use_decimal=True argument (unless the argument is provided in the dump function, but that requires a lot of alteration in Weboob, and I would rather remove simplejson support altogether). So when present, we force it. Under json: There is no use_decimal, so we already go to the default() method of the Encoder.
-
-
-
-
-
- Dec 17, 2018
-
-
Handle all add new recipient timeout, for exemple: mobile app authentication request has timeout
-
-
Handle multiple authentication in order to add new recipient
-
to share it between boobank and boobill.
-
There were no indices for formatter table so I added a "#" column with 1, 2 , 3 (...) so it is easier to locate account numbers and use "investment 42" or "history 28" without copypasting the account ID. This only occurs when using commands interactively.
-
Unicode should be accepted too in python2, and result should be unicode-decoded. u'%C3%A9' should give u'\xe9' not u'\xc3\xa9' Also add tests.
-
When there are no <td>, TableCell.call_without_colspan returned empty list, but TableCell.call_with_colspan crashed because it couldn't count tds. Compatible behavior is to also return empty list.
-
It's not exactly a timeout but for now it seems sufficient for requests to retry. I don't know exactly in what circumstances this errors occurs in the wild, but it can tentatively be reproduced experimentally with a very long wait (minutes or hours) before doing the handshake.
-
If "," is the thousands separator, "12,345" should be accepted but not "123,45".
-