Liam Clarke wrote: > Hi all, > > After having a frustrating night last night trying to install pyid3lib > on XP, which I think is due to something in distutils.core, I'm > wondering how I should report it. > > I have the dotNET framework 2.0 installed, which should give distutils > access to the MSVC++ compiler, but it's searching for the 1.1 > framework, and so tells me I have no dotNET install. > > This is a pain in the donkey synonym, but after some mucking about > trying to compile the extension myself (which never quite worked) I > found that you can specify a different compiler, so I tried mingw32. > Unfortunately, that errored to the extent that where the error started > exceeded my console buffer, even when set to max. > > Secondly, how and where do bug reports go? I thought I'd ask here > because I want to avoid the "noob" comments and "use a real OS" > comments...
If you want to pursue this I suggest you post a detailed report on your problem to comp.lang.python. Don't assume it is a distutils bug, you will get a better response if you assume that you are doing something wrong and ask for help. You can speculate that it might be a bug, but one of the maxims of c.l.py is something like, "If you think you have found a bug in Python, you're probably wrong" - and the maxim is often right. c.l.py is pretty friendly to newbies who give a clear problem statement and don't start with the belief that Python is broken. I don't think I have ever seen a "use a real OS" comment there and it's clear that some of the Python heavyweights are very familiar with Windows. Bug reports go to SourceForge - http://sourceforge.net/tracker/?group_id=5470&atid=105470 - but I would try c.l.py first. Kent _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
