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 liori
Recipients liori, orsenthil
Date 2011-04-18.12:55:49
SpamBayes Score 0.0002312749
Marked as misclassified No
Message-id <1303131350.65.0.0180303514479.issue11862@psf.upfronthosting.co.za>
In-reply-to
Content
If __str__ is meant to be a user-understandable way of expressing an URL, the best way to do that is to show it the same way user sees it in usually. This is now done by .geturl() call.

This way I wouldn't have to remember to serialize it in cases where I want to display an URL to user:

    url = urlparse.urlparse(sys.args[1])
    ...
    print "Downloading {1}".format(url)

would mean: "show me that URL".

And if you would like to display its internal representation as a record of scheme/host/path/..., you always have __repr__. Currently both __str__ and __repr__ return `ParsedResult(scheme="http", netloc='example.com', ...)`
History
Date User Action Args
2011-04-18 12:55:50liorisetrecipients: + liori, orsenthil
2011-04-18 12:55:50liorisetmessageid: <1303131350.65.0.0180303514479.issue11862@psf.upfronthosting.co.za>
2011-04-18 12:55:50liorilinkissue11862 messages
2011-04-18 12:55:49lioricreate