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 orsenthil
Recipients ezio.melotti, mastahyeti, orsenthil, r.david.murray
Date 2012-08-30.18:38:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPOVWORZ8rfvJxrk4yLqVg2TYK-A2Oq0aMLq=11nPLVcMsJcXg@mail.gmail.com>
In-reply-to <1346350665.33.0.731435453404.issue15824@psf.upfronthosting.co.za>
Content
On Thu, Aug 30, 2012 at 11:17 AM, mastahyeti <report@bugs.python.org> wrote:
>
> When parsing a url with urlparse.urlparse, the return type is non-mutable (named tuple). This is really inconvenient, because one of the most common (imop) use cases for urlparse is to parse a url, make an adjustment or change and then unparse it. Currently, something like this is required:

Not actually, using the namedtuple is a convenience and working
through way may help you to be generate your target url in a more
meaningful way. Also remember that we moved to namedtuple after
understanding that it is more meaningful to use that for parsed
result.  So, my vote for this proposal is -1. And if you need discuss
the strategies of how to use it, then you can ask over at python-help
or related lists.
History
Date User Action Args
2012-08-30 18:38:27orsenthilsetrecipients: + orsenthil, ezio.melotti, r.david.murray, mastahyeti
2012-08-30 18:38:23orsenthillinkissue15824 messages
2012-08-30 18:38:23orsenthilcreate