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

Not a Development Environment

[TeamSPAM]

While this may be an interesting project, it is not a development environment. It appears to be a framework/library for building services. If this were java, then this project would be similar to tomcat or jboss.

Re:Not a Development Environment

[znerd]

In fact it would be more like XINS, which is a framework that runs within a Java environment (Tomcat, JBoss, etc.) which also supports automatic load-balancing, fail-over, without losing requests, lossless re-initialization, etc. etc.

This would bring Python to a new level of professional server-side applications.

Re:Not a Development Environment

[TeamSPAM]

XINS does appear to be a close java equivilent compare to my examples. Either way I read the title and description which lead me to think this was an IDE for Python.

Comments from the author

[tgt]

First of all, thank you for attention.

Now, I will try to answer some of the above question and explain my point.

This projects is a live development environment (you may call it framework or library) which simply grew out of my own personal development needs. As I do development of business-oriented services, it answers some of the real questions.

For example, "... Or; you could try writing it correctly from the beginning." is wrong. Have you ever written anything which was right from the start or would not have to be changed ever ? On the other hand, have you ever faced a need to restart a busy live service for upgrade because there is a typo in a wording ?

This leads the first (out of the two) Pythomnic principles - simplify _building_ (introducing new stuff and fixind existing). You can change the source code on the fly and reconfigure the thing without stopping the service, moreover without any visible service interruption.

Py-Fate is useful indeed, thank you. It's the second major Pythomnic principle - be ready for failures as they are inevitable and design accordingly. It can be used as a separate project (which it is - in fact a single Python module), but it fits Pythomnic making it more useful.

As to the lack of useful stuff, agree 100%, but please, this is one person project release 1.0. If you would like to contribute, you are sure welcome. The information on the site is covering everything, but it's certainly not written in marketing language (I never worked in marketing). If you have questions, please feel free to ask (e-mail or forum).

I will be continuing the project, because I feel the project is answering the right questions. You may contribute, or you can help with design or you can just consider it to be a concept at this moment and keep an eye on it.