➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients eric.araujo, ivan_herman, orsenthil
Date 2012-02-25.05:32:41
SpamBayes Score 0.0016112278
Marked as misclassified No
Message-id <1330147962.01.0.694827598211.issue14072@psf.upfronthosting.co.za>
In-reply-to
Content 
urlparse doesn’t actually implement generic parsing rules according to the most recent RFCs; it has hard-coded registries of supported schemes.  tel is not currently supported.  That said, it’s strange that the parsing differs in your two examples.
History
Date User Action Args
2012-02-25 05:32:42eric.araujosetrecipients: + eric.araujo, orsenthil, ivan_herman
2012-02-25 05:32:42eric.araujosetmessageid: <1330147962.01.0.694827598211.issue14072@psf.upfronthosting.co.za>
2012-02-25 05:32:41eric.araujolinkissue14072 messages
2012-02-25 05:32:41eric.araujocreate