> On 7 Jan 2017, at 02:18, Tristan Seligmann wrote:
>
> On Sat, 7 Jan 2017 at 03:23 Glyph Lefkowitz wrote:
>
> Maybe we should support unicode for the body as well. We can set the charset
> in the mime-type and everything so that it will be properly intelligible by
> the server, which doesn
thanks for the quick replys guys, you were right. a .encode('utf-8')
helps.
actually the json.dumps part in the code is wrong.
it has to be:
somepage = yield treq.post(target_url, body.encode('utf-8'),
headers=headers, cookies=cookies )
Am Samstag, den 07.01.2017, 12:00 + schrieb Cory Ben
> On Jan 7, 2017, at 8:21 AM, steven meiers wrote:
>
> thanks for the quick replys guys, you were right. a .encode('utf-8')
> helps.
Glad you were able to get it working!
-g___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twist
> On Jan 7, 2017, at 4:00 AM, Cory Benfield wrote:
>
>
>> On 7 Jan 2017, at 02:18, Tristan Seligmann wrote:
>>
>> On Sat, 7 Jan 2017 at 03:23 Glyph Lefkowitz wrote:
>>
>> Maybe we should support unicode for the body as well. We can set the
>> charset in the mime-type and everything so tha
* What?
A new year means renewed ambition. So let's talk about receiving
streaming requests!
* Why?
Twisted's HTTP server implementation does not allow application code
to interact with a request until its body has been entirely
received. It also doesn't allow incremental access to the
Bug summary
__
Summary for 2017-01-01 through 2017-01-08
Opened Closed Total Change
Enhancements: 4 8 1340 -4
Defects: 5 3880 +2
Tasks: 0 1 9
