>on at least some occasions the Python client gets non-standard results, while curl and (Guido, forgive me) PHP do fine
Ok, young one, here's the thing. If you see a problem like this then file a bug. Ideally write a test case. And if you're an overachiever, dig into the code and fix it. Any bug in an http client that reposts data is incredibly serious, and needs to be fixed.
The other value in doing this is that you don't spread Fear, Uncertainty, and Doubt - or FUD as it is often referred to. FUD is usually ascribed to big companies trying to discourage using a competitors product, but it can also be spread by the ignorant or misinformed inadvertantly. No offense, but I think that's the case in this case, because Python is not a niche language, it's used (and it's http libraries are used) by a lot of people, and the error mode you describe is very, very serious.
I did report this to the API maintainers, who couldn't make heads or tails of it. I didn't file a Python bug because I honestly don't think Python is the problem.
But you are right, it is more responsible to pursue this until fixed rather than raise warnings.
FYI, the `email` field in your profile is not publicly visible. If you want other people to be able to email you, you need to put it in your `about` text.
+1. Probably curl also had bugs before (and still does). These get fixed over time, but that doesn't mean improving the interaction isn't worthwhile in the first place.
This was a warning of a hazard to navigation, when a more diligent effort to remove the hazard is called for.