>>>>> "tavis" == Tavis Rudd <[EMAIL PROTECTED]> writes:
tavis> On Tuesday 02 April 2002 06:55, you wrote: >> Now that 0.7 is out, I think it's high time that we moved Webware >> in the direction of a 1.0 release. What things still need to be >> done? tavis> In order of priority: tavis> - completely automated test suite, that is easy to add new tavis> tests to I'm guessing here, but I suspect this should be a combination of PyUnit tests and some kind of Web app testing framework; a friend of mine's coworker, Keyton Weissinger, has just released a Web app testing framework, which he calls Puffin, (recently announced in c.l.py.a) which Webware might want to adapt or adopt... tavis> - a better logging framework: tavis> - separation of error reporting from error logging tavis> - based on either Sacha's LoggingKit or PEP 282 tavis> (http://python.sourceforge.net/peps/pep-0282.html) The implementation of 282 that's been floating around looks very interesting. I've been playing with it for use in a Py project. URL to Sacha's LoggingKit? I can't remember hearing about this before. >> But in my opinion, it's only the lack of automated testing that >> really prevents us from being at a 1.0 level. There are a few minor tweaks I suspect to get in before 1.0 as well, but I'd say the big things are the testing framework, distutils, better docs, and logging solution. The existing installation script works fine, but a distutils setup would be more ideal; on my box I have 3 working versions of python, and the whole /usr/bin/env python does not pick the right one for Webware, so I had to fix that in the existing script. That wouldn't have happened with distutils since I'd have run "python2.2 setup.py install", but that is admittedly a small matter. Best, Kendall Clark _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
