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 r.david.murray
Recipients Claudiu.Popa, Joshua.Johnston, ezio.melotti, orsenthil, r.david.murray
Date 2013-09-30.14:28:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380551336.5.0.789489179533.issue18857@psf.upfronthosting.co.za>
In-reply-to
Content
No, Senthil is correct.

My original liking for this idea came from my mistaken impression that a value without an '=' was different from a value with an '='.  But clearly the practice in the industry (the de facto standard) is that they are the same, and indicate that the value of the parameter is the empty string.

So, urls do *not* have any way of representing a null value (as differentiated from an empty string).  All url values are strings.  This means that the correct value to use for a python value is always its string representation, which in the case of None is "None", just as the correct representation of a Python boolean value is "True" or "False" (since http also does not have any specifically boolean type, only string values).
History
Date User Action Args
2013-09-30 14:28:56r.david.murraysetrecipients: + r.david.murray, orsenthil, ezio.melotti, Claudiu.Popa, Joshua.Johnston
2013-09-30 14:28:56r.david.murraysetmessageid: <1380551336.5.0.789489179533.issue18857@psf.upfronthosting.co.za>
2013-09-30 14:28:56r.david.murraylinkissue18857 messages
2013-09-30 14:28:56r.david.murraycreate