[Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release] (original) (raw)
Steven D'Aprano steve at pearwood.info
Fri Sep 17 03:55:35 CEST 2010
- Previous message: [Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release]
- Next message: [Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 17 Sep 2010 11:34:26 am R. David Murray wrote:
Perhaps another difference is that in my mind *as an application developer*, the "real" email message consists of unicode headers and message bodies, with attachments that are sometimes binary, and that the wire-format is this formalized encoding we have to use to be able to send it from place to place. In that mental model it seems to make perfect sense to have a StringMessage that I have encode to transmit, and a BytesMessage that I receive and have to decode to work with.
+1
-- Steven D'Aprano
- Previous message: [Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release]
- Next message: [Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]