Pymyob

Latest version: v1.2.24

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

Scan your dependencies

Page 6 of 10

1.1.4

Added endpoints for `GeneralLedger/Category`.

1.1.3

24 Added endpoints for `Purchase/Bill/Miscellaneous` (thanks callumanderson-alliance!).

1.1.2

23 Added endpoints for `Banking/SpendMoneyTxn` and `Banking/ReceiveMoneyTxn` (thanks mattjegan!).

1.1.1

21 Added support for requests-oauthlib 3.0 (thanks mattjegan !)

1.1.0

20 Added timeout support. Defaults to no timeout as was the behaviour for prior versions.

1.0

**This release has breaking changes!**
Please read below, then step through the README to update your code to conform.

15 Cleaned up some final niggles with the way company file credentials are stored, and how they are passed around:
- Added support for storing multiple sets of company file credentials.
- Removed need to pass `company_id` into every single method, by promoting `CompanyFile` from a json blob to a class.
- base64 conversion of the userpass is now done internally, rather than asking the user to do it. Just call the new `cred.authenticate_companyfile(company_id, username, password)` method.

**Important note**: Due to the changes to how company file credentials are stored, if you're upgrading from a previous version, you'll either need to tweak your stored `state` json blob, or ask your customers to reconnect their MYOB integrations from scratch. If you want to do the former, the steps to migrating your stored `state` json blob are as follows:

state = <persistently_stored_state_in_your_db>
userpass = state['userpass']
del state['userpass']
state['companyfile_credentials'] = {
'<company_uid>': userpass,
}
Now push state back into your db where you had it before.

Trying to spin up a `PartnerCredentials` instance with `PartnerCredentials(**old_state)` will fail loudly, as `userpass` will be flagged as an unwanted argument.


Enjoy!

Page 6 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.