-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
PEP 508: fix mistakes in the complete parsley grammar #3069
Comments
I found another error this line: |
According to setction 2 of rfc3986, those are really mistakes and should be fixed |
I created #3070 to address this issue |
Accepted PEPs are generally considered to be historical documents. Where is the living document that carries this information? |
I only found two related peps on this topic: pep440 and pep508. The reference page on pypa https://pip.pypa.io/en/stable/reference/requirement-specifiers refers to pep508 |
Ah! That page is the living document that I'm referring to, and since it cites PEP 508 as the specification, that means that this does need to be updated. Next step: Need a subject-matter expert to confirm the correctness of the change. |
I have another question on
According to the regex implementation from https://github.com/pypa/packaging/blob/main/src/packaging/specifiers.py
When However, the parsley grammar only allows |
Seeing as @pradyunsg has worked on this general code most recently and is active here, he might be someone else to ask for an expert opinion here (or know whom else to). |
The complete parsley grammer in pep 508
My question is why
pct_encoded
only contains one hexdig? Shouldn't it bepct_encoded = '%' hexdig{2}
?The text was updated successfully, but these errors were encountered: