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 scoder
Recipients akira, brg@gladman.plus.com, gladman, mark.dickinson, mrabarnett, scoder, steven.daprano, terry.reedy, vstinner, wolma
Date 2014-09-25.16:09:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1411661353.22.0.131494634495.issue22477@psf.upfronthosting.co.za>
In-reply-to
Content
IMHO, the most straight forward way for a new gcd() function to work would be to always, predictably return a non-negative value and let users handle all cases themselves where a negative sign of any or all input values has a specific meaning to them. That's the path of least surprise, and it's very easy to implement at the C level for PyLong values (as they are internally unsigned anyway).
History
Date User Action Args
2014-09-25 16:09:13scodersetrecipients: + scoder, terry.reedy, mark.dickinson, vstinner, mrabarnett, steven.daprano, akira, wolma, gladman, brg@gladman.plus.com
2014-09-25 16:09:13scodersetmessageid: <1411661353.22.0.131494634495.issue22477@psf.upfronthosting.co.za>
2014-09-25 16:09:13scoderlinkissue22477 messages
2014-09-25 16:09:13scodercreate