On 15 Oct, 2009, at 3:39, Chris Barker wrote:
Ronald Oussoren wrote:Is anyone interested in helping to create a testsuite for py2app?The first priority would be to have some blackbox tests, unittests can be added later.good idea. The testcases would be simple applications with asetup.py and a verification script. Testcases should focus on variations/libraries that people actually use (Cocoa application, wxWidget application, Tk application, ..., using matplotlib, ...)I've got a few of these already -- wx and mpl at least, though no verification scripts. I can't imagine they'd be hard to write, though.I'm out of town and without my mac for a while. If I don't contribute something in a few weeks, feel free to ask again.
That would be great. I'll start working on a test harnass and will report back when I'm ready for contributions.
NOTE: I'm not sure quite what to do to verify -- I can test that it builds and runs, which would be a good start, but that wouldn't test if it would run on another machine... it's a start in any case.
Testing that it builds and runs would be good enough until there are good reasons to expect otherwise. I'll also write a couple of tests that verify that the Python framework gets copied into the bundle for '--standalone' builds and doesn't get copied for '--semi-standalone' ones (including builds using the system python).
NOTE 2: I don't think the OP's problem has been addressed -- he appears to be getting errors because the "python" in his app bundle is a ink to one in the system rather than a self contained copy. This despite using python.org python. Any ideas?
I know, but don't have time to look into that until tomorrow or Sunday. Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
