SIG for Development of Persistence and Transaction Frameworks
There will be a Python Persistence BOF at the O'Reilly Open Source Conference.
A Python Persistence Special Interest Group was recently formed to explore ways to add basic persistence and transaction mechanisms into the core of Python to avoid duplication of effort by a variety of projects that have similar issues. This BOF will permit participants to ponder Python persistence in person. In addition, anyone interested in an informal Python Persistence breakfast discussion with Jim Fulton and Guido van Rossum is welcome to join us at the O'Reilly Food Tent Wednesday morning at 7am.
ProblemA number of projects are underway to provide persistence mechanisms for Python. These efforts have a number of common requirements, including:
Most of these efforts are focused on providing persistence using relational database data. The efforts are, for the most part, proceeding independently. Each will attempt to address the above requirements independently, with much duplication of effort.
The Zope Object Database (ZODB) has satisfied the above requirements for some time. ZODB is currently undergoing a transition from ZODB 3, which was based on ExtensionClass, to ZODB 4, which is based on Python 2.2 new-style classes. As a part of this effort, the ZODB persistence and transaction frameworks are being factored out of ZODB into separate packages, with the hope that they will be of use to other persistence-based frameworks.
It will be a huge duplication of effort if each of the various persistence projects has to address the above requirements independently. Worse, the resulting systems will have independent frameworks that are unlikely to interoperate. Objects built for one framework will need to be rewritten to work with another.
A new persistence-SIG is proposed to explore and, if possible, produce persistence and transaction frameworks that can be used for a variety of persistence implementations, including relational database-based persistence and the ZODB.
Coordinator: Jeremy Hylton
Conclusion: When 1.0 versions of the frameworks are delivered, or September 1, 2003, whichever is sooner.
Deliverables: PEPs documenting the frameworks created and software implementing key parts of the frameworks.
Assuming that a satisfactory framework can be defined, then the framework and core implementations should be included in standard Python distributions.
ScopeThe scope of this SIG includes common frameworks for:
The scope does *not* include: