[Python-bugs-list] [Bug #110834] urlparse and HTTP parameters (PR#205)

[noreply@sourceforge.net]

Bug #110834, was updated on 2000-Aug-01 14:13
Here is a current snapshot of the bug.

Project: Python
Category: Library
Status: Open
Resolution: Later
Bug Group: Feature Request
Priority: 3
Summary: urlparse and HTTP parameters (PR#205)

Details: Jitterbug-Id: 205
Submitted-By: mnot@akamai.com
Date: Tue, 15 Feb 2000 17:09:44 -0500 (EST)
Version: 1.5.2
OS: All


Python parses urls into the following data structure:
  (scheme, netloc, path, params, query, fragment)
and references RFC1808. 1808 has been updated by RFC2396, which allows
on each path segment, not just the last. This would imply a data structure
either like this:
  (scheme, netloc, path, query, fragment)
or this:
  (scheme, netloc, [(segment, parameters)...], query, fragment)

Rather than updating urlparse.py (and introducing incompatibility), it may be
nice to introduce a new class (say, uriparse.py) that implements 2396. If
there's enough interest, I may give it a go...


====================================================================
Audit trail:
Wed Feb 23 21:39:30 2000	guido	sent reply 1
Wed Feb 23 21:39:42 2000	guido	changed notes
Wed Feb 23 21:39:42 2000	guido	moved from incoming to request

Follow-Ups:

Date: 2000-Aug-01 14:13
By: none

Comment:
From: Guido van Rossum <bugs-py@python.org>
Subject: Re: urlparse and HTTP parameters (PR#205)
Date: Wed Feb 23 21:39:30 2000

Go for it!

--Guido van Rossum

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

Date: 2000-Aug-01 14:13
By: none

Comment:
Go for it!
-------------------------------------------------------

Date: 2000-Aug-16 19:02
By: fdrake

Comment:
An excellent idea; it can be incorporated in the existing urlparse module using new names.  This won't be done for Python 2.0 at any rate, however.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110834&group_id=5470