From: Benedict V. <Ben...@sj...> - 2005-09-26 13:13:11
|
****** Message from InterScan E-Mail VirusWall NT ****** ** No virus found in attached file noname.htm ** No virus found in attached file noname.htm This message has been scanned, and is intended to be virus-free. ***************** End of message *************** |
From: Jimmy R. <ji...@re...> - 2005-09-26 19:01:38
|
Michael Cariaso wrote: > Benedict Verheyen suggests: > """ > Change the file Lib\site-packages\py2exe\build_exe.py: > Find the line > package =3D ".".join(item.__name__.split(".")[:-1]) > and change it too: > package =3D "\\".join(item.__name__.split(".")[:-1]) >=20 > Then you should get the mxDateTime error anymore at least that did it > for me. > The solution came from somebody on the list so the original message is > still > available somewhere > """ >=20 > And he's right, it works well. This is a good enough solution for me. > But for the sake of which ever developer follows me on this project, > it'd be helpful if I knew if this sort of chance is expected to be part > of a future release of the excellent py2exe program, or if I should be > instructing them how to patch the local copy. >=20 > Thomas Heller requests that this list be used instead of contacting him > directly. >=20 > So Thomas, you out there. Should I expect this to be fixed in a future > version, or is there something more complicated necessary? According to the following note from Thomas, the change has been committed to CVS so it will be in future releases. http://sf.net/mailarchive/forum.php?thread_id=3D8154607&forum_id=3D40690 Jimmy |
From: Thomas H. <th...@py...> - 2005-09-26 19:25:41
|
"Jimmy Retzlaff" <ji...@re...> writes: > Michael Cariaso wrote: >> Benedict Verheyen suggests: >> """ >> Change the file Lib\site-packages\py2exe\build_exe.py: >> Find the line >> package = ".".join(item.__name__.split(".")[:-1]) >> and change it too: >> package = "\\".join(item.__name__.split(".")[:-1]) >> >> Then you should get the mxDateTime error anymore at least that did it >> for me. >> The solution came from somebody on the list so the original message is >> still >> available somewhere >> """ >> >> And he's right, it works well. This is a good enough solution for me. >> But for the sake of which ever developer follows me on this project, >> it'd be helpful if I knew if this sort of chance is expected to be > part >> of a future release of the excellent py2exe program, or if I should be >> instructing them how to patch the local copy. >> >> Thomas Heller requests that this list be used instead of contacting > him >> directly. >> >> So Thomas, you out there. Should I expect this to be fixed in a future >> version, or is there something more complicated necessary? > > According to the following note from Thomas, the change has been > committed to CVS so it will be in future releases. > > http://sf.net/mailarchive/forum.php?thread_id=8154607&forum_id=40690 Yes, it will be in 0.6.3 (which *may* be the last py2exe release that I'll do). Thomas |