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 anders.rundgren.net@gmail.com
Recipients anders.rundgren.net@gmail.com, bob.ippolito, ethan.furman, rhettinger
Date 2014-12-29.09:58:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419847110.11.0.128746604663.issue23123@psf.upfronthosting.co.za>
In-reply-to
Content
Well, I could have insisted on canonicalization of floating-point data but that's so awkward that outlawing such data is a cleaner approach.  Since the target for JCS is security- and payment-protocols, I don't think the absence of floating-point support will be a show-stopper. I does though make the IETF folks unhappy.

Another reason for still wanting it to work as currently specified is because it would be nice to have JCS running on three fully compatible platforms, including one which I haven't designed :-)
History
Date User Action Args
2014-12-29 09:58:30anders.rundgren.net@gmail.comsetrecipients: + anders.rundgren.net@gmail.com, rhettinger, bob.ippolito, ethan.furman
2014-12-29 09:58:30anders.rundgren.net@gmail.comsetmessageid: <1419847110.11.0.128746604663.issue23123@psf.upfronthosting.co.za>
2014-12-29 09:58:30anders.rundgren.net@gmail.comlinkissue23123 messages
2014-12-29 09:58:29anders.rundgren.net@gmail.comcreate