[Python-bugs-list] [ python-Feature Requests-618024 ] urlparse fails on imap://

[noreply@sourceforge.net]

Feature Requests item #618024, was opened at 2002-10-03 21:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=618024&group_id=5470

Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Asle Pedersen (apederse)
Assigned to: Piers Lauder (pierslauder)
Summary: urlparse fails on imap://

Initial Comment:
urlparse does not parse imap:// urls (RFC 2192). I am not 
all sure but this seem to be an appropriate patch:

	urlparse.uses_relative.append('imap')
	urlparse.uses_netloc.append('imap')
	urlparse.non_hierarchical.append('imap')
	urlparse.uses_params.append('imap')
	urlparse.uses_query.append('imap')

----------------------------------------------------------------------

>Comment By: Piers Lauder (pierslauder)
Date: 2002-11-05 21:44

Message:
Logged In: YES 
user_id=196212

I've never tried to use the imap URL form, and I'm unaware of
which IETF RFC documents its allowable syntax. Seems ok,
but why not  "urlparse.uses_fragment.append('imap')" as well?

(Searching google...) This looks like the document that
defines it:
http://ftp.ics.uci.edu/pub/ietf/uri/rfc2192.txt
"IMAP URL Scheme"

No mention of '#', so I guess no fragments :-)

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2002-11-05 12:30

Message:
Logged In: YES 
user_id=33168

Piers, is this right?  If so, I can make the change.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355470&aid=618024&group_id=5470