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 exarkun
Recipients exarkun, tarek, zooko
Date 2009-01-28.00:25:04
SpamBayes Score 6.15242e-11
Marked as misclassified No
Message-id <>
As far as Twisted is concerned, the two cases Tarek mentioned aren't
really relevant.  In order for Zooko's use case to be handled ("install
Twisted on an OLPC"), what would be ideal is if there were a way to tell
distutils about an extension which is optional.  It doesn't matter if it
can be built or not.  Any failure is irrelevant.

This doesn't necessarily have to mean that errors pass silently.  The
build failure can still be reported.  The build could even fail by
default and distutils could gain a new option for switching the behavior
to succeeding if only optional extensions fail to build.  Or it could be
the other way around, with an option to make the build fail if any
optional extensions cannot be built (this approach favors people who
don't really know what a "build" is and just want something installed,
leaving the more advanced option to people who are able to figure out
that there are options that control build behavior).
Date User Action Args
2009-01-28 00:25:08exarkunsetrecipients: + exarkun, zooko, tarek
2009-01-28 00:25:08exarkunsetmessageid: <>
2009-01-28 00:25:06exarkunlinkissue4706 messages
2009-01-28 00:25:04exarkuncreate