Message 119142 - Python tracker

➜

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.

In-reply-to
Author	djc
Recipients	djc, jfinkels, theller
Date	2010年10月19日.16:25:19
SpamBayes Score	0.00978485
Marked as misclassified	No
Message-id	<1287505524.5.0.859185793242.issue10036@psf.upfronthosting.co.za>

Content
Current Ubuntu builds from the buildbot also only show the libffi warning: http://www.python.org/dev/buildbot/builders/x86%20Ubuntu%20Shared%203.x/builds/2326/steps/compile/logs/warnings I suspect we don't really fix libffi compile warnings because (a) libffi is just bundled from upstream in python, for ctypes, AFAICT, and (b) libffi maintenance seems to be intermittent at best. For example, it seems like we're not bundling any released version of libffi, but just some snapshot from the upstream repo.

Content

Current Ubuntu builds from the buildbot also only show the libffi warning:
http://www.python.org/dev/buildbot/builders/x86%20Ubuntu%20Shared%203.x/builds/2326/steps/compile/logs/warnings
I suspect we don't really fix libffi compile warnings because (a) libffi is just bundled from upstream in python, for ctypes, AFAICT, and (b) libffi maintenance seems to be intermittent at best. For example, it seems like we're not bundling any released version of libffi, but just some snapshot from the upstream repo.

History
Date	User	Action	Args
2010年10月19日 16:25:24	djc	set	recipients: + djc, theller, jfinkels
2010年10月19日 16:25:24	djc	set	messageid: <1287505524.5.0.859185793242.issue10036@psf.upfronthosting.co.za>
2010年10月19日 16:25:20	djc	link	issue10036 messages
2010年10月19日 16:25:20	djc	create

homepage