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 cdavid
Recipients cdavid, christian.heimes, mark.dickinson, rhettinger
Date 2009-01-06.16:05:00
SpamBayes Score 0.20302948
Marked as misclassified No
Message-id <1231257900.98.0.221802927218.issue2121@psf.upfronthosting.co.za>
In-reply-to
Content
@ Mark

Concerning float('inf') * 1j: you're right, my rambling did not make any
sense, sorry.

I agree that adding complexity may be a good reason to warrant an
arbitrary feature; actually, I did not manage to handle nan/inf at first
because of the complexity :) But as I mentioned in a previous comment, I
think my patch simplifies the parsing as well. I suggested to split the
patch in to: one whithout any new feature (no handling of nan/inf), and
then anoter handling nan/inf on the top of it. Would that be acceptable ?

Also, how should I proceed to share implementation between floatobject.c
and complexobject.c ? Would creating a new file for the common code be
acceptable ?
History
Date User Action Args
2009-01-06 16:05:01cdavidsetrecipients: + cdavid, rhettinger, mark.dickinson, christian.heimes
2009-01-06 16:05:00cdavidsetmessageid: <1231257900.98.0.221802927218.issue2121@psf.upfronthosting.co.za>
2009-01-06 16:05:00cdavidlinkissue2121 messages
2009-01-06 16:05:00cdavidcreate