Task #10649 (closed)
Opened 11 years ago
Closed 9 years ago
Ensure PyCHRM and pychrm-omero are installable or in PYTHONPATH
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | critical | Milestone: | Partner-1 |
| Component: | Scripting | Version: | 4.4.9 |
| Keywords: | n.a. | Cc: | analysis@…, sbesson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description
At the moment the omero-pychrm scripts hard-code the paths to the built PyChrm? module and the utils directory.
PyChrm? should be installable as a python module so pip install -e pychrm-svn-repo may work but needs to be tested.
As for omero-pychrm/utils maybe they should be packaged as another module? Or made part of PyChrm?, or a fork? They're not suitable for including as part of the main OMERO distribution.
Finally omero-pychrm/scripts needs to be installed to the omero sripts directory.
Change History (11)
comment:1 Changed 11 years ago by jamoore
- Cc sbesson added
comment:2 Changed 11 years ago by spli
I'll give the pip packaging a go.
For lib/scripts would an an installation script that runs omero.sh script upload XXX.py --official be easier?
comment:3 Changed 11 years ago by jamoore
If you think that the installation will happen on a machine other than localhost (of the server), then that would definitely work. If you are on localhost, then you can just copy the files in. The trick will be, that on upgrade, those files will no longer be present. The use of the submodule will keep them persistent, as will putting lib/scripts somewhere "safe" and symlinking.
comment:4 Changed 11 years ago by spli
- Sprint set to 2013-04-09 (7))
- Status changed from new to accepted
comment:5 Changed 11 years ago by jburel
- Sprint changed from 2013-04-09 (7)) to 2013-05-07 (8)
Moved from sprint 2013-04-09 (7))
comment:6 Changed 11 years ago by spli
The following should compile and install pychrm, and similarly for the utility scripts in omero-pychrm.
pip install svn+http://wnd-charm.googlecode.com/svn/pychrm/trunk/@675#egg=pychrm pip install git+git://github.com/manics/omero-pychrm.git@cleanup_10583#egg=OmeroPychrm
The omero/scripts part is still to be handled, and needs some modifications to work with pychrm r675.
comment:7 Changed 11 years ago by jburel
- Sprint changed from 2013-05-07 (8) to Blocker 4.4.9 (1)
Moved from sprint 2013-05-07 (8)
comment:8 Changed 10 years ago by spli
Referencing ticket #9946 has changed sprint.
comment:9 Changed 10 years ago by jburel
Referencing ticket #9946 has changed sprint.
comment:10 Changed 10 years ago by spli
- Milestone changed from OMERO-4.4.x to Partner-1
- Version set to 4.4.9
comment:11 Changed 9 years ago by spli
- Remaining Time changed from 1 to 0
- Resolution set to invalid
- Status changed from accepted to closed
Will be handled in TRello if necessary.
Setting up a pip-installed package is quite easy, Simon, and pulls in dependencies recursively. So, I'd probably vote for pip install pychrm_omero (or whatever name) which brings in everything else.
cd lib/scripts && git pull ... should bring in the other scripts, but the question is will that be an easily updatable strategy for anyone who's moving from 4.4.a to 4.4.b.