➜

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 mark.dickinson
Recipients mark.dickinson, skip.montanaro
Date 2009-10-16.08:50:23
SpamBayes Score 6.028511e-13
Marked as misclassified No
Message-id <1255683026.56.0.545074734506.issue7147@psf.upfronthosting.co.za>
In-reply-to
Content 
I think this patch should be applied, on the basis that:

 - the WITHOUT_COMPLEX macro doesn't appear to be documented, or
   linked to any existing configure option

 - there aren't enough developer and/or buildbot cycles to
   keep obscure options like this well tested and maintained

 - building py3k with -DWITHOUT_COMPLEX currently fails anyway

 - the complex type is (slightly) more tightly integrated in
   py3k than in trunk, thanks to PEP 3141:  (-1)**0.5 produces
   a complex result in py3k; in trunk it gives ValueError.

Any objections to getting rid of WITHOUT_COMPLEX?

The patch itself looks fine to me.
History
Date User Action Args
2009-10-16 08:50:26mark.dickinsonsetrecipients: + mark.dickinson, skip.montanaro
2009-10-16 08:50:26mark.dickinsonsetmessageid: <1255683026.56.0.545074734506.issue7147@psf.upfronthosting.co.za>
2009-10-16 08:50:25mark.dickinsonlinkissue7147 messages
2009-10-16 08:50:23mark.dickinsoncreate