You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Query parameters not properly URL-encoded (pandas data pipeline) #9
I think the root cause here might be related to the client.request method, which is using the params dictionary directly without URL-encoding the query parameters. IIRC, the requests library (which is likely being used under the hood) expects the query parameters to be passed as a dict with the keys being the parameter names and the values being the parameter values. However, it does not automatically URL-encode the values. You might want to try using the urllib.parse.urlencode function to encode the params dictionary before passing it to the client.request method.
We’re currently experimenting with a slightly different approach using Pandas for handling responses, so this area is still evolving on our side.
Any suggestions or experiments around improving the decoding/handling flow are more than welcome — feel free to share ideas or even open follow-up PRs.
Activity
IlyasFardaouix commentedon Mar 19, 2026
I think the root cause here might be related to the
client.requestmethod, which is using theparamsdictionary directly without URL-encoding the query parameters. IIRC, therequestslibrary (which is likely being used under the hood) expects the query parameters to be passed as adictwith the keys being the parameter names and the values being the parameter values. However, it does not automatically URL-encode the values. You might want to try using theurllib.parse.urlencodefunction to encode theparamsdictionary before passing it to theclient.requestmethod.francescobianco commentedon Mar 24, 2026
Good point, thanks @IlyasFardaouix for looking into it.
We’re currently experimenting with a slightly different approach using Pandas for handling responses, so this area is still evolving on our side.
Any suggestions or experiments around improving the decoding/handling flow are more than welcome — feel free to share ideas or even open follow-up PRs.
Deadpool2000 commentedon Apr 5, 2026
Hey @francescobianco ,
I just raised a PR #16 fixing this bug.
Check, Verify and Let me know!
Merge pull request #16 from Deadpool2000/fix-issue-9
francescobianco commentedon Apr 14, 2026
Great work @Deadpool2000, thanks for the PR! 🙌
Even though this seems to fix the issue, we’ll keep it open for now so we can run some internal tests in our environment over the next few months.
Once everything is fully verified and confirmed as stable, we’ll proceed with closing the issue.
Thanks again for your collaboration!
Deadpool2000 commentedon Apr 15, 2026
@francescobianco Thanks 😊
francescobianco commentedon May 12, 2026
Thanks @Deadpool2000 now you are mentioned here https://github.com/openapi/openapi-python-sdk/releases/tag/0.3.0
Deadpool2000 commentedon May 12, 2026
@francescobianco thanks for the mention, happy to see it all make it into the release 😊