LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL
Lloyd L Chambers
Lloyd.Chambers at sun.com
Fri Feb 22 11:05:39 PST 2008
Looks good, but how does on pronounce 'psycopg2' and 'ZPsycopgDA'?
On Feb 20, 2008, at 12:47 PM, James Gates wrote:
> 1pager attached.
>
> James Gates wrote:
>> I am sponsoring this fast-track on behalf of Staale Smedseng. The
>> timer expires 02/28/08. Attached is a copy of the proposal, which
>> can also be found in the case directory.
>> I believe it qualifies for micro/patch release binding.
>> I have also discussed interface taxonomy with Staale. He believes
>> the Python DBAPI 2.0 standard (PEP-249) is stable enough (and the
>> community sufficiently reliable) to warrant classifying the
>> exported interfaces as uncommitted. But I am unsure if we can have
>> a feature that exports uncommitted interfaces, but depends on
>> volatile interfaces?
> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
> Copyright 2008 Sun Microsystems
>
>
> 1. Introduction
> 1.1. Project/Component Working Name:
>
> psycopg2: Deliver Python DBAPI 2.0 driver for PostgreSQL into
> OpenSolaris and Solaris
>
> 1.2. Name of Document Author/Supplier:
>
> Staale Smedseng <staale dot smedseng at sun dot com>
>
> 1.3. Date of This Document:
>
> February 15, 2008
>
> 1.4. Name of Major Document Customer(s)/Consumer(s):
> 1.4.1. The PAC or CPT you expect to review your project:
>
> Database
>
> 1.4.2. The ARC(s) you expect to review your project:
>
> LSARC
>
> 1.4.3. The Director/VP who is "Sponsoring" this project:
>
> Heidi Bergh-Hoff <heidi dot bergh-hoff at sun dot com>
>
> 1.4.4. The name of your business unit:
>
> Database Technology Group (DBTG)
>
> 1.5. Email Aliases:
> 1.5.1. Responsible Manager:
>
> Masood Mortazavi <masood dot mortazavi at sun dot com>
>
> 1.5.2. Responsible Engineer:
>
> Staale Smedseng <staale dot smedseng at sun dot com>
>
> 1.5.3. Marketing Manager:
>
> Rebecca Hansen <rebecca dot hansen at sun dot com>
>
> 1.5.4. Interest List:
>
> 2. Project Summary
> 2.1. Project Description:
>
> The following is to be delivered into OpenSolaris SFW
> consolidation:
>
> * The psycopg2 implementation of the Python DBAPI 2.0 as
> part of the vendor-specific modules delivered with the
> Python interpreter.
>
> * The associated ZPsycopgDA module developed by the psycopg2
> team, for Zope access to PostgreSQL databases. ZPsycopgDA
> employs the psycopg2 module.
>
> The project requests patch release binding.
>
> 2.2. Risks and Assumptions:
>
> psycopg2 is an open source product, and Sun is not involved in
> its development. However, Psycopg2 should be considered a
> mature and stable product, implementing the Python DBAPI 2.0
> standard (PEP-249). The associated technical risks with
> including psycopg2 is considered low.
>
> The business risks associated with not providing a Python
> interface for PostgreSQL is considered high, as we would
> provide a less complete environment for PostgreSQL as compared
> to what the open source community would expect.
>
> 3. Business Summary
> 3.1. Problem Area:
>
> psycopg2 is necessary for Python application to be able to
> work with a PostgreSQL database. Both Python and PostgreSQL
> are delivered with Solaris.
>
> 3.2. Market/Requester:
>
> Any Solaris user who wants to access PostgreSQL from Python.
>
> 3.3. Business Justification:
>
> An interface for accessing a PostgreSQL database from Python
> applications is necessary for completeness of our PostgreSQL
> offering on Solaris, in particular compared to other platforms
> delivering PostgreSQL.
>
> 3.4. Competitive Analysis:
>
> 3.5. Opportunity Window/Exposure:
>
> Psycopg2 is ready to be integrated.
>
> 3.6. How will you know when you are done?:
>
> When the psycopg2 driver is delivered into the OpenSolaris SFW
> consolidation.
>
> 4. Technical Description:
> 4.1. Details:
>
> psycopg2 is an open source (GPL license) Python module
> implementing a Python DBAPI 2.0 compliant database driver for
> use with the PostgreSQL database. This project intends to
> deliver this module into Solaris both for 32-bit and 64-bit
> Python.
>
> Also, the associated Zope ZPsycopgDA module will be
> delivered. This module provides access to PostgreSQL from
> Zope, and builds on psycopg2. ZPsycopgDA is developed by the
> same team as psycopg2.
>
> The project will follow the instructions in PSARC/2006/666
> regarding setting correct mtime on derived python files
> (*.pyc), avoiding Python interpreter rebuild on module load.
>
> The project will follow the instructions in PSARC/2005/555
> regarding installation directory for these vendor modules.
>
> 4.2. Bug/RFE Number(s):
>
> 4.3. In Scope:
>
> 4.4. Out of Scope:
>
> 4.5. Interfaces:
>
> EXPORTED STABILITY NOTES
> ------------------------------------------------------------
> psycopg2 Uncommitted (NEW) psycopg2 python module
> ZPsycopgDA Uncommitted (NEW) ZPsycopgDA python module
>
>
> IMPORTED STABILITY NOTES
> ------------------------------------------------------------
> Python 2.4.x Volatile PSARC/2005/532,PSARC/2006/666
> libpq Volatile LSARC/2008/004
>
> 4.6. Doc Impact:
>
> Python modules are self-documenting (documentation included
> in the module files). No special care has to be taken.
>
> 4.7. Admin/Config Impact:
>
> 4.8. HA Impact:
>
> 4.9. I18N/L10N Impact:
>
> 4.10. Packaging & Delivery:
>
> The following package will be created: SUNWpsycopg2. This
> module will contain both the psycopg2 module and the
> dependent ZPsycopgDA module.
>
> 4.11. Security Impact:
>
> 4.12. Dependencies:
>
> LIBRARY VERSION COMMENT
> --------------------------------------------------
> libpq.so 5.x PostgreSQL client library
> python 2.4.x Python interpreter
>
> 5. Reference Documents:
>
> Psycopg2 wiki
> http://www.initd.org/tracker/psycopg/wiki/PsycopgTwo
>
> PEP-249: Python Database API Specification v2.0
> http://www.python.org/dev/peps/pep-0249/
>
> PSARC/2005/555 "Python 'vendor-packages' support"
>
> PSARC/2006/666 "64-bit Python and removal of Python 2.3 from
> Nevada"
>
> LSARC/2008/004 "Integrate PostgreSQL version 8.3 into Solaris"
>
> 6. Resources and Schedule:
> 6.1. Projected Availability:
>
> Delivery targeted for snv_86 (Q4FY08), and Solaris 10 update
> at first opportunity.
>
> 6.2. Cost of Effort:
>
> Minimal. One resource to integrate into SFW gate.
>
> 6.3. Cost of Capital Resources:
>
> 6.4. Product Approval Committee requested information:
> 6.4.1. Consolidation or Component Name:
>
> SFWNV
>
> 6.4.3. Type of CPT Review and Approval expected:
> 6.4.4. Project Boundary Conditions:
> 6.4.5. Is this a necessary project for OEM agreements:
> 6.4.6. Notes:
> 6.4.7. Target RTI Date/Release:
> 6.4.8. Target Code Design Review Date:
> 6.4.9. Update approval addition:
>
> 6.5. ARC review type:
>
> FastTrack
>
> 6.6. ARC Exposure:
>
> Open.
>
> 6.6.1. Rationale:
>
> 7. Prototype Availability:
> 7.1. Prototype Availability:
>
> 7.2. Prototype Cost:
---
Lloyd L Chambers
lloyd.chambers at sun.com
Sun Microsystems, Inc
More information about the opensolaris-arc
mailing list