From johnf@sac.sfbay.sun.com Fri Oct 23 12:07:32 2009 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 n9NJ7Vsx027377 for ; Fri, 23 Oct 2009 12:07:31 -0700 (PDT) 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 n9NJ7QV7004832; Fri, 23 Oct 2009 20:07:30 +0100 (BST) 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 <0KRZ00B09EGG1B00@brm-avmta-1.central.sun.com>; Fri, 23 Oct 2009 13:07:28 -0600 (MDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KRZ0050VEGGK140@brm-avmta-1.central.sun.com>; Fri, 23 Oct 2009 13:07:28 -0600 (MDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9NJ7RTJ012507; Fri, 23 Oct 2009 12:07:27 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9NJ7QcP027371; Fri, 23 Oct 2009 12:07:26 -0700 (PDT) Received: (from johnf@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n9NJ7QBC027367; Fri, 23 Oct 2009 12:07:26 -0700 (PDT) Date: Fri, 23 Oct 2009 12:07:26 -0700 (PDT) From: John Fischer Subject: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] To: PSARC-ext@sun.com Message-id: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3292 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Python lxml 1.2. Name of Document Author/Supplier: Author: John Fischer 1.3 Date of This Document: 23 October, 2009 4. Technical Description 1.0 Introduction 1.1 Project/Component Working Name: Python lxml 1.2 Purpose This project delivers the Python lxml bindings for Python 2.4 and Python 2.6. Release binding: Patch 2.0 Project Description lxml is a Pythonic binding for the libxml2 and libxslt libraries. It is unique in that it combines the speed and feature completeness of these libraries with the simplicity of a native Python API, mostly compatible but superior to the well-known ElementTree API. The default Python bindings of libxml2 are fast, thrilling, powerful, and your code might fail in some horrible way that you really shouldn't have to worry about when writing Python code. lxml combines the power of libxml2 with the ease of use of Python. This project is maintained within the Code Speak project. As such the project team will follow the community (http://codespeak.net/lxml) for bug fixes. The project will initially ship with Python 2.4 bindings as well as Python 2.6 bindings. Once the install code is ported to Python 2.6 then install will rely upon the Python 2.6 bindings. The port of install to Python 2.6 is underway. 2.1 Exported Interface table Interface Classification Comments ----------------------------------- --------------- --------------- SUNWpython-lxml Uncommitted SVr4 pkg for Python 2.4 bits SUNWpython26-lxml Uncommitted SVr4 pkg for Python 2.6 bits python2.[46]/vendor-packages/lxml Uncommitted Python binding install location ElementTree API Volatile [4] lxml.etree API Volatile [5] lxml.objectify API Volatile [6] * Note: The Python 2.4 bindings are Obsolete Volatile to match the Python 2.6 and 3.0 case (PSARC 2009/043) 2.2 Imported Interface table Interface Classification Comments ----------------------------------- --------------- --------------- /usr/bin/python2.4 Obsolete PSARC 2009/043 /usr/bin/python2.6 Uncommitted PSARC 2009/043 ====================== 3. Reference Documents ====================== [1] lxml website http://codespeak.net/lxml -- only for reference [2] materials/prototype2.[46] [3] materials/pkginfo2.[46] [4] materials/element.htm -- ElementTree API [5] materials/lxml.etree-api.html -- lxml.etree API [6] materials/lxml.objectify-api.html -- lxml.objectify API 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From johnlev@barman.uk.sun.com Sat Oct 24 05:51:32 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9OCpWLK021497 for ; Sat, 24 Oct 2009 05:51:32 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9OCpWBF015046 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 24 Oct 2009 05:51:32 -0700 (PDT) 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 <0KS000F01RPWL100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 24 Oct 2009 05:51:32 -0700 (PDT) Received: from dm-uk-02.uk.sun.com ([129.156.101.196]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KS000C0ERPVWX10@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 24 Oct 2009 05:51:32 -0700 (PDT) Received: from barman.uk.sun.com (barman.UK.Sun.COM [129.156.132.12]) by dm-uk-02.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9OCpTeF005377; Sat, 24 Oct 2009 13:51:29 +0100 (BST) Received: from johnlev by barman.uk.sun.com with local (Exim 4.42) id 1N1gGc-0002eq-LV; Sat, 24 Oct 2009 14:02:46 +0100 X-URL: http://jurassic.eng/~johnlev/ Date: Sat, 24 Oct 2009 14:02:46 +0100 From: John Levon Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] In-reply-to: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> Sender: John Levon To: John Fischer Cc: PSARC-ext@sun.com Message-id: <20091024130246.GA10007@barman.uk.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> User-Agent: Mutt/1.5.6i Status: RO Content-Length: 347 On Fri, Oct 23, 2009 at 12:07:26PM -0700, John Fischer wrote: > ElementTree API Volatile [4] > lxml.etree API Volatile [5] > lxml.objectify API Volatile [6] Can you confirm you'll be delivering both 32 and 64 bit versions of the .so files? regards john From John.Fischer@sun.com Mon Oct 26 13:55:25 2009 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 n9QKtOX8007676 for ; Mon, 26 Oct 2009 13:55:25 -0700 (PDT) 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 n9QKtJ90024220; Tue, 27 Oct 2009 04:55:22 +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 <0KS5007013G95500@brm-avmta-1.central.sun.com>; Mon, 26 Oct 2009 14:55:21 -0600 (MDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KS5002T33G8M320@brm-avmta-1.central.sun.com>; Mon, 26 Oct 2009 14:55:20 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9QKtKdW020687; Mon, 26 Oct 2009 20:55:20 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KS5009002TW3P00@mail-amer.sun.com>; Mon, 26 Oct 2009 14:55:20 -0600 (MDT) Received: from [192.168.0.103] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KS5009Z13G03V20@mail-amer.sun.com>; Mon, 26 Oct 2009 14:55:12 -0600 (MDT) Date: Mon, 26 Oct 2009 13:52:19 -0700 From: John Fischer Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] In-reply-to: <20091024130246.GA10007@barman.uk.sun.com> Sender: John.Fischer@sun.com To: John Levon Cc: John Fischer , PSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4AE60C03.4010203@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> <20091024130246.GA10007@barman.uk.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20090929) Status: RO Content-Length: 472 John, Yes, we will be delivering both 32 and 64 bit versions of the .so files. John John Levon wrote: > On Fri, Oct 23, 2009 at 12:07:26PM -0700, John Fischer wrote: > >> ElementTree API Volatile [4] >> lxml.etree API Volatile [5] >> lxml.objectify API Volatile [6] > > Can you confirm you'll be delivering both 32 and 64 bit versions of the > .so files? > > regards > john From John.Fischer@sun.com Thu Oct 29 10:34:05 2009 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 n9THY3CQ001496 for ; Thu, 29 Oct 2009 10:34:04 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n9THXjJq016402 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 30 Oct 2009 01:34:02 +0800 (SGT) 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 <0KSA00G0BE4NPM00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 29 Oct 2009 10:33:59 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSA009ACE4MODF0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 29 Oct 2009 10:33:58 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9THXv0q022594 for ; Thu, 29 Oct 2009 17:33:57 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KSA00200BABLL00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 29 Oct 2009 11:33:57 -0600 (MDT) Received: from [192.168.0.102] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KSA00C0AE45PD30@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 29 Oct 2009 11:33:42 -0600 (MDT) Date: Thu, 29 Oct 2009 10:30:48 -0700 From: John Fischer Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] In-reply-to: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> Sender: John.Fischer@sun.com Cc: PSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4AE9D148.9070201@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20090929) Status: RO Content-Length: 3772 All, Tomorrow is the timeout for this case. I have addressed John Levon's question about 32-bit and 64-bit versions of the .so files. Any other issues welcome. Thanks, John John Fischer wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Python lxml > 1.2. Name of Document Author/Supplier: > Author: John Fischer > 1.3 Date of This Document: > 23 October, 2009 > 4. Technical Description > 1.0 Introduction > 1.1 Project/Component Working Name: > > Python lxml > > 1.2 Purpose > > This project delivers the Python lxml bindings for Python 2.4 > and Python 2.6. > > Release binding: Patch > > 2.0 Project Description > > lxml is a Pythonic binding for the libxml2 and libxslt libraries. > It is unique in that it combines the speed and feature completeness > of these libraries with the simplicity of a native Python API, > mostly compatible but superior to the well-known ElementTree API. > The default Python bindings of libxml2 are fast, thrilling, powerful, > and your code might fail in some horrible way that you really > shouldn't have to worry about when writing Python code. lxml combines > the power of libxml2 with the ease of use of Python. > > This project is maintained within the Code Speak project. As such > the project team will follow the community (http://codespeak.net/lxml) > for bug fixes. > > The project will initially ship with Python 2.4 bindings as well as > Python 2.6 bindings. Once the install code is ported to Python 2.6 > then install will rely upon the Python 2.6 bindings. The port of > install to Python 2.6 is underway. > > 2.1 Exported Interface table > Interface Classification Comments > ----------------------------------- --------------- --------------- > SUNWpython-lxml Uncommitted SVr4 pkg for > Python 2.4 bits > SUNWpython26-lxml Uncommitted SVr4 pkg for > Python 2.6 bits > python2.[46]/vendor-packages/lxml Uncommitted Python binding > install > location > ElementTree API Volatile [4] > lxml.etree API Volatile [5] > lxml.objectify API Volatile [6] > > * Note: The Python 2.4 bindings are Obsolete Volatile to match the > Python 2.6 and 3.0 case (PSARC 2009/043) > > 2.2 Imported Interface table > Interface Classification Comments > ----------------------------------- --------------- --------------- > /usr/bin/python2.4 Obsolete PSARC 2009/043 > /usr/bin/python2.6 Uncommitted PSARC 2009/043 > > ====================== > 3. Reference Documents > ====================== > [1] lxml website http://codespeak.net/lxml -- only for reference > [2] materials/prototype2.[46] > [3] materials/pkginfo2.[46] > [4] materials/element.htm -- ElementTree API > [5] materials/lxml.etree-api.html -- lxml.etree API > [6] materials/lxml.objectify-api.html -- lxml.objectify API > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From John.Fischer@sun.com Fri Oct 30 12:02:16 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n9UJ2FTR014184 for ; Fri, 30 Oct 2009 12:02:16 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9UJ25EV009311 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 30 Oct 2009 12:02:15 -0700 (PDT) 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 <0KSC0031BCVLTD00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 12:02:09 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSC00HHTCVKIRB0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 12:02:09 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9UJ28mc023071 for ; Fri, 30 Oct 2009 19:02:08 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KSC00600CETRU00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 13:02:08 -0600 (MDT) Received: from [192.168.0.102] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KSC009LNCV8XIA0@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 13:01:57 -0600 (MDT) Date: Fri, 30 Oct 2009 11:59:03 -0700 From: John Fischer Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] In-reply-to: <4AE9D148.9070201@sun.com> Sender: John.Fischer@sun.com To: PSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4AEB3777.5020008@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> <4AE9D148.9070201@sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 4120 Anyone care to +1 this fast track? Thanks, John John Fischer wrote: > All, > > Tomorrow is the timeout for this case. I have addressed John Levon's > question about 32-bit and 64-bit versions of the .so files. Any other > issues welcome. > > Thanks, > > John > > > John Fischer wrote: >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Python lxml >> 1.2. Name of Document Author/Supplier: >> Author: John Fischer >> 1.3 Date of This Document: >> 23 October, 2009 >> 4. Technical Description >> 1.0 Introduction >> 1.1 Project/Component Working Name: >> Python lxml >> >> 1.2 Purpose >> >> This project delivers the Python lxml bindings for Python 2.4 >> and Python 2.6. >> >> Release binding: Patch >> >> 2.0 Project Description >> >> lxml is a Pythonic binding for the libxml2 and libxslt libraries. >> It is unique in that it combines the speed and feature >> completeness of these libraries with the simplicity of a native >> Python API, mostly compatible but superior to the well-known >> ElementTree API. The default Python bindings of libxml2 are fast, >> thrilling, powerful, and your code might fail in some horrible way >> that you really shouldn't have to worry about when writing Python >> code. lxml combines the power of libxml2 with the ease of use of >> Python. >> >> This project is maintained within the Code Speak project. As such >> the project team will follow the community >> (http://codespeak.net/lxml) >> for bug fixes. >> >> The project will initially ship with Python 2.4 bindings as well as >> Python 2.6 bindings. Once the install code is ported to Python >> 2.6 then install will rely upon the Python 2.6 bindings. The port of >> install to Python 2.6 is underway. >> >> 2.1 Exported Interface table >> Interface Classification Comments >> ----------------------------------- --------------- --------------- >> SUNWpython-lxml Uncommitted SVr4 pkg for >> Python 2.4 bits >> SUNWpython26-lxml Uncommitted SVr4 pkg for >> Python 2.6 bits >> python2.[46]/vendor-packages/lxml Uncommitted Python binding >> install >> location >> ElementTree API Volatile [4] >> lxml.etree API Volatile [5] >> lxml.objectify API Volatile [6] >> >> * Note: The Python 2.4 bindings are Obsolete Volatile to match the >> Python 2.6 and 3.0 case (PSARC 2009/043) >> >> 2.2 Imported Interface table >> Interface Classification Comments >> ----------------------------------- --------------- --------------- >> /usr/bin/python2.4 Obsolete PSARC 2009/043 >> /usr/bin/python2.6 Uncommitted PSARC 2009/043 >> >> ====================== >> 3. Reference Documents >> ====================== >> [1] lxml website http://codespeak.net/lxml -- only for reference >> [2] materials/prototype2.[46] >> [3] materials/pkginfo2.[46] >> [4] materials/element.htm -- ElementTree API >> [5] materials/lxml.etree-api.html -- lxml.etree API >> [6] materials/lxml.objectify-api.html -- lxml.objectify API >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> SFW >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> _______________________________________________ >> opensolaris-arc mailing list >> opensolaris-arc@opensolaris.org > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From glenn.skinner@sun.com Fri Oct 30 12:28:19 2009 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 n9UJSIdZ014738 for ; Fri, 30 Oct 2009 12:28:19 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n9UJS9JR007579 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 30 Oct 2009 19:28:17 GMT 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 <0KSC00F13E358P00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 12:28:17 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSC00DQGE34I310@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 12:28:17 -0700 (PDT) Received: from ivrel.sfbay.sun.com (ivrel.SFBay.Sun.COM [129.146.74.76]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9UJSGYN017050; Fri, 30 Oct 2009 12:28:16 -0700 (PDT) Received: from ivrel (ivrel [129.146.74.76]) by ivrel.sfbay.sun.com (8.14.3+Sun/8.14.3) with SMTP id n9UJKlB8006975; Fri, 30 Oct 2009 12:20:47 -0700 (PDT) Date: Fri, 30 Oct 2009 12:20:47 -0700 (PDT) From: Glenn Skinner Subject: Re: 2009/579 [Python lxml] To: PSARC-ext@sun.com, John.Fischer@sun.com Reply-to: Glenn Skinner Message-id: <200910301920.n9UJKlB8006975@ivrel.sfbay.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_36 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: T/rQhzphvz1dmbpOURiSug== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 1809 Date: Fri, 30 Oct 2009 11:59:03 -0700 From: John Fischer Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] To: PSARC-ext@sun.com Anyone care to +1 this fast track? Thanks for the prod. ... >> The project will initially ship with Python 2.4 bindings as >> well as Python 2.6 bindings. Once the install code is >> ported to Python 2.6 then install will rely upon the Python >> 2.6 bindings. The port of install to Python 2.6 is >> underway. >> >> 2.1 Exported Interface table >> Interface Classification Comments >> ----------------------------------- --------------- --------------- >> SUNWpython-lxml Uncommitted SVr4 pkg for >> Python 2.4 bits >> SUNWpython26-lxml Uncommitted SVr4 pkg for >> Python 2.6 bits >> python2.[46]/vendor-packages/lxml Uncommitted Python binding >> install >> location >> ElementTree API Volatile [4] >> lxml.etree API Volatile [5] >> lxml.objectify API Volatile [6] >> >> * Note: The Python 2.4 bindings are Obsolete Volatile to match the >> Python 2.6 and 3.0 case (PSARC 2009/043) Given that install intends to use this library (and thus its API), are Uncommitted and Volatile suitable stability levels? (In particular, will they deliver into the same consolidation?) -- Glenn From John.Fischer@sun.com Fri Oct 30 13:14:32 2009 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 n9UKEVFR016665 for ; Fri, 30 Oct 2009 13:14:32 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n9UKET3S030718 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 30 Oct 2009 14:14:31 -0600 (MDT) 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 <0KSC0080BG86TG00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 13:14:30 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSC00HW5G85ILE0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 13:14:30 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9UKETH8023754; Fri, 30 Oct 2009 20:14:29 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KSC00000G477700@mail-amer.sun.com>; Fri, 30 Oct 2009 14:14:29 -0600 (MDT) Received: from [192.168.0.102] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KSC00D9YG7XBVA0@mail-amer.sun.com>; Fri, 30 Oct 2009 14:14:22 -0600 (MDT) Date: Fri, 30 Oct 2009 13:11:28 -0700 From: John Fischer Subject: Re: 2009/579 [Python lxml] In-reply-to: <200910301920.n9UJKlB8006975@ivrel.sfbay.sun.com> Sender: John.Fischer@sun.com To: Glenn Skinner Cc: PSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4AEB4870.9050708@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910301920.n9UJKlB8006975@ivrel.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 2295 Glenn, This will be delivered through the SFW consolidation. The Install team is unsure which consolidation they will end up in. ON makes the most sense. With that all said, the Install team is the team delivering this into the SFW consolidation. Perhaps when the Install team uses the interface there should be a contract established. Would that be acceptable? Thanks, John Glenn Skinner wrote: > Date: Fri, 30 Oct 2009 11:59:03 -0700 > From: John Fischer > Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] > To: PSARC-ext@sun.com > > Anyone care to +1 this fast track? > > Thanks for the prod. > > ... > >> The project will initially ship with Python 2.4 bindings as > >> well as Python 2.6 bindings. Once the install code is > >> ported to Python 2.6 then install will rely upon the Python > >> 2.6 bindings. The port of install to Python 2.6 is > >> underway. > >> > >> 2.1 Exported Interface table > >> Interface Classification Comments > >> ----------------------------------- --------------- --------------- > >> SUNWpython-lxml Uncommitted SVr4 pkg for > >> Python 2.4 bits > >> SUNWpython26-lxml Uncommitted SVr4 pkg for > >> Python 2.6 bits > >> python2.[46]/vendor-packages/lxml Uncommitted Python binding > >> install > >> location > >> ElementTree API Volatile [4] > >> lxml.etree API Volatile [5] > >> lxml.objectify API Volatile [6] > >> > >> * Note: The Python 2.4 bindings are Obsolete Volatile to match the > >> Python 2.6 and 3.0 case (PSARC 2009/043) > > Given that install intends to use this library (and thus its API), are > Uncommitted and Volatile suitable stability levels? > > (In particular, will they deliver into the same consolidation?) > > -- Glenn > From glenn.skinner@sun.com Fri Oct 30 13:35:39 2009 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 n9UKZc5X017632 for ; Fri, 30 Oct 2009 13:35:39 -0700 (PDT) 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 n9UKZYFe008872 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 31 Oct 2009 04:35:37 +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 <0KSC00905H7CGT00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 14:35:36 -0600 (MDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSC008COH7B2I00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 30 Oct 2009 14:35:35 -0600 (MDT) Received: from ivrel.sfbay.sun.com (ivrel.SFBay.Sun.COM [129.146.74.76]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n9UKZZKo027057; Fri, 30 Oct 2009 13:35:35 -0700 (PDT) Received: from ivrel (ivrel [129.146.74.76]) by ivrel.sfbay.sun.com (8.14.3+Sun/8.14.3) with SMTP id n9UKS54a007027; Fri, 30 Oct 2009 13:28:05 -0700 (PDT) Date: Fri, 30 Oct 2009 13:28:05 -0700 (PDT) From: Glenn Skinner Subject: Re: 2009/579 [Python lxml] To: John.Fischer@sun.com Cc: PSARC-ext@sun.com Reply-to: Glenn Skinner Message-id: <200910302028.n9UKS54a007027@ivrel.sfbay.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_36 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: FxptpiTLRmu0KBJWL1k4Vw== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3338 Date: Fri, 30 Oct 2009 13:11:28 -0700 From: John Fischer Subject: Re: 2009/579 [Python lxml] This will be delivered through the SFW consolidation. The Install team is unsure which consolidation they will end up in. ON makes the most sense. With that all said, the Install team is the team delivering this into the SFW consolidation. Perhaps when the Install team uses the interface there should be a contract established. Would that be acceptable? I was hoping that the Python lxml library has had a history of evolving without incompatible changes, so that Committed would be a reasonable choice of stability in practice. (E.g., are the APIs really likely to change incompatibly? If they have a moderately large user base, that would seem to be an unlikely event.) (I'm also not sure what it means to have an Uncommitted library delivering implementations of Volatile APIs. In the interface table below, does Uncommitted refer merely to the package name and library location or does it apply to the library's contents as well?) But if all parties accept these stability levels with their eyes open, I won't stand in the way. So +1, but I still hope to see the proposal modified to bump the stability levels. -- Glenn Glenn Skinner wrote: > Date: Fri, 30 Oct 2009 11:59:03 -0700 > From: John Fischer > Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] > To: PSARC-ext@sun.com > > Anyone care to +1 this fast track? > > Thanks for the prod. > > ... > >> The project will initially ship with Python 2.4 bindings as > >> well as Python 2.6 bindings. Once the install code is > >> ported to Python 2.6 then install will rely upon the Python > >> 2.6 bindings. The port of install to Python 2.6 is > >> underway. > >> > >> 2.1 Exported Interface table > >> Interface Classification Comments > >> ----------------------------------- --------------- --------------- > >> SUNWpython-lxml Uncommitted SVr4 pkg for > >> Python 2.4 bits > >> SUNWpython26-lxml Uncommitted SVr4 pkg for > >> Python 2.6 bits > >> python2.[46]/vendor-packages/lxml Uncommitted Python binding > >> install > >> location > >> ElementTree API Volatile [4] > >> lxml.etree API Volatile [5] > >> lxml.objectify API Volatile [6] > >> > >> * Note: The Python 2.4 bindings are Obsolete Volatile to match the > >> Python 2.6 and 3.0 case (PSARC 2009/043) > > Given that install intends to use this library (and thus its API), are > Uncommitted and Volatile suitable stability levels? > > (In particular, will they deliver into the same consolidation?) From Mark.Carlson@sun.com Sat Oct 31 15:56:02 2009 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 n9VMu1iU014135 for ; Sat, 31 Oct 2009 15:56:02 -0700 (PDT) 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 n9VMu0rh001052 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sat, 31 Oct 2009 22:56:01 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 <0KSE00703IDCT400@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 31 Oct 2009 15:56:00 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSE004UAIDBDZ90@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 31 Oct 2009 15:55:59 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n9VMtx2M025633 for ; Sat, 31 Oct 2009 22:55:59 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KSE00100I1R4T00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 31 Oct 2009 16:55:59 -0600 (MDT) Received: from Macintosh-335.local ([unknown] [88.79.237.14]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KSE000IWID8EE90@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sat, 31 Oct 2009 16:55:59 -0600 (MDT) Date: Sat, 31 Oct 2009 16:55:56 -0600 From: "Mark A. Carlson" Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] In-reply-to: <4AEB3777.5020008@sun.com> Sender: Mark.Carlson@sun.com To: John.Fischer@sun.com Cc: PSARC-ext@sun.com Message-id: <4AECC07C.4020804@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_yXOvBbcRYuPF5rhOEFEBlw)" X-PMX-Version: 5.4.1.325704 References: <200910231907.n9NJ7QBC027367@sac.sfbay.sun.com> <4AE9D148.9070201@sun.com> <4AEB3777.5020008@sun.com> User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Status: RO Content-Length: 14774 This is a multi-part message in MIME format. --Boundary_(ID_yXOvBbcRYuPF5rhOEFEBlw) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT I've reviewed the case and have no issues. +1 -- mark John Fischer wrote: > Anyone care to +1 this fast track? > > Thanks, > > John > > > John Fischer wrote: >> All, >> >> Tomorrow is the timeout for this case. I have addressed John Levon's >> question about 32-bit and 64-bit versions of the .so files. Any other >> issues welcome. >> >> Thanks, >> >> John >> >> >> John Fischer wrote: >>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> Python lxml >>> 1.2. Name of Document Author/Supplier: >>> Author: John Fischer >>> 1.3 Date of This Document: >>> 23 October, 2009 >>> 4. Technical Description >>> 1.0 Introduction >>> 1.1 Project/Component Working Name: >>> Python lxml >>> >>> 1.2 Purpose >>> >>> This project delivers the Python lxml bindings for Python 2.4 >>> and Python 2.6. >>> >>> Release binding: Patch >>> >>> 2.0 Project Description >>> >>> lxml is a Pythonic binding for the libxml2 and libxslt >>> libraries. It is unique in that it combines the speed and >>> feature completeness of these libraries with the simplicity of a >>> native Python API, mostly compatible but superior to the >>> well-known ElementTree API. The default Python bindings of >>> libxml2 are fast, thrilling, powerful, and your code might fail >>> in some horrible way that you really shouldn't have to worry >>> about when writing Python code. lxml combines the power of >>> libxml2 with the ease of use of Python. >>> >>> This project is maintained within the Code Speak project. As such >>> the project team will follow the community >>> (http://codespeak.net/lxml) >>> for bug fixes. >>> >>> The project will initially ship with Python 2.4 bindings as well as >>> Python 2.6 bindings. Once the install code is ported to Python >>> 2.6 then install will rely upon the Python 2.6 bindings. The >>> port of >>> install to Python 2.6 is underway. >>> 2.1 Exported Interface table >>> Interface Classification Comments >>> ----------------------------------- --------------- --------------- >>> SUNWpython-lxml Uncommitted SVr4 pkg for >>> Python 2.4 bits >>> SUNWpython26-lxml Uncommitted SVr4 pkg for >>> Python 2.6 bits >>> python2.[46]/vendor-packages/lxml Uncommitted Python >>> binding >>> install >>> location >>> ElementTree API Volatile [4] >>> lxml.etree API Volatile [5] >>> lxml.objectify API Volatile [6] >>> >>> * Note: The Python 2.4 bindings are Obsolete Volatile to match the >>> Python 2.6 and 3.0 case (PSARC 2009/043) >>> >>> 2.2 Imported Interface table >>> Interface Classification Comments >>> ----------------------------------- --------------- --------------- >>> /usr/bin/python2.4 Obsolete PSARC 2009/043 >>> /usr/bin/python2.6 Uncommitted PSARC 2009/043 >>> >>> ====================== >>> 3. Reference Documents >>> ====================== >>> [1] lxml website http://codespeak.net/lxml -- only for reference >>> [2] materials/prototype2.[46] >>> [3] materials/pkginfo2.[46] >>> [4] materials/element.htm -- ElementTree API >>> [5] materials/lxml.etree-api.html -- lxml.etree API >>> [6] materials/lxml.objectify-api.html -- lxml.objectify API >>> >>> >>> 6. Resources and Schedule >>> 6.4. Steering Committee requested information >>> 6.4.1. Consolidation C-team Name: >>> SFW >>> 6.5. ARC review type: FastTrack >>> 6.6. ARC Exposure: open >>> >>> _______________________________________________ >>> opensolaris-arc mailing list >>> opensolaris-arc@opensolaris.org >> _______________________________________________ >> opensolaris-arc mailing list >> opensolaris-arc@opensolaris.org > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org -- * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson@Sun.COM --Boundary_(ID_yXOvBbcRYuPF5rhOEFEBlw) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT I've reviewed the case and have no issues.

+1

-- mark

John Fischer wrote:
Anyone care to +1 this fast track?

Thanks,

John


John Fischer wrote:
All,

Tomorrow is the timeout for this case.  I have addressed John Levon's
question about 32-bit and 64-bit versions of the .so files.  Any other
issues welcome.

Thanks,

John


John Fischer wrote:
Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     Python lxml
    1.2. Name of Document Author/Supplier:
     Author:  John Fischer
    1.3  Date of This Document:
    23 October, 2009
4. Technical Description
1.0 Introduction
1.1 Project/Component Working Name:
        Python lxml

1.2 Purpose

    This project delivers the Python lxml bindings for Python 2.4
    and Python 2.6.

    Release binding: Patch

2.0 Project Description

    lxml is a Pythonic binding for the libxml2 and libxslt libraries.     It is unique in that it combines the speed and feature completeness     of these libraries with the simplicity of a native Python API,     mostly compatible but superior to the well-known ElementTree API.      The default Python bindings of libxml2 are fast, thrilling, powerful,     and your code might fail in some horrible way that you really     shouldn't have to worry about when writing Python code. lxml combines     the power of libxml2 with the ease of use of Python.

    This project is maintained within the Code Speak project.  As such
    the project team will follow the community (http://codespeak.net/lxml)
    for bug fixes.

    The project will initially ship with Python 2.4 bindings as well as
    Python 2.6 bindings.  Once the install code is ported to Python 2.6     then install will rely upon the Python 2.6 bindings.  The port of
    install to Python 2.6 is underway.
    2.1 Exported Interface table
    Interface                Classification    Comments
    ----------------------------------- --------------- ---------------
    SUNWpython-lxml                     Uncommitted     SVr4 pkg for
                                                        Python 2.4 bits
    SUNWpython26-lxml                   Uncommitted     SVr4 pkg for
                                                        Python 2.6 bits
    python2.[46]/vendor-packages/lxml   Uncommitted     Python binding                                                         install                                                         location
    ElementTree API                     Volatile        [4]
    lxml.etree API                      Volatile        [5]
    lxml.objectify API                  Volatile        [6]

    * Note: The Python 2.4 bindings are Obsolete Volatile to match the
        Python 2.6 and 3.0 case (PSARC 2009/043)

2.2 Imported Interface table
    Interface                Classification    Comments
    ----------------------------------- --------------- ---------------
    /usr/bin/python2.4                  Obsolete        PSARC 2009/043
    /usr/bin/python2.6                  Uncommitted     PSARC 2009/043

======================
3. Reference Documents
======================
    [1] lxml website http://codespeak.net/lxml -- only for reference
    [2] materials/prototype2.[46]
    [3] materials/pkginfo2.[46]
    [4] materials/element.htm -- ElementTree API
    [5] materials/lxml.etree-api.html -- lxml.etree API
    [6] materials/lxml.objectify-api.html -- lxml.objectify API


6. Resources and Schedule
    6.4. Steering Committee requested information
       6.4.1. Consolidation C-team Name:
        SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open

_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org

--
Mark A. Carlson
Sr. Architect

Systems Group
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM

--Boundary_(ID_yXOvBbcRYuPF5rhOEFEBlw)-- From John.Fischer@sun.com Tue Nov 3 16:50:03 2009 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 nA40o2j7005342 for ; Tue, 3 Nov 2009 16:50:02 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id nA40o0ko029046 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 4 Nov 2009 08:50:01 +0800 (SGT) 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 <0KSK00K037NCH000@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 03 Nov 2009 16:50:00 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KSK008JL7NC58B0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 03 Nov 2009 16:50:00 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nA40nxfk007122; Wed, 04 Nov 2009 00:49:59 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KSK003007G6S800@mail-amer.sun.com>; Tue, 03 Nov 2009 17:49:59 -0700 (MST) Received: from [192.168.10.4] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KSK007W87NAEZD0@mail-amer.sun.com>; Tue, 03 Nov 2009 17:49:59 -0700 (MST) Date: Tue, 03 Nov 2009 16:47:02 -0800 From: John Fischer Subject: Re: 2009/579 [Python lxml] In-reply-to: <200910302028.n9UKS54a007027@ivrel.sfbay.sun.com> Sender: John.Fischer@sun.com To: Glenn Skinner Cc: PSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4AF0CF06.5030307@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200910302028.n9UKS54a007027@ivrel.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091013) Status: RO Content-Length: 4157 Glenn, Thanks for the +1. I understand the desire for a higher classification. I will monitor the community and respond appropriately when I see the interface evolution slowing down. I noticed that there were several deprecated interfaces between lxml 2.0 and lxml 2.1 as well as function name changes between major versions. Because of these facts I am not yet comfortable with declaring a higher commitment level. Again, I will monitor the community for the group and the ARC. You are correct that the Uncommitted interfaces refer to only the package names and directory locations. With that I am marking the case closed approved. Thanks, John Glenn Skinner wrote: > Date: Fri, 30 Oct 2009 13:11:28 -0700 > From: John Fischer > Subject: Re: 2009/579 [Python lxml] > > This will be delivered through the SFW consolidation. The Install team > is unsure which consolidation they will end up in. ON makes the most > sense. With that all said, the Install team is the team delivering this > into the SFW consolidation. > > Perhaps when the Install team uses the interface there should be a > contract established. Would that be acceptable? > > I was hoping that the Python lxml library has had a history of > evolving without incompatible changes, so that Committed would be a > reasonable choice of stability in practice. (E.g., are the APIs > really likely to change incompatibly? If they have a moderately large > user base, that would seem to be an unlikely event.) > > (I'm also not sure what it means to have an Uncommitted library > delivering implementations of Volatile APIs. In the interface table > below, does Uncommitted refer merely to the package name and library > location or does it apply to the library's contents as well?) > > But if all parties accept these stability levels with their eyes open, > I won't stand in the way. > > So +1, but I still hope to see the proposal modified to bump the > stability levels. > > -- Glenn > > Glenn Skinner wrote: > > Date: Fri, 30 Oct 2009 11:59:03 -0700 > > From: John Fischer > > Subject: Re: Python lxml [PSARC/2009/579 FastTrack timeout 10/30/2009] > > To: PSARC-ext@sun.com > > > > Anyone care to +1 this fast track? > > > > Thanks for the prod. > > > > ... > > >> The project will initially ship with Python 2.4 bindings as > > >> well as Python 2.6 bindings. Once the install code is > > >> ported to Python 2.6 then install will rely upon the Python > > >> 2.6 bindings. The port of install to Python 2.6 is > > >> underway. > > >> > > >> 2.1 Exported Interface table > > >> Interface Classification Comments > > >> ----------------------------------- --------------- --------------- > > >> SUNWpython-lxml Uncommitted SVr4 pkg for > > >> Python 2.4 bits > > >> SUNWpython26-lxml Uncommitted SVr4 pkg for > > >> Python 2.6 bits > > >> python2.[46]/vendor-packages/lxml Uncommitted Python binding > > >> install > > >> location > > >> ElementTree API Volatile [4] > > >> lxml.etree API Volatile [5] > > >> lxml.objectify API Volatile [6] > > >> > > >> * Note: The Python 2.4 bindings are Obsolete Volatile to match the > > >> Python 2.6 and 3.0 case (PSARC 2009/043) > > > > Given that install intends to use this library (and thus its API), are > > Uncommitted and Volatile suitable stability levels? > > > > (In particular, will they deliver into the same consolidation?) >