From james.gates@sun.com Wed Feb 20 09:23:24 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1KHNNfN009001 for ; Wed, 20 Feb 2008 09:23:24 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1KHNFlc021270 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 20 Feb 2008 17:23:23 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWJ0010HSAWG300@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 09:23:20 -0800 (PST) Received: from dm-uk-01.uk.sun.com ([129.156.101.115]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWJ00GHKSAUWIE0@nwk-avmta-2.sfbay.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 09:23:19 -0800 (PST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-01.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1KHNIOR002832 for ; Wed, 20 Feb 2008 17:23:18 +0000 (GMT) Received: from [192.168.1.102] (vpn-129-150-65-89.East.Sun.COM [129.150.65.89]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id m1KHN4To028600 for ; Wed, 20 Feb 2008 17:23:12 +0000 (GMT) Date: Wed, 20 Feb 2008 12:22:28 -0500 From: James Gates Subject: LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL To: lsarc-ext@sun.com Message-id: <47BC61D4.3050601@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 579 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? From james.gates@sun.com Wed Feb 20 12:48:20 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1KKmK0r000957 for ; Wed, 20 Feb 2008 12:48:20 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m1KKm726018123 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 20 Feb 2008 20:48:10 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWK00H0D1S84300@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 13:48:08 -0700 (MST) Received: from dm-uk-02.uk.sun.com ([129.156.101.196]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWK009M51S75C70@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 13:48:07 -0700 (MST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-02.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1KKm6Hs006329 for ; Wed, 20 Feb 2008 20:48:06 +0000 (GMT) Received: from [192.168.1.102] (vpn-129-150-65-89.East.Sun.COM [129.150.65.89]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id m1KKlttA001831 for ; Wed, 20 Feb 2008 20:48:00 +0000 (GMT) Date: Wed, 20 Feb 2008 15:47:25 -0500 From: James Gates Subject: Re: LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL In-reply-to: <47BC61D4.3050601@sun.com> To: lsarc-ext@sun.com Message-id: <47BC91DD.8060501@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_vMPukhMjyUjcRfu82DmBvw)" X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <47BC61D4.3050601@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 7758 This is a multi-part message in MIME format. --Boundary_(ID_vMPukhMjyUjcRfu82DmBvw) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT 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? --Boundary_(ID_vMPukhMjyUjcRfu82DmBvw) Content-type: text/plain; name=psycopg2_2.0_1pager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=psycopg2_2.0_1pager.txt 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 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 1.4.4. The name of your business unit: Database Technology Group (DBTG) 1.5. Email Aliases: 1.5.1. Responsible Manager: Masood Mortazavi 1.5.2. Responsible Engineer: Staale Smedseng 1.5.3. Marketing Manager: Rebecca Hansen 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: --Boundary_(ID_vMPukhMjyUjcRfu82DmBvw)-- From storycrafter@gmail.com Wed Feb 20 15:14:54 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1KNEsvO012254 for ; Wed, 20 Feb 2008 15:14:54 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1KNEnm3008716 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 20 Feb 2008 15:14:53 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWK0050N8KPAC00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 16:14:49 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWK00MFH8KOF150@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 20 Feb 2008 16:14:48 -0700 (MST) Received: from relay17i.sun.com (ip127.net129179-4.block1.us.syntegra.com [129.179.4.127]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m1KNCYYT027442 for ; Wed, 20 Feb 2008 23:14:48 +0000 (GMT) Received: from mmp14es.sun.com ([160.41.209.24] [160.41.209.24]) by relay17i.sun.com with ESMTP id BT-MMP-339791 for lsarc-ext@sun.com; Wed, 20 Feb 2008 23:14:48 +0000 (Z) Received: from relay16i.sun.com (relay16i.sun.com [129.179.4.126]) by mmp14es.sun.com with ESMTP id BT-MMP-83660 for lsarc-ext@sun.com; Wed, 20 Feb 2008 23:14:48 +0000 (Z) Received: from wf-out-1314.google.com ([209.85.200.173] [209.85.200.173]) by relay1i.sun.com with ESMTP id BT-MMP-3368561 for lsarc-ext@sun.com; Wed, 20 Feb 2008 23:14:48 +0000 (Z) Received: by wf-out-1314.google.com with SMTP id 28so758231wfa.17 for ; Wed, 20 Feb 2008 15:13:07 -0800 (PST) Received: by 10.142.191.2 with SMTP id o2mr1046005wff.132.1203549187724; Wed, 20 Feb 2008 15:13:07 -0800 (PST) Received: by 10.142.158.16 with HTTP; Wed, 20 Feb 2008 15:13:07 -0800 (PST) Date: Wed, 20 Feb 2008 17:13:07 -0600 From: Mark Martin Subject: Re: LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL In-reply-to: <47BC91DD.8060501@sun.com> To: James Gates Cc: lsarc-ext@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pn5yow55AdxZpInL+lAQO7MUQAemn8D4qm5SPQlLQKQ=; b=DRjbRSA7Eo99IKmmBMgQurl7fm00YkRpWRUZ6zRU7TpkSpPzK8zB7NAB3gXFa0iBkmvjWKQSIgFGY8ojsIDtk8vn3DENkhkrpXo6KCXj+F6j3pjKqZN125I5sZo0tAHcOKRcZPv1fJVjyjjxERQMCapmnEPVq92+KAwIh0qksvk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=D7XB+JH2aYTqdEiuQ1hmqmNjj00CVl0nWZkwQwUfBjZl/oS1tTBHUi3cedRmPRy4FoNe0sJKFICzKJDNS3uIg4pbDYPz+6OC4v8wiraSljgNtXWVK0eSrxPYDDNJqi/UynV95XIeKLF4MTuxr/9nwlC3yXRGCTzN8ZcKlBLJy30= X-PMX-Version: 5.2.0.264296 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 0.077sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <47BC61D4.3050601@sun.com> <47BC91DD.8060501@sun.com> Status: RO Content-Length: 440 Waiting for OSo to catch up for materials... On Wed, Feb 20, 2008 at 2:47 PM, James Gates wrote: > 4.5. Interfaces: > > EXPORTED STABILITY NOTES > ------------------------------------------------------------ > psycopg2 Uncommitted (NEW) psycopg2 python module > ZPsycopgDA Uncommitted (NEW) ZPsycopgDA python module > Where will these files be located? From james.gates@sun.com Thu Feb 21 06:27:35 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1LERZqC011219 for ; Thu, 21 Feb 2008 06:27:35 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1LERYgg036421 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Thu, 21 Feb 2008 07:27:34 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWL00M0HETXHP00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 06:27:33 -0800 (PST) Received: from dm-uk-01.uk.sun.com ([129.156.101.115]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWL00HGOETWAD40@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 21 Feb 2008 06:27:33 -0800 (PST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-01.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1LERVcY027325; Thu, 21 Feb 2008 14:27:31 +0000 (GMT) Received: from [192.168.1.102] (vpn-129-150-65-75.East.Sun.COM [129.150.65.75]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id m1LERHZJ015534; Thu, 21 Feb 2008 14:27:23 +0000 (GMT) Date: Thu, 21 Feb 2008 09:26:46 -0500 From: James Gates Subject: Re: LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL In-reply-to: To: Mark Martin Cc: lsarc-ext@sun.com, Staale Smedseng Message-id: <47BD8A26.4080909@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <47BC61D4.3050601@sun.com> <47BC91DD.8060501@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 829 4.1. Details: [...] The project will follow the instructions in PSARC/2005/555 regarding installation directory for these vendor modules. Which basically means /usr/lib/python2.4/vendor-packages// /usr/lib/python2.4/vendor-packages//64/ for the 32-bit and 64-bit versions respectively. Mark Martin wrote: > Waiting for OSo to catch up for materials... > > On Wed, Feb 20, 2008 at 2:47 PM, James Gates wrote: > >> 4.5. Interfaces: >> >> EXPORTED STABILITY NOTES >> ------------------------------------------------------------ >> psycopg2 Uncommitted (NEW) psycopg2 python module >> ZPsycopgDA Uncommitted (NEW) ZPsycopgDA python module >> > > > Where will these files be located? From Lloyd.Chambers@sun.com Fri Feb 22 11:05:55 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1MJ5sWW010520 for ; Fri, 22 Feb 2008 11:05:55 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1MJ5gAT019288 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Sat, 23 Feb 2008 03:05:53 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWN0061FMDQ4S00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 12:05:50 -0700 (MST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWN009SZMDPZEE0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 12:05:49 -0700 (MST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m1MJ5nSf008250 for ; Fri, 22 Feb 2008 11:05:49 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JWN00B01M4S5600@fe-sfbay-10.sun.com> (original mail from Lloyd.Chambers@Sun.COM) for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Fri, 22 Feb 2008 11:05:49 -0800 (PST) Received: from [192.168.1.8] ([129.150.18.151]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JWN000CVMDGWS30@fe-sfbay-10.sun.com>; Fri, 22 Feb 2008 11:05:48 -0800 (PST) Date: Fri, 22 Feb 2008 11:05:39 -0800 From: Lloyd L Chambers Subject: Re: LSARC/2008/127 psycopg2: Python DBAPI 2.0 driver for PostgreSQL In-reply-to: <47BC91DD.8060501@sun.com> Sender: Lloyd.Chambers@sun.com To: James Gates Cc: lsarc-ext@sun.com Message-id: <9E777FA5-DCC2-4E8A-90CB-9DC9FB7DE5F6@sun.com> MIME-version: 1.0 X-Mailer: Apple Mail (2.919.2) Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <47BC61D4.3050601@sun.com> <47BC91DD.8060501@sun.com> Status: RO Content-Length: 7749 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 > > 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 > > 1.4.4. The name of your business unit: > > Database Technology Group (DBTG) > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: > > Masood Mortazavi > > 1.5.2. Responsible Engineer: > > Staale Smedseng > > 1.5.3. Marketing Manager: > > Rebecca Hansen > > 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@sun.com Sun Microsystems, Inc From james.gates@sun.com Thu Feb 28 09:17:26 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m1SHHPf8008757 for ; Thu, 28 Feb 2008 09:17:26 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m1SHHIa6013554 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Fri, 29 Feb 2008 01:17:24 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JWY0002ZLCYAV00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 28 Feb 2008 10:17:23 -0700 (MST) Received: from dm-uk-02.uk.sun.com ([129.156.101.196]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JWY00IIVLBWQV50@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Thu, 28 Feb 2008 10:16:44 -0700 (MST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-02.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m1SHGhcp023064; Thu, 28 Feb 2008 17:16:43 +0000 (GMT) Received: from [192.168.1.102] (vpn-129-150-64-163.East.Sun.COM [129.150.64.163]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id m1SHGUNp018003; Thu, 28 Feb 2008 17:16:37 +0000 (GMT) Date: Thu, 28 Feb 2008 12:15:58 -0500 From: James Gates Subject: LSARC case approved 02/28/2008 (2008/127) To: Staale Smedseng Message-id: <47C6EC4E.8000909@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 231 Name: psycopg2: Python DBAPI 2.0 driver for PostgreSQL Submitter: Staale Smedseng Owner: James Gates Interest: X-Original-Status: closed approved fast-track 02/28/2008 Exposure: open Comment: