Bill Janssen wrote: > Alan Kennedy <a...@xhaus.com> wrote: > > [Bill] > > > I think the controlling reference here is RFC 3875. > > > > I think the controlling references are RFC 2616, RFC 2396 > > and RFC 3987. > > I see what you're saying, but it's darn near impossible, as a practical > matter, to get any guidance on encoding matters from those. > > The question is where those names come from, and they come from CGI, > and that is (practically speaking) defined these days by RFC 3875, > as much as anything.
If so, then PEP 333 really should be updated to point at a version of the CGI "spec" that doesn't reference e.g. RFC 1808 for URI's. As it is, one could easily come to the conclusion that, for example, path parameters like /path;a=3 aren't supported (because the CGI draft that PEP 333 mentions disallows them). I'd be much happier referring to 3875, and even happier diverging from strict compliance to what was always a shaky spec. Robert Brewer fuman...@aminus.org _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
