Matthieu Berthomé

I'm experimenting with limiting token disclosure risk by passing API calls through a passthrough proxy (similar to https://github.com/google/magic-github-proxy). This way I could put another token somewhere that would be allowed...

I could workaround using a more custom provider I think (like the httpreq), but I figured I could send the PR either way, some providers here have a customizable base_url.

I second this. As is, the repo's Dockerfile is not buildable (there is a undocumented `config` file/directory needed)

anecdotically, for other keyboard layouts, an alias would also be good. `qsdf` for me, on an AZERTY keyboard (damned French people /s)

Are you syncing-pushing the changes ? client.be_payees.remove(element) client.push()

Do you mean Combine Payees accessible in the "Manage Payees" in the web app ? If that's the case, if I understand how that feature works, the idea would be:...

Great ! Thanks. It looks like there are leftover commits from when you checked out that repo, made the changes 89d08f9 then merged from upstream (my repo, I guess). For...

This is a clever hack :+1:

OK, cannot reproduce, we have to see what happens for your situation: Next step would be digging in the JSON data that is received by pynYNAB before it's treated and...

Sorry, you need to add a logging.basicConfig() (doc [here](https://docs.python.org/2/library/logging.html#logging.basicConfig)) line to add basic streamhandler to the logging facility before the logging works. Add it anywhere in the script, before the...