<p><br>
On Dec 26, 2010 2:55 PM, "Dan Villiom Podlaski Christiansen" <<a href="mailto:danchr@gmail.com">danchr@gmail.com</a>> wrote:<br>
><br>
> On 26 Dec 2010, at 16:39, Augie Fackler wrote:<br>
><br>
>> On Dec 26, 2010, at 6:51 AM, Dan Villiom Podlaski Christiansen wrote:<br>
>>><br>
>>><br>
>>> # HG changeset patch<br>
>>> # User Dan Villiom Podlaski Christiansen <<a href="mailto:danchr@gmail.com">danchr@gmail.com</a>><br>
>>> # Date 1293200527 -3600<br>
>>> # Node ID a37295adc5d962fd8ea86b4dc2472b0ad0f11deb<br>
>>> # Parent 4233e0fb74d1d801ad2ce9e3f713a0ca4c8ba668<br>
>>> test-trusted.py: fix on PyPy<br>
>>><br>
>>> The test previously did a few print statements without end-of-line<br>
>>> followed by a write from the UI object. For some reason, PyPy<br>
>>> consistently inserted a space one character later. Changing the print<br>
>>> statements to include a newline fixes this.<br>
>><br>
>><br>
>> This sounds like a bug in pypy to me. Do the pypy guys not agree?<br>
><br>
><br>
> I just checked, and the warning is printed on standard error, whereas the dots were printed on standard output. The exact order of intermingled stdout/stderr output seems thoroughly into implementation-defined territory…</p>
<p>Fair enough.</p>
<p>><br>
> --<br>
><br>
><br>
> Dan Villiom Podlaski Christiansen<br>
> <a href="mailto:danchr@gmail.com">danchr@gmail.com</a><br>
><br>
</p>