You all take 7 months to first look at the issue and then decide that you'd
like more information because the initial submission was incomplete?

Oh well,  Suit yourself.  Doesn't matter to me.  I've already stopped using
sunstudio.  That python build was one of the last things I did on Solaris
which I had been actively using for 20 years, but some device driver issues
have made it no longer worth the effort.

sdw

On Sat, Jun 26, 2010 at 4:39 AM, Mark Lawrence <report@bugs.python.org>wrote:

>
> Mark Lawrence <breamoreboy@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 <report@bugs.python.org>
> <http://bugs.python.org/issue4919>
> _______________________________________
>