Ticket #300 (closed task: fixed)

Opened 15 years ago

Last modified 13 years ago

Create definitive python installation procedure and apply to glue

Reported by: anonymous Owned by: spascoe
Priority: desirable Milestone: PROD Step2
Component: T13_Data_Provider Version:
Keywords: Cc:

Description (last modified by spascoe) (diff)

Glue has several versions of Python installed on it with differing configurations. We should commit a build system to svn that will build python with all the necessary dependencies and configuration options needed by NDG.

This system can then be applied to glue to create a new definitive python installation. The build system can be updated to include dependencies so that consistent python installations can be created on other data providers.

Known dependencies that will have to be included:

  1. Most of CDAT's (cdms, vcs, cdunif_pp) could be included using the  mini-install script but will need extending to include vcs.
  2. ZSI 1.6.0 + NDG patch
  3. cElementTree 1.0.2
  4. ElementTree 1.2.6
  5. libxml2-python 2.6.15
  6. pyXMLSec 0.2.1
  7. SQLObject 0.6.1
  8. Numeric
  9. Scientific

Please add dependencies here.

Change History

comment:1 Changed 15 years ago by spascoe

  • Status changed from new to assigned

comment:2 Changed 15 years ago by domlowe

  • Description modified (diff)
  • Reporter spascoe deleted

comment:3 Changed 15 years ago by spascoe

  • Description modified (diff)

Added more dependent packages.

comment:4 Changed 15 years ago by spascoe

  • Description modified (diff)
  • Milestone changed from ALPHA to BETA

An installer for Python 2.4.3 plus SOME of the dependencies has been placed at TI13-DataProvider/trunk/python_installer. Those dependencies that are not trivially installable via the setuputils package management system are not included.

The scope of this ticket has changed because the DeliveryService will no longer require embedding python in bbftp, thus any Python 2.4 distribution can be used for development. Therefore I'm resheduling the ticket to BETA and we should probably discuss how to progress on a standard Python distribution.

comment:5 Changed 14 years ago by spascoe

  • Milestone changed from BETA to PROD Step2

comment:6 Changed 13 years ago by spascoe

  • Status changed from assigned to closed
  • Resolution set to fixed

The PythonEggs system mainly solves this problem, although some dependencies are still managed manually.

Note: See TracTickets for help on using tickets.