Mark Lawrence <breamore...@yahoo.co.uk> added the comment: 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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4919> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
