[Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices) (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue Sep 21 17:26:51 CEST 2010
- Previous message: [Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices)
- Next message: [Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 22 Sep 2010 00:10:01 +0900 "Stephen J. Turnbull" <stephen at xemacs.org> wrote:
But I don't know whether the web apps programmers will be satisfied with such a minimal API.
Web app programmers will generally go through a framework, which handles encoding/decoding for them (already so in 2.x).
And there are a lot of APIs that probably should be considered candidates for polymorphic versions (regexp matching and searching, for example).
As a matter of fact, the re module APIs are already polymorphic, all the while disallowing any mixing of bytes and unicode.
Regards
Antoine.
- Previous message: [Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices)
- Next message: [Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]