[Python-Dev] Polymorphic best practices [was: (Not) delaying the 3.2 release] (original) (raw)
Terry Reedy tjreedy at udel.edu
Fri Sep 17 05:45:12 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 ]
Based on the discussion so far, I think you should go ahead and implement the API agreed on by the mail sig both because is has been agreed on (and thinking about the wsgi discussion, that seems to be a major achievement) and because it seems sensible to me also, as far as I understand it. The proof of the API will be in the testing. As long as you think it covers all intended use cases, I am not sure that abstract discussion can go much further.
I do have a thought about space and duplication. For normal messages, it is not an issue. For megabyte (or in the future, gigabyte?) attachments, it is. So if possible, there should only be one extracted blob for both bytes and string versions of parsed messages. Or even make the extraction from the raw stream lazy, when specifically requested.
-- Terry Jan Reedy
- 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 ]