This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients benjamin.peterson, daniel.urban, dsdale24
Date 2011-03-20.17:25:56
SpamBayes Score 1.0824674e-14
Marked as misclassified No
Message-id <AANLkTi=CFQNn5qNBdM0cTbib5JBUNWntwtBPYAK5HABF@mail.gmail.com>
In-reply-to <AANLkTikac-ssEM4dudNuqbTD9d3TGD1VBGF6_QVF2xRQ@mail.gmail.com>
Content
2011/3/20 Darren Dale <report@bugs.python.org>:
>
> Darren Dale <dsdale24@gmail.com> added the comment:
>
> On Sun, Mar 20, 2011 at 5:18 AM, Daniel Urban <report@bugs.python.org> wrote:
>>
>> Daniel Urban <urban.dani+py@gmail.com> added the comment:
>>
>> I tried to test your patch, but the build dies with this error:
>> Fatal Python error: Py_Initialize: can't initialize sys standard streams
>> Traceback (most recent call last):
>>  File ".../cpython/Lib/io.py", line 60, in <module>
>> Aborted
>>
>> I don't know why is this, but I get this error consistently with your patch, and no error without the patch.
>
> Have you added any print statements to the patch? I'm working on a
> completely new patch, which only touches abc.py on an existing
> python3.2 install. When I add a print statement to the abstract
> property creation routine, and run test_abc.py, I get the same error.

That's likely because the io library depends on abcs, so using print
in them creates a dependency cycle.
History
Date User Action Args
2011-03-20 17:25:58benjamin.petersonsetrecipients: + benjamin.peterson, daniel.urban, dsdale24
2011-03-20 17:25:56benjamin.petersonlinkissue11610 messages
2011-03-20 17:25:56benjamin.petersoncreate