Message 334041 - Python tracker

Message334041

Author	martin.panter
Recipients	anh.le, dmi.baranov, madison.may, martin.panter, orsenthil
Date	2019-01-19.06:52:27
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1547880748.02.0.318455624207.issue18140@roundup.psfhosted.org>
In-reply-to

Content
Today I read RFC 3986, and I think the URLs in the bug reports are valid, and are already parsed correctly. The path is allowed to have a literal “at” symbol: path-abempty = ( "/" segment ) segment = pchar pchar = unreserved / pct-encoded / sub-delims / ":" / "@" The query and fragment are allowed to have “at” and question marks: query = ( pchar / "/" / "?" ) fragment = ( pchar / "/" / "?" ) So I think this could be closed because the parsing is working correctly.

Content

Today I read RFC 3986, and I think the URLs in the bug reports are valid, and are already parsed correctly. The path is allowed to have a literal “at” symbol:

path-abempty = *( "/" segment )
segment = *pchar
pchar = unreserved / pct-encoded / sub-delims / ":" / "@"

The query and fragment are allowed to have “at” and question marks:

query = *( pchar / "/" / "?" )
fragment = *( pchar / "/" / "?" )

So I think this could be closed because the parsing is working correctly.

History
Date	User	Action	Args
2019-01-19 06:52:30	martin.panter	set	recipients: + martin.panter, orsenthil, dmi.baranov, madison.may, anh.le
2019-01-19 06:52:28	martin.panter	set	messageid: <1547880748.02.0.318455624207.issue18140@roundup.psfhosted.org>
2019-01-19 06:52:28	martin.panter	link	issue18140 messages
2019-01-19 06:52:27	martin.panter	create