On Fri, Sep 26, 2014 at 9:58 PM, PJ Eby p...@telecommunity.com wrote:
On Thu, Sep 25, 2014 at 11:32 PM, Robert Collins
robe...@robertcollins.net wrote:
So I propose we drop the write callable, and include a queue based
implementation in the adapter for PEP- code.
If you're dropping
On 27 September 2014 08:21, Benoit Chesneau bchesn...@gmail.com wrote:
On Fri, Sep 26, 2014 at 5:32 AM, Robert Collins robe...@robertcollins.net
wrote:
...
So I propose we drop the write callable, and include a queue based
implementation in the adapter for PEP- code.
-Rob
What would
On Fri, Sep 26, 2014 at 5:02 PM, Robert Collins
robe...@robertcollins.net wrote:
But perhaps it would be nicer to say:
iterator of headers_dict_or_body_bytes
With the first item yielded having to be headers (or error thrown),and
the last item yielded may be a dict to emit trailers.
So:
def
On 27 September 2014 10:31, PJ Eby p...@telecommunity.com wrote:
On Fri, Sep 26, 2014 at 5:02 PM, Robert Collins
robe...@robertcollins.net wrote:
But perhaps it would be nicer to say:
iterator of headers_dict_or_body_bytes
With the first item yielded having to be headers (or error thrown),and
On Fri, Sep 26, 2014 at 7:41 PM, Robert Collins
robe...@robertcollins.net wrote:
One thing we could do with the status code in the headers dict is to
default to 200 - the vastly common case (in the same way that throwing
an error generates a 500). Then status wouldn't be required at all for
