When try to reverse a transaction or a particular TransactionID, connection to the openapi portal timeout and raises the Mpesa Connection Error

Here is the sample of the error message;

    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='openapi.m-pesa.com', port=433): Max retries exceeded with url: /sandbox/ipg/v2/vodacomTZN/reversal/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f51f410f2e0>: Failed to establish a new connection: [Errno 111] Connection refused'))

This is just a suggestion, I used to run tests against the python version I was using on my machine before pushing to GitHuB, using this approach sometimes I found my self breaking my packages on other python versions unknowingly by using some features which are not compatible with some versions of python usually older versions because on my machine I was usually using the latest version. So to avoid this I started using tox and CI to tests my packages against all versions of python which I support before merging changes to master branch this way I would know whether I’ve broken something or not.

So my suggestion here is to add a way to run tests against all versions of python which you want to support so that u don’t break things on other versions unknowingly, don’t just assume whatever runs on python version on your machine will run on other versions too.

Thank you for the great library, I really appreciate the work you are doing.
The setup.py shows that the package has only two dependencies https://github.com/Kalebu/pypesa/blob/d2526183b09de997307b200530af4baab749b992/setup.py#L34-L39 But in requirements.txt there’re way more dependencies, is there any reason for that.

Greetings @Kalebu , so this just a suggestion on the package structure improvement. Suggestion list goes as follows;

• Use __init__.py to only Import key classes | methods from modules directly into the package namespace. i.e the folder structure could then be;

pypesa/
__init__.py
mpesa.py
mpesa_execptions.py
service_urls.py

• __init__.py could also include other important parameters like, version, author, release date, doc-string with a decent sample usage etc etc.
• Add a tests folder with the following structure;

tests/
__init__.py
test_pypesa.py

Note, tests/__init__.py can/should be left empty.

• Any other structural improvements that i haven't listed/noticed yet.

So to sum up, i think i can working on this if you think it might be a good idea. Also, i think there other code related improvements suggestion(mostly on the OOD), that i will definitely create their own separate issues.

@Kalebu Hello again. So i think at this point it would be advantageous to add Actions to the project for the ease of workflows automation. Current all (if not most) of the workflows a manual, of which its a perfect disasters recipe along the way.