On 9/18/2010 2:29 AM, python-dev-request at python.org wrote:
> Polymorphic best practices [was: (Not) delaying the 3.2 release]
If you're hung up on this, try writing the user-level documentation
first. Your target audience is a working-level Web programmer, not
someone who knows six programming languages and has a CS degree.
If the explanation is too complex, so is the design.
Coding in this area is quite hard to do right. There are
issues with character set, HTML encoding, URL encoding, and
internationalized domain names. It's often done wrong;
I recently found a Google service which botched it.
Python libraries should strive to deliver textual data to the programmer
in clean Unicode. If someone needs the underlying wire representation
it should be available, but not the default.
John Nagle
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4