➜
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.
Created on 2002-10-03 11:20 by apederse, last changed 2022-04-10 16:05 by admin. This issue is now closed.
| Messages (5) | |||
|---|---|---|---|
| msg53649 - (view) | Author: Asle Pedersen (apederse) | Date: 2002-10-03 11:20 | |
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')
|
|||
| msg53650 - (view) | Author: Neal Norwitz (nnorwitz) *  |
Date: 2002-11-05 01:30 | |
Logged In: YES user_id=33168 Piers, is this right? If so, I can make the change. |
|||
| msg53651 - (view) | Author: Piers Lauder (pierslauder) *  |
Date: 2002-11-05 10:44 | |
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 :-)
|
|||
| msg53652 - (view) | Author: Piers Lauder (pierslauder) * |
Date: 2002-11-22 06:05 | |
Logged In: YES user_id=196212 Just to reiterate - this change is fine by me, so please make the suggested changes to the urlparse module's classification schemes. |
|||
| msg53653 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2003-01-06 06:59 | |
Logged In: YES user_id=33168 Checked in as: * Lib/urlparse.py 1.36 * Lib/test/test_urlparse.py 1.10 * Misc/NEWS 1.603 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:05:43 | admin | set | github: 37255 |
| 2002-10-03 11:20:54 | apederse | create | |