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 brandon-rhodes
Recipients belopolsky, benjamin.peterson, brandon-rhodes, eric.araujo, ncoghlan
Date 2011-03-17.23:56:16
SpamBayes Score 8.401841e-06
Marked as misclassified No
Message-id <1300406177.49.0.656669560299.issue11572@psf.upfronthosting.co.za>
In-reply-to
Content
Éric, the Makefile in Python trunk seems to include Objects/complexobject.o in the build unilaterally without any way to turn it off. What is leading you to believe that Python 3 can conditionally turn the "complex" type off during a build?

I do not understand your question about Unicode — could you reference the line number in the patch file that is worrying you?
History
Date User Action Args
2011-03-17 23:56:17brandon-rhodessetrecipients: + brandon-rhodes, ncoghlan, belopolsky, benjamin.peterson, eric.araujo
2011-03-17 23:56:17brandon-rhodessetmessageid: <1300406177.49.0.656669560299.issue11572@psf.upfronthosting.co.za>
2011-03-17 23:56:16brandon-rhodeslinkissue11572 messages
2011-03-17 23:56:16brandon-rhodescreate