On Apr1, 11:17pm, AchipA <[email protected]> wrote: > > Achipa, I assume you are using some latest trunk source of web2py, > > therefore we are not in the same boat. Would you mind, to use EXACT > > web2py 1.59 's web2py_src.zip and/or web2py_win.zip, and use my > > That's exactly what I did (fresh 1.59 web2py_src.zip from the site). I > do trunk/source development on my linux machine. Windows testing is > somewhat lacking as I only have access to windows through an emulator > (virtualbox). I'll try and scramble a 'real' windows machine (but I > doubt that's of any relation to the issue) and also try to implement > some unittests so we can pinpiont where your and my copy go differebt > routes. That will be fun, multithreaded unittests sure can make a > person go crosseyed.
"Crosseyed", that is exactly how I feel now, after testing 4 different web2py builds: 1.56.4exe, 1.59src, 1.59exe, 1.59homemade exe. >_< I understand you already help me a lot, you always did, many thanks for that! However I suggest you try to use 1.59 web2py_win.zip to do one more last test next time. Because IMHO the src edition is affected by so many possible factors such as Python version, py2exe version, packages like win32con, mysqldb, etc... But web2py_win.zip is standalone therefore not affect by any above factors on the target machine. I just want to make sure, whether the fresh 1.59 web2py_win.zip can cron or not. Thanks! Best regards, Iceberg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
