Hi On 10 January 2011 18:04, Anthony Tuininga <[email protected]> wrote: > Hi, > > This is a bug in the Python win32 extensions which was fixed 7 weeks > ago by Mark Hammond. The suggested fix below is the one that has been > checked in, too. :-) You can make the same change yourself and all > will be well. I've just tested it myself and found that to be the > case. I'm not sure when the next release of the Python win32 > extensions is going to be since the last one was in 2009! See here for > the diff > > http://pywin32.cvs.sourceforge.net/viewvc/pywin32/pywin32/win32/Lib/win32verstamp.py?r1=1.5&r2=1.6
Ha! :) Exactly what I thought. > The reason this has come up now is because of the fact that I added > support for stamping the code with a version resource. I could turn Ah, OK. That explains it then :) > that off for Python 3 or catch the error and print a message > indicating to fix the bug (I generally don't like this sort of code > but this might be a good reason for such) or just modify the > README.txt to add the warning in there. Any thoughts? Nobody had until very recently requested the version resource stuff, so maybe you could disable it by default for Python 3, but provide an option to enable it if you want it and have a working version of win32verstamp.py? -- Michael Wood <[email protected]> ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ cx-freeze-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
