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
[TODO: remove in v15] Duplicate HTTP Auth Basic and HTTP Auth Digest tools have to be merged #1688
Comments
@jaraco we've forgotten to remove this thing. Maybe we need some label for deprecations to check before doing major releases? |
The only thing I worry about is that new tool runs on |
At YouGov, we have some applications that still use the deprecated handlers. I'm not sure we've given enough time for deprecation warnings to be noticed and addressed. Also, it's not that we had forgotten to remove it; we just hadn't yet removed it. I don't think there's any prescribed schedule for removing deprecated functionality. |
Well, I removed those in master. |
While working on #1680 I realized that there's functional duplication in tools we provide by default.
There's
auth_basic
,auth_digest
and alsobasic_auth
,digest_auth
.They also have duplicate tests spread across 3-5 test modules, which has to be handled as well.
#913 (0704e6c) and as mentioned in #914:
Do you want to request a feature or report a bug?
Deprecated tool removal.
What is the current behavior?
There's ambiguity making end-users confused about which tool to use.
If the current behavior is a bug, please provide the steps to reproduce and if possible a screenshots and logs of the problem.
See src
What is the expected behavior?
Just one well-documented and well-tested implementation for each of Basic/Digest HTTP Auth methods.
What is the motivation / use case for changing the behavior?
There should be one-- and preferably only one --obvious way to do it. (Zen of Python)
Please tell us about your environment:
—
The text was updated successfully, but these errors were encountered: