No wheels for releases newer than 0.13

[bartbroere]

Steps to reproduce:

Install the bunq_sdk using micropip in Pyodide for example:

import micropip

await micropip.install('bunq_sdk')

or if you want only binary releases, you could reproduce this with "normal" pip as well:

python3 -m pip install --only-binary bunq_sdk bunq_sdk

What should happen:

The newest version should be installed. In my opinion ideally there should be both a binary and source release on PyPI for each version.

What happens:

A very old version (0.13) gets installed, since that was the last release to include a pure Python wheel.

To fix this

I'm not sure what process uploads the releases to PyPI, but I think it could be worthwhile to build and publish the wheel version as well as the source release, by doing something like this:

python3 setup.py bdist_wheel
python3 -m twine upload dist/*

Extra info:

Relates to this PR: pyodide/pyodide#3801, because I first suspected simplejson caused this. Since I'm (not by choice) installing an old version of the bunq_sdk I got a very old version of simplejson.

This is a useful resource about wheels and source releases: https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#wheels

[two-trick-pony-NL]

👋 Hey @bartbroere

I work at bunq and am currently reviewing the bunq API docs, open issues and SDK’s and came across your issue. I know it’s been open for a while, and I’d love to understand how it’s impacting you. Beyond the obvious -fixing this issue-, what else could we do to improve your experience with our API?

If you want to share your thoughts on how we can improve on our public API:

📅 I'd love to schedule a 15 minute interview to understand your needs through: Calendly
💬 Or if you don't have time for a call, you can give us some general feedback through this form

Your feedback will go straight to our product team! 🚀

[two-trick-pony-NL]

Hi! We're closing this issue as it's tied to an older version of our SDKs, and we've since completely revamped them as part of bunq Update 28.

This is a fresh start—we've tested the new SDKs extensively, and we’ll be putting them to the test again during our upcoming hackathon this Friday, where we’ll fix idiosyncrasies on the spot. (You’re welcome to join us!)

If this issue (or a new one) shows up with the updated SDKs, feel free to reopen or file a new report—we're happy to jump on it.