Subscription.find('') raises UnexpectedError about braintree_python HOT 6 CLOSED

foresto,

Thanks for submitting this issue. It is indeed a problem with the client library. We have queued up a task to fix this and it should be included in the next release.

from braintree_python.

@foresto,

We've recently released a new version of our Python Client Library that has included a fix for this behavior. Instead of returning an UnexpectedError we'll now return a NotFoundError. We recommend you test for a blank id before calling any find method or catch this error.

Please let me know if you have any questions,

Cory
Braintree Developer

from braintree_python.

Thank you. Does the fix cover Customer.find() as well? One of your staff suggested Customer.find() with a nonexistent id to test the connection to the braintree server, so it looks like we'll be using this after all.

from braintree_python.

Yep, any find method now ensures that id is set before attempting to communicate with Braintree.

from braintree_python.

Oh? In that case, you ought to add this to the release notes. As I said, one of your staff recommended using find() with a nonexistent id to test the connection to the server. If an id of '' no longer attempts to contact the server, you have just broken this test.

from braintree_python.

Sorry for the confusion! We recommend using a non-existent payment method token, not an empty string. If you use an empty string, we'll respond with NotFoundError without contacting our Gateway.

from braintree_python.