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 Retro, belopolsky, brian.curtin, georg.brandl, lemburg, mark.dickinson, michael.foord, pitrou, rhettinger
Date 2010-12-02.22:08:14
SpamBayes Score 2.3761885e-07
Marked as misclassified No
Message-id <1291327699.21.0.727167397491.issue10562@psf.upfronthosting.co.za>
In-reply-to
Content
> Personally, I think it's more important to be able to read
> scientific data easily without too many problems, then to be
> able to write the processed data in exactly the same way it
> was read.

I wonder whether there are many examples where scientific data is written in a form that Python's complex() constructor couldn't currently read, but would be able to read if it accepted 'i' in place of 'j'.

My (wild) guess would be that, in the cases where the data isn't stored in binary form anyway, complex numbers are written simply as pairs of floats.
History
Date User Action Args
2010-12-02 22:08:19mark.dickinsonsetrecipients: + mark.dickinson, lemburg, georg.brandl, rhettinger, belopolsky, pitrou, Retro, michael.foord, brian.curtin
2010-12-02 22:08:19mark.dickinsonsetmessageid: <1291327699.21.0.727167397491.issue10562@psf.upfronthosting.co.za>
2010-12-02 22:08:14mark.dickinsonlinkissue10562 messages
2010-12-02 22:08:14mark.dickinsoncreate