in addition to version and build number. This is necessary for getting
the extended-base annotation for qiime 1.9.1, which does not contain the
annotation in linux-64/qiime-1.9.1-np110py27_1.tar.bz2 while in the
newer linux-64/qiime-1.9.1-np112py27_1.tar.bz2 it is present. This
depends of course on `conda search` returning packages sorted by upload
time and is a little brittle. It does seem better than always picking
the oldest upload time as we do without this change. Also looks in
meta.yaml for extended base annotation, since sometimes this isn't
present in info/about.json.
This is easier to use in planemo (we don't need to figure out which
image to use based on the return value of
any_target_requires_extended_base) and leaves open the possibility for
custom base image annotation in conda recipes or other places.
This will continue to work for single column files
or files that make use of the second and third column already
(build_number and name_override).
I don't think we should be using name_override,
but given the library nature and not knowing if anyone
except for biocontainers/multi-package-containers uses
this I chose to keep backwards compaitbility.
This does add support for meaningful column headers,
so we can write something like
```
\#base_image targets build_number
extended package 10
```
and not include name_override.
- enables docker destination for interactivetool tests
- fixes a wrong argument in entrypoint management
- fixes the test setup that targeted a previous iteration (which was
still called realtimetools)
- prevents deleting the working directory before python has a chance to
start the container monitor (that's the sleep command)
- fixes some odd interactive tool test assertions
- uses unicode arguments in key_type_token_mapping.py.
uwsgi arguments are always passed as bytestrings.
Broken in commit 7d3b9c53bb .
Before the above-mentioned commit, when a
`<param name="blah" type="select" multiple="true"/>` was left unselected,
its value was `None`, casted to string as `"None"`.
Tool authors would check if the user has selected a value with something
like:
```
#if str($blah) != 'None':
```
After the above-mentioned commit, the value of the unselected param is `[]`,
casted to string as `""`, which breaks tools using the check above.
This restores the previous behaviour.
Seen in pull request:
https://github.com/galaxyproject/tools-iuc/pull/2691
Dannon