Skip to content
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

Correct comparison with urlparse #183

Open
merwok opened this issue Feb 9, 2024 · 0 comments
Open

Correct comparison with urlparse #183

merwok opened this issue Feb 9, 2024 · 0 comments

Comments

@merwok
Copy link

merwok commented Feb 9, 2024

Hello!

Just a thought from reading your docs: it’s not quite accurate to say that urlparse doesn‘t have a URL type, given that it does return a named tuple, with instances being immutable and having a _replace method for derivation.

It’s not a full modern class with nice methods, and it doesn’t change the fact that there is no validation in urllib.parse, but it’s better than strings or dicts!

Ref: https://docs.python.org/3/library/urllib.parse.html#structured-parse-results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant