Closed pallinger closed 1 month ago
Could someone review this?
Update: I left AUSSDA, so my funding for pyDataverse development has stopped.
I want to get some basic funding to implement the most urgent updates (PRs, Bug fixes, maintenance work). If you can support this, please reach out to me. (www.stefankasberger.at). If you have feature requests, the same.
Another option would be, that someone else helps with the development and / or maintenance. For this, also get in touch with me (or comment here).
Could someone review this?
Sorry for the delay! Thanks for converting this into a PR 👍 Reviewing now!
@pallinger can you sync your branch to the latest commit so it isn't out-of-date?
@pallinger thanks for syncing! I'll test it and check with @skasberger about the two checks that need to be run.
Could this be related?
@pdurbin yes this PR will resolve the error. Had the same issue a while back and adding the content-type
fixed it. Shall we merge this PR then? The changes shouldn't break anything.
@JR-1991 I haven't tested it but if you're happy, I'm happy! 😜
Kudos, SonarCloud Quality Gate passed!
@pallinger good news! As @JR-1991 says in this comment, the switch to httpx
fixed this: https://github.com/gdcc/pyDataverse/issues/143#issuecomment-2104513723
I'll go ahead and close this pull request.
By the way, if you haven't heard, we have regular pyDataverse meetings now. You're welcome to join! Please see https://py.gdcc.io . We're also on Zulip: https://dataverse.zulipchat.com/#narrow/stream/377090-python
fix newer dataverse compatibility by adding content-type=application/json header
Changes:
based on https://github.com/JR-1991/pyDataverse/commit/0fcfcd3fbc6bf1aec869899f715a51dca25e91be
Closes #143