Skip to main content

Upgrading Business::PayPal::API

·369 words·2 mins·
❤️ It's great to see you here! I'm currently available on evenings and weekends for consulting and freelance work. Let's chat about how I can help you achieve your goals.

I got co-maint on Business::PayPal::API about 3 years ago in order to patch one line that was throwing a warning. The previous release had been 2 years prior to that. So it’s fair to say that this module has not lately been on a rapid release cycle. It’s still in use, though, and lately there has been some activity on related to it. So, I finally took an evening to sit down and try to cut a new release.

I got the bulk of the work done last night. I had been partially through a conversion to Dist::Zilla. I was able to finish that yesterday. This evening I finally got my head around how to get the tests running. It’s a non-trivial process.

There are a huge number of commits that I merged in for this latest release. All of the tests are passing except for one related to searching for “mass pay” payments. It’s in t/advanced/TransactionSearch.t. To be honest, that test failure doesn’t concern me too much. I don’t have a pile of time to invest in this at this point and my main concern is not breaking anything that involves sending and receiving payments. I’m also not sure when this test was actually last passing since most of the tests don’t actually run when the module is installed. That all predates me.

I’m pragmatic enough to say that I can either try to fix this test at some point over the next 3 years or cut a new release now and get this thing out the door. I really do want to get this out into the wild. If it turns out there is an actual issue with the mass pay search, I hope someone will pitch in with a fix.

If you rely on this module, please consider giving the TRIAL release a test run. Pull requests are happily accepted.

If I’ve heard no complaints by Oct 15, 2015 I will make a proper release including these latest changes.

Edit: I just checked the current latest release and TransactionSearch.t fails there as well, so this test failure is at least 3 years old, which means it’s not a blocker to putting out a new release.


Stop Writing Your Own Commify Functions
·802 words·4 mins
On the status of HTTP::BrowserDetect
·837 words·4 mins
browser detection HTTP perl
How I Spent my 2015 Hackathon
·650 words·4 mins
metacpan perl Programming