Pythomnic, Development Environment for Python

Dmitry Dvoinikov writes "Just released is a conceptual middleware development environment in (and for) Python called Pythomnic ("Pitomnik" is a Russian for "breeding nursery, reserve"). Recognizing the building as a process in time, Pythomnic focuses on creating an environment in which fault tolerant redundant services can be built. Pythomnic is designed so that source code updates, releases and reconfigurations are made at runtime without any visible service interruption. Likewise, external systems (ex. databases) can be switched at will, with no request lost. Multiple Pythomnic instances running on different machines call each other transparently, thus provoking distribution and redundancy. To complete the picture, a handful of syntactically transparent fault tolerance templates make easy to write fault-tolerant code. "

Comments

Too bad Slashdot doesn't work like K5

[hey!]

Otherwise I'd have given editorial advice, e.g.

(1) Compare and contrast with familiar frameworks and platforms or explain why such a comparison can't be made. For example, I think it would make a lot of sense to compare this to J2EE. If Zope is Python's Tomcat, then is this intended to be Python's J2EE?

(2) Delineate the limits of what this is meant to do for you. This would tell what other parts need to work in concert with this. For example, I notice this google search returns no hits: security site: http://www.pythomnic.org/

More info???

[Evardsson]

The entire site left me wanting nothing more than a little more info. There is one "live demo" piece - that uses a connector that is not currently included in the project. There is very little to tell me why I would choose this over any other middleware solution, such as TurboGears or Django or . . ..
The only thing that really piqued my interest is the inclusion of Py-Fate - but why do I need the rest? I don't think the case was made. If, however, Py-Fate does all that it purports to - well, that would be a handy tool to have.