Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Sure. And if HTTP was all about browsers keying off pages, that would
> > be fine with me. But it's not. HTTP is used in lots of places where
> > there are no browsers;
>
> I'm sorry, I don't follow you. The fact that something
Bill Janssen parc.com> writes:
>
> Sure. And if HTTP was all about browsers keying off pages, that would
> be fine with me. But it's not. HTTP is used in lots of places where
> there are no browsers;
I'm sorry, I don't follow you. The fact that something else than a browser makes
the request
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Sure. But nowhere does a spec say that this page charset should be used
> > in sending the values of a FORM using application/x-www-form-urlencoded
> > in a new HTTP request. It's just a convention some browsers use.
>
> Let's ca
Bill Janssen parc.com> writes:
>
> Sure. But nowhere does a spec say that this page charset should be used
> in sending the values of a FORM using application/x-www-form-urlencoded
> in a new HTTP request. It's just a convention some browsers use.
Let's call it a de facto standard then. A beha
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > ``The content type "application/x-www-form-urlencoded" is inefficient
> > for sending large quantities of binary data or text containing non-ASCII
> > characters.
>
> The fact that it's "inefficient" (i.e. takes more bytes than an
Bill Janssen parc.com> writes:
>
> ``The content type "application/x-www-form-urlencoded" is inefficient
> for sending large quantities of binary data or text containing non-ASCII
> characters.
The fact that it's "inefficient" (i.e. takes more bytes than an optimal encoding
scheme would) doesn't
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > This whole discussion seems a bit "rare and obscure" to me. I've built
> > URLs for years without this method, and never felt the lack. What bugs me
> > is the lack of a way to build multipart-formdata payloads, the only standard
Bill Janssen parc.com> writes:
>
> This whole discussion seems a bit "rare and obscure" to me. I've built
> URLs for years without this method, and never felt the lack. What bugs me
> is the lack of a way to build multipart-formdata payloads, the only standard
> way to send non-Latin1 strings a
Antoine Pitrou wrote:
> Bill Janssen parc.com> writes:
> >
> > Or even better, stop trying to use a mapping, and just make the "params"
> > value a list of (name, value) pairs.
>
> You can even accept both a list of (name, value) pairs /and/ some **kwargs,
> like
> the dict constructor does.
Bill Janssen parc.com> writes:
>
> Or even better, stop trying to use a mapping, and just make the "params"
> value a list of (name, value) pairs.
You can even accept both a list of (name, value) pairs /and/ some **kwargs, like
the dict constructor does. It would be a pity to drop the user-frien
Mart Sõmermaa gmail.com> writes:
>
> On Mon, Apr 13, 2009 at 12:56 AM, Antoine Pitrou pitrou.net>
wrote:
> Mart Sõmermaa gmail.com> writes:
> >
> > Proposal: add add_query_params() for appending query parameters to an URL
to
> urllib.parse and urlparse.
> Is there anything to /remove/ a query p
Mart Sõmermaa gmail.com> writes:
>
> Proposal: add add_query_params() for appending query parameters to an URL to
urllib.parse and urlparse.
Is there anything to /remove/ a query parameter?
___
Python-Dev mailing list
Python-Dev@python.org
http://mai
12 matches
Mail list logo
