-
Notifications
You must be signed in to change notification settings - Fork 64
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
Regression in 1.1.0 #49
Comments
Martin- thanks for teasing out the root cause of the problem. I've been too casual with the release process, so I just cut it from main. I want to compare the pip version against my local server that I uploaded from and see why there's a difference. I'll definitely add a unit test, thank you very much for giving breadcrumbs on that. (feel free to PR some of it if you want) |
Apologies I think I was mistaken about the release process bug - the git blame showing me the commit was 5 years old was misleading given it was merged in March. I think this will do it #50 |
Gotcha, I need to sort out how that affects #21, I think. |
closes #50. A simple revert doesn't actually fix the regression, as the previous version would then fail the "hyphen in key" issue. This solves both. Thanks to @martinamps for finding and documenting this in #49.
Okay. I closed #50, which traded one bug for another. I also added unit tests for both- and in fact, you can see that the unit test for your problem isn't fixed until 1d01f46. Do you have an environment where you can test this before I release it as v1.1.1? I mean, something like this:
|
@tedder thanks for the quick turnaround, can confirm this works :) |
great! I just uploaded it to pypi. |
Authentication has begun failing for us with multiple query strings because the
1.1.0
release (which is not tagged in GitHub) has introduced this commit from 5 years ago which appears to be a regression. The 1.0.1 branch did not include itAny ideas how this happened / how it can be prevented moving forward?
Simple repro test:
EDIT: Ah I see though the commit is 5 years old, the merge just landed more recently.
The text was updated successfully, but these errors were encountered: