Dennis Lee Bieber wrote: > On Sat, 07 Apr 2007 11:36:05 +0200, hg <[EMAIL PROTECTED]> declaimed the > following in comp.lang.python: > >> >> I am now facing your problem ... on a machine that used to work fine. >> >> Have you figured it out ? >> >> Could it be a conflict between pyserial and pywin32 ? >> > > The test still runs on my system -- which is still running the > ActiveState 2.4.3 build*... So that probably clears M$ of any > malfeasance (via various and sundry patches). > > The closest a google search came up with was someone trying to > control a serial port printer getting failures on setupcomm (and /not/ > via Python). I think the gist was that any port except the one the > printer was connected to was okay. > > So... Is there some device connected to the port in question? > Possibly a device that has a system level driver (ie, a Windows printer > entry) that might be preventing changes... > > > > > > * Too many 3rd-party modules still aren't available in 2.5 versions > for my tastes... > -- > Wulfraed Dennis Lee Bieber KD6MOG > [EMAIL PROTECTED] [EMAIL PROTECTED] > HTTP://wlfraed.home.netcom.com/ > (Bestiaria Support Staff: [EMAIL PROTECTED]) > HTTP://www.bestiaria.com/
My fault, I actually _had_ the issue with python 2.4 I removed everything and reinstalled python 2.4.4, pywin( lastest) and pyserial (latest) ... the problem is gone. hg -- http://mail.python.org/mailman/listinfo/python-list
