I'd like to work on making it a viable development platform first. So my priorities would be:
* unit tests,
* exception handling,
* restarting when source is changed.
For logging, shouldn't we use Python's built-in logging facility?
-ww
On Feb 1, 2005, at 5:47 PM, Ian Bicking wrote:
I'd come up with a better list if I we did this, but this is off the top of my head:
* Exception handling and reporting
* Configuration
* PSP
* TaskKit
* Smoothing out deployment (server integration; mostly a matter of glue scripts)
* Logging (well, WebKit doesn't do this well either)
* Better sessions (DynamicStore style)
* Test framework (there are some basic functional tests, and other portions have unit tests; still, I find this isn't a terribly motivating sprinting topic ;)
* Documentation (well, I don't know if WebKit is that much further ahead; writing documentation for Webware reminds me of the all the rough edges and arbitrary aspects. I'm writing up the development process for a coworker now, which is why I'm feeling all down on it. I believe WSGIKit documentation be more pleasant; that said, I don't think it's a great topic for a sprint either.)
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
