➜

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 rbcollins
Recipients adaptivelogic, eric.snow, gvanrossum, martius, ncoghlan, pitrou, rbcollins, rhettinger, vstinner, yselivanov
Date 2015-01-26.23:30:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422315057.67.0.99933845598.issue17911@psf.upfronthosting.co.za>
In-reply-to
Content 
So its fairly simple IMO: it will be more code, not less, to support the non-triple API, *and* it can be added later, unless we're proposing not to support the triple API at all (which hasn't been proposed AFAICT).

To me thats a fairly strong argument for adding non-triple support later.
History
Date User Action Args
2015-01-26 23:30:57rbcollinssetrecipients: + rbcollins, gvanrossum, rhettinger, ncoghlan, pitrou, vstinner, eric.snow, yselivanov, adaptivelogic, martius
2015-01-26 23:30:57rbcollinssetmessageid: <1422315057.67.0.99933845598.issue17911@psf.upfronthosting.co.za>
2015-01-26 23:30:57rbcollinslinkissue17911 messages
2015-01-26 23:30:57rbcollinscreate