On 10 November 2010 10:39, Connell, Paul <[email protected]> wrote: > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of mark florisson > Sent: 09 November 2010 16:16 > To: [email protected] > Subject: Re: [Cython] Cython gdb on Windows > >> The next problem was with the xml parser. I found I had to manually >> add >> >> from xml.parsers import expat >> > >> Why did you have to do that? I don't believe xml.parsers.expat provides an >> ElementTree interface, so this would break all the code. >> Cygdb needs an ElementTree implementation, of which there are several, and >> it tries all implementations that are out there. > Python2.5 comes with >> xml.etree.ElementTree in the stdlib, and cygdb actually requires python 2.5 >> or higher at this moment so it >should not be an issue. > > Python complained that expat was missing. So I imported it. This is with > Python 2.7 by the way. >
Weird, this shouldn't happen. Could you paste a full traceback so I know which implementation it tried to import and what happened? In any case, it sounds like something was not installed correctly. >> cygdb now goes through the motions of working, although I am against another >> brick wall now in that my modules and python installation are all 64 bit, >> whereas mingw/msys is 32 bit. This isn't cygdb's fault though... >> >> I hope some of this is useful. I've not yet got a useable cygdb, but >> hopefully am getting there. > >>Yes, this is kind of unfortunate that windows is always a problem. > > It certainly is... > > > Cheers, > Paul > _______________________________________________ > Cython-dev mailing list > [email protected] > http://codespeak.net/mailman/listinfo/cython-dev > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
