Mercurial > repos > jankanis > package_python3_4
changeset 17:d30e6a97dfbf draft default tip
add dependency on zlib
| author | jankanis |
|---|---|
| date | Wed, 28 May 2014 10:44:03 -0400 |
| parents | 7719329e5b98 |
| children | |
| files | tool_dependencies.xml |
| diffstat | 1 files changed, 55 insertions(+), 24 deletions(-) [+] |
line wrap: on
line diff
--- a/tool_dependencies.xml Wed May 28 05:28:22 2014 -0400 +++ b/tool_dependencies.xml Wed May 28 10:44:03 2014 -0400 @@ -4,6 +4,10 @@ <repository changeset_revision="3b19041c651c" name="package_openssl_1_0" owner="iuc" prior_installation_required="True" toolshed="http://toolshed.g2.bx.psu.edu" /> </package> + <package name="zlib" version="1.2.8"> + <repository changeset_revision="31f1e69aae89" name="package_zlib_1_2_8" owner="iuc" prior_installation_required="True" toolshed="http://toolshed.g2.bx.psu.edu" /> + </package> + <package name="sqlite" version="3.8.3"> <repository changeset_revision="706b1f3b1fc0" name="package_sqlite_3_8_3" owner="iuc" prior_installation_required="True" toolshed="http://toolshed.g2.bx.psu.edu" /> </package> @@ -19,6 +23,9 @@ <action type="download_by_url">https://www.python.org/ftp/python/3.4.1/Python-3.4.1.tgz</action> <action type="set_environment_for_install"> + <repository changeset_revision="31f1e69aae89" name="package_zlib_1_2_8" owner="iuc" toolshed="http://toolshed.g2.bx.psu.edu"> + <package name="zlib" version="1.2.8" /> + </repository> <repository changeset_revision="3b19041c651c" name="package_openssl_1_0" owner="iuc" toolshed="http://toolshed.g2.bx.psu.edu"> <package name="openssl" version="1.0.1g" /> </repository> @@ -61,8 +68,8 @@ <action type="set_environment"> <environment_variable action="prepend_to" name="PATH">$INSTALL_DIR/bin</environment_variable> - <environment_variable action="prepend_to" name="LD_LIBRARY_PATH">$ENV[LD_LIBRARY_PATH]</environment_variable> - <!-- empty PYTHONPATH, otherwise we will get Galaxy's Python 2 libraries in the Python 3 path --> + <environment_variable action="prepend_to" name="LD_LIBRARY_PATH">$ENV[LD_LIBRARY_PATH]</environment_variable> + <!-- clear PYTHONPATH, otherwise we will get Galaxy's Python 2 libraries in the Python 3 path. --> <environment_variable action="set_to" name="PYTHONPATH" /> <environment_variable action="set_to" name="PYTHONHOME">$INSTALL_DIR</environment_variable> <environment_variable action="prepend_to" name="PKG_CONFIG_PATH">$INSTALL_DIR/lib/pkgconfig</environment_variable> @@ -80,41 +87,65 @@ This build of python is configured with --enable-loadable-sqlite-extensions, any other settings are default. This build does not include modules for lzma and Tkinter, but does include ssl, (g)dbm and sqlite. Adding the missing modules should not be very difficult but requires wrapping the external sources that these modules require inside galaxy. - Python as of version 3.3 includes a built-in virtual environment manager. To create a python 3 virtual env, include the following actions in your tool_dependencies.xml: + Python as of version 3.3 includes a built-in virtual environment manager. To create a python 3 virtual env, include the following actions in your tool_dependencies.xml, e.g. for a package MY_TOOL_venv: <action type="set_environment_for_install"> <repository name="python3" owner="jankanis"> <package name="python3" version="3.4.1" /> </repository> - <!-- other install time dependencies --> + <!-- other install time dependencies --> </action> <action type="shell_command"> - # Unset any saved environment settings from parent virtual - # environments, e.g. for python 2 or if Galaxy itself is running - # from within a virtual environment. - unset _OLD_VIRTUAL_PATH; unset _OLD_VIRTUAL_PYTHONHOME - # Create virtual environment MY_TOOL_venv - pyvenv MY_TOOL_venv - # install python packages - MY_TOOL_venv/bin/pip3 install {{NEEDED_PYTHON_PACKAGES}} + # Unset any saved environment settings from parent virtual + # environments, e.g. for python 2 or if Galaxy itself is running + # from within a virtual environment. + unset _OLD_VIRTUAL_PATH; unset _OLD_VIRTUAL_PYTHONHOME + # Create virtual environment MY_TOOL_venv + pyvenv MY_TOOL_venv + # install python packages + MY_TOOL_venv/bin/pip3 install {{NEEDED_PYTHON_PACKAGES}} </action> <action type="set_environment"> - <!-- Remove any incoming PYTHONPATH elements from Galaxy's own python 2 environment, - but include an existing install time PYTHONPATH (e.g. from other python3 virtual - environments in the dependency hierarchy. --> - <environment_variable name="PYTHONPATH" action="set_to">$INSTALL_DIR/MY_TOOL_venv/lib/python3.4/site-packages:$ENV[PYTHONPATH]</environment_variable> - <!-- All that is really needed to use a specific virtual environment is that the - python interpreter in that environment is used, so add it to PATH --> - <environment_variable name="PATH" action="prepend_to">$INSTALL_DIR/MY_TOOL_venv/bin</environment_variable> - <!-- Clear incoming PYTHONHOME just like the venv's 'activate' command does --> - <environment_variable name="PYTHONHOME" action="set_to"></environment_variable> - <!-- To find shared libraries for python built-in modules such as libssl or libsqlite3 - we need to re-export LD_LIBRARY_PATH --> - <environment_variable name="LD_LIBRARY_PATH" action="prepend_to">$ENV[LD_LIBRARY_PATH]</environment_variable> + + <!-- Setting the PYTHONPATH correctly can be a bit tricky, because you must + make sure that the runtime PYTHONPATH from galaxy itself is not + included, as it probably points to python 2 code that can crash a + program if python 3 tries to load it. + + If you only use a single virtual environment that is created + specifically for a tool you are creating, you can just use a set_to + like below. + + If you create a virtual environment installation that is meant to be + reused by other packages, the virtual environment should probably + prepend its site-packages to the PYTHONPATH since a tool could be + using python modules from several virtual environments. But in such a + scenario the tool that uses these virtual environments should also + depend directly on the python3 package, and this dependency should be + listed before any virtual environment dependencies. This ensures that + the python3 environment settings that clear PYTHONPATH are sourced + first so galaxy's runtime PYTHONPATH is excluded. Virtual environments + can then prepend their PYTHONPATHs to each other. --> + <environment_variable name="PYTHONPATH" action="set_to">$INSTALL_DIR/MY_TOOL_venv/lib/python3.4/site-packages</environment_variable> + <!-- All that is really needed to use a specific virtual environment is that the + python interpreter in that environment is used, so add it to PATH --> + <environment_variable name="PATH" action="prepend_to">$INSTALL_DIR/MY_TOOL_venv/bin</environment_variable> + <!-- Clear incoming PYTHONHOME just like the venv's 'activate' command does --> + <environment_variable name="PYTHONHOME" action="set_to"></environment_variable> + <!-- To find shared libraries for python built-in modules such as libssl or libsqlite3 + we need to re-export LD_LIBRARY_PATH --> + <environment_variable name="LD_LIBRARY_PATH" action="prepend_to">$ENV[LD_LIBRARY_PATH]</environment_variable> </action> + + Then, in your MY_TOOL.xml add the following requirement: + + <requirements> + <requirement name="package" version="XXX">MY_TOOL_venv</requirement> + </requirements> + </readme> </package>