I'm probably be there just for monday and tuesday. Maybe sunday.
Regarding what to do, I hope to have the automated tests for all kits=20
converted before PyCon so we can rely on them to not break things. It=20=
would be nice to have a build before then too so we are freer to change=20=
Some ideas I have are:
=95 Documentation as Eric Radman suggests.
=95 Some example websites to be included in the distribution. =
thinking one very simple website to get started with, and another fully=20=
featured website with masteads, navigation, forms, user authentication,=20=
and maybe DB support with MiddleKit
=95 Clean up the build process. Instead of building the =
and so forth in place, how about put things in a build/ directory like=20=
=95 Split WebKit into two parts, a WSGI container, and WSGIKit.
=95 Reorganize working app folders. I'm thinking about a folder =
Run.py sets up your python path, and launches the app server. =
server notices that there are no configuration files so it creates a=20
directory for it's files and writes in default config files:
The advantages would be: (1) Easy to clean out temporary webware data,=20=
it's all in one folder. (2) You can distribute applications and=20
examples with just a few files. In the simplest case, run.py and=20
On Jan 31, 2005, at 11:21 PM, Tracy Ruggles wrote:
> I'll be there. Not sure yet how many days early, but at least the=20
> last 2 days of the sprint period, maybe all 4. Any specific work=20
> anyone is interested in?
> Winston Wolff wrote:
winston wolff - (646) 827-2242 - http://www.stratolab.com - learning by=20=