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 jcea
Recipients benjamin.peterson, georg.brandl, jcea, mduft
Date 2011-04-27.17:12:04
SpamBayes Score 2.8643754e-14
Marked as misclassified No
Message-id <1303924325.65.0.829249589742.issue11937@psf.upfronthosting.co.za>
In-reply-to
Content
I don't agree with some details of the patch (I would move the log-like calculation to a inline function, and document WHY it is needed at all, for instance), but supporting a new platform is good, moreover when the patch is so small.

I would ask for a seasoned Python-developer to decide the target for this. Personally I would be OK to target 2.7.2, 3.2.1 and 3.3. But since this would be considered a new feature the target would be 3.3. Given the special status of 2.7 (to be maintained for a long time), I would target it too. In any case, this is something that the release managers of each version should consider.

I am "nosy-ing" Benjamin Peterson (2.7) and Georg Brandl (3.2) as release managers. I am interested in their opinion. I don't think we should involucrate 3.1 with this, with 3.2 already published.

After that, we can discuss the patch details.

PS: Markus, could you possibly summarize intierix?. We would need a patch for 3.3 too. Maybe too for 3.2, if Georg opinion is favourable.
History
Date User Action Args
2011-04-27 17:12:05jceasetrecipients: + jcea, georg.brandl, benjamin.peterson, mduft
2011-04-27 17:12:05jceasetmessageid: <1303924325.65.0.829249589742.issue11937@psf.upfronthosting.co.za>
2011-04-27 17:12:05jcealinkissue11937 messages
2011-04-27 17:12:04jceacreate