Teach OpenSRF how to install and configure Python in a friendly manner
Bug #669469 reported by
Dan Scott
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenSRF |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
This might be a meta-bug, but Michael Giarlo's recent experience getting OpenSRF Python running for a Python-based service showed that some rough edges need to be filed off OpenSRF Python. Specifically:
* install opensrf.py in BINDIR (perhaps under a different name like opensrf-python.py to match opensrf-perl.pl?)
* set default directories in opensrf.py based on autoconf vars
* remove the requirement of the -p flag for opensrf.py
* deal with parsing comments in opensrf.xml / opensrf_core.xml
* teach osrf_ctl.sh to handle Python-based services
* include osrf/apps/
* more docs
To post a comment you must log in.
We've made a lot of progress!
* http:// svn.open- ils.org/ trac/OpenSRF/ changeset/ 2055, opensrf.py is now installed in BINDIR and osrf_ctl.sh is aware of Python-based services
* http:// svn.open- ils.org/ trac/OpenSRF/ changeset/ 2054, comments in opensrf.xml no longer disturb opensrf.py
* http:// svn.open- ils.org/ trac/OpenSRF/ changeset/ 2067, opensrf.py now has reasonable defaults (defined by autoconf) for the -p and -f flags.
* http:// svn.open- ils.org/ trac/OpenSRF/ changeset/ 2053, osrf/apps/ example. py is now installed