Pyroostermoney

Latest version: v2023.12.1

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

Scan your dependencies

Page 2 of 4

0.3.5

- New pot related actions in this release (add 10 , remove 11 and transfer money 12 )
- Money transfers from/to custom pots are not currently supported, although the code exists there is an outstanding issue (see 12)
- Fixes an issue where pot targets display a raw value rather than the real value (16)
- A number of under the hood changes to accommodate the above features and introductions of a couple of new enums.

**Full Changelog**: https://github.com/pantherale0/pyroostermoney/compare/0.3.4...0.3.5

0.3.4

- `ChildAccount` now exposes allowance settings

**Full Changelog**: https://github.com/pantherale0/pyroostermoney/compare/0.3.3...0.3.4

0.3.3

- Add action to freeze or unfreeze a card
- Jobs now parse the day of week
- Refactor some enums and move them into a central place

**Full Changelog**: https://github.com/pantherale0/pyroostermoney/compare/0.3.2...0.3.3

0.3.2

- Fix issues returning family account balance https://github.com/pantherale0/ha-roostermoney/issues/4

0.3.1

Breaking

Removal of the built-in updater due to unexpected issues updating data, your application should now call `RoosterMoney.update()` at regular intervals to keep the data up to date.

0.3.0

MAJOR RELEASE

This release changes how a number of internal objects are created and the main `RoosterMoney` session is initialized.

To login, you should initialize your var like so:


from pyroostermoney import RoosterMoney

session = RoosterMoney.create(username="username here", password="password here")

session.children


Details

- Support for the `use_updater` parameter has now been removed as this will be used for all sessions going forward
- The default update interval is now set to 30s, you can use a lower number at your own risk although a future version will set this to a minimum of 15s
- The updater for all `ChildAccount` objects has been moved back to the main class, this will improve performance for accounts with multiple children.
- The `remove_card_information` parameter will be changed in a future release to `exclude_card_pin` - basic card info will return by default to allow for future extended functions with a card (such as disabling settings, changing limits and more)
- `exclude_card_pin` is set to `True` by default for security measures.
- Future versions will remove the cached username and password, for these a new exception will be thrown where your application will need to catch and sign back in using its own cache. The internal cache will contain session tokens, refresh tokens and a security code generated by reversing your password, after renaming the parameter `remove_card_information` this "security code" will only be stored if `exclude_card_pin` is set to `False`
- Transaction information now separates declines and stores declined reasons (along with updating the event system to support this)
- If a card reaches its contactless limit, a new event will fire with the child user_id, alongside a separate transaction event firing too
- Event system now contains a new source `INTERNAL`
- Event system now contains three new types: `AUTH` `EVENT_SUBSCRIBE` and `EVENT_UNSUBSCRIBE`
- Jobs are now sorted by date and time order, latest first.

**Full Changelog**: https://github.com/pantherale0/pyroostermoney/compare/0.2.5...0.3.0

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.