[issue8339] urlunparse(urlparse('x://')) now returns 'x:' instead of 'x://'

New submission from Michael Glassford : An unfortunate side-effect of this change: http://svn.python.org/view/python/branches/release26-maint/Lib/urlparse.py?r1=66717&r2=78235 which was made to fix this issue: http://bugs.python.org/issue7904 is that urlparse.urlunparse(urlparse.urlp

[issue8339] urlunparse(urlparse('x://')) now returns 'x:' instead of 'x://'

Michael Glassford added the comment: It caused a minor issue with the Schemes extension for Mercurial: the output changed, which caused a unit test to fail. I'm pretty sure I have a Mercurial patch to fix that issue, however. -- ___ Python tr

[issue8339] urlunparse(urlparse('x://')) now returns 'x:' instead of 'x://'

Michael Glassford added the comment: > In those cases, I would assume that 'x://y', x:/y','x:/','/' > as valid URLS, but not the two examples you mentioned. Only 2 comments about this: 1) Although the urlparse documentation does mention the relevant R