On 11 Feb, 2009, at 18:18, Christopher Barker wrote:
Lack of a proper testing infrastructure is a major issue for py2app
at the moment, it is way to easy to accidently break something
when changing the py2app code base. Having a set of test
applications would at least make it easier to ensure that nothing
gets accidently broken.
Do you have any ideas about how to runs tests automatically?
Not yet. Just testing application launching should be good enough to
find most issues, but I'm afraid there will be some clicking
involved. The important bit is that there needs to be a clear way to
test if everything still works.
Also -- any plans to support eggs? I'm using py2app to bundle up a
Pylons-based app (web framework). It makes heavy use of eggs (and
pkg_resources, the real problem), and I had to write a lot of extra
code to get everything I needed included.
Egg-support is on my todolist, I intend to work on that when I'm at
pycon.
It's worth looking at what bb-freeze is doing -- they're using
modulegraph too. I'd like to see a py2app -- bbfreeze merger, in fact.
It seems the app building process has two distinct parts:
1) figuring out what to include
2) bundling it all up
(1) is pretty platform dependent, so I"d love to see it the same in
a tool for all platforms.
-- OK figuring out which shared libs to include is probably
platform dependent...
It should be possible to move all of that to a platform independent
library, with plugins to detect shared libraries. That would be a
worthwhile exercise because it is rather lame that every packaging
tool needs to reinvent the wheel here.
Ronald
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
