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 BreamoreBoy
Recipients BreamoreBoy, taverngeek
Date 2010-06-26.10:39:24
SpamBayes Score 0.0014113908
Marked as misclassified No
Message-id <1277548766.34.0.312274203743.issue4919@psf.upfronthosting.co.za>
In-reply-to
Content
I got this in an email from the OP.

"Hi,
I don't even remember this issue any more, but it seems to me that it is completely irrelevant that the error occurred with software that now how has a newer version.

That the essential fact is that the configure process makes mistakes creates a situation in which the includes fail to work properly.  The only relevance of Python x.x is that version DEMONSTRATES the error.

The philosophy that the apparent error need not be considered because right now it happens to a possibly obsolete version of software just means it will happen again.  Presumably, it will be just another hassle for those that test compile against sunstudio.  Using that sort of rationale to close issues is exactly how to make sunstudio into a piece of crap.

sdw
"

Could somebody pick this up?
History
Date User Action Args
2010-06-26 10:39:26BreamoreBoysetrecipients: + BreamoreBoy, taverngeek
2010-06-26 10:39:26BreamoreBoysetmessageid: <1277548766.34.0.312274203743.issue4919@psf.upfronthosting.co.za>
2010-06-26 10:39:25BreamoreBoylinkissue4919 messages
2010-06-26 10:39:24BreamoreBoycreate