-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARBSubscriptionType issue with Python 3.8 #145
Comments
I've encoutered the same problem. I've created an issue directly on PyXB and also found an temporary solution: pabigot/pyxb#123 |
Reproducable in 3.9. I've tried many things, including @AntonDeMeester's solution but nothing is working. Any help would be greatly appreciated as this is holding up a production release. |
I'm pretty sure I found a solution but for the life of me I actually can't find what it was. Been so long ago now, I can't even remember what project I ran into this on. |
The solution above by @AntonDeMeester did end up working with 3.9. Just had to set startDate = customdate(datetime object) and it ended up posting the ARB correctly. This is a clear issue with pyxb and Authorize.net, but I don't see any real resolution coming for this. Shame, really. Thanks for everyone's help. |
Facing the same issue with Python 3.10, the custom date is also not working. Any recommendations will be helpful. Thank you. |
@anmolmonga-kiwi Are you sure? I use this solution on 3.10. |
TCS-Dev Dhanashree- If I try to execute the file, I am not able to reproduce the error because we have replaced the offending serialization library with a newer one, which will hopefully not cause more issues like this. This issue has been fixed in v1.1.5. |
When updating from Python 3.7 => 3.8, I've started to receive the following complaint from Authorize.net / PyXB:
It seems to be related to the
paymentScheduleType.startDate
property. I've tried setting it to a pyxb date, a python datetime.date, and a string. None of these work. And if I roll back to Python 3.7, the issue goes away. Any thoughts or suggestions? Is this a mistake on my end?The text was updated successfully, but these errors were encountered: