As mentioned on the mailing list, Spyce development is going on in a subversion repository. We (well, I) got tired of waiting for sourceforge to leave the CVS dark ages... Get your bleeding edge spyce from http://svn-hosting.com/svn/spyce.
The web site will be updated with this information eventually soon.
(Incidently, I use svn-hosting.com for several projects and it's an excellent, reasonably priced service if you feel you have better things to do than learn how to admin a new source control system. I run the svn repository for my day job and I'd rather let someone else do it when I have the choice.)
Earlier, I wrote about how ORM developers shouldn't try to re-invent SQL . It doesn't need to be done, and you're not likely to end up with an actual improvement. SQL may be designed by committee, but it's also been refined from thousands if not millions of man-years of database experience. The same applies to DDL. (Data Definition Langage -- the part of the SQL standard that deals with CREATE and ALTER.) Unfortunately, a number of Python ORMs are trying to replace DDL with a homegrown Python API. This is a Bad Thing. There are at least four reasons why: Standards compliance Completeness Maintainability Beauty Standards compliance SQL DDL is a standard. That means if you want something more sophisticated than Emacs, you can choose any of half a dozen modeling tools like ERwin or ER/Studio to generate and edit your DDL. The Python data definition APIs, by contrast, aren't even compatibile with other Python tools. You can't take a table definition
Comments