Wolfgang Maier

on third thought one could allow unicode escapes in the tool interface text field and decode them on the python side. Then if your users are willing to type `Voil\xe0`...

That's an easy case then, but I think I already have a proper general solution ready. Going to open a PR soon.

Should be addressed in https://github.com/galaxyproject/tools-iuc/pull/4662 Thanks for checking the other tool. Might fix that too if I have a bit of spare time again.

Puh, quite useful new functionality, but needs some time to incorporate it all.

Thanks for making the wrapper autoupdate-compatible @bernt-matthias :)

Sure, no problem. The data in [mapped_data.zip](https://github.com/samtools/samtools/files/2636359/mapped_data.zip) is the relevant (for producing the reported output) snippet (chr1:248567000-248568000) from publicly available test data from the [Texas Cancer Research Biobank](http://txcrb.org/open.html) (sample TCRBOA6-N)....

Thanks for the investigation and the detailed explanation @valeriuo ! Glad that I could help.

Looks like dgidb-related functionality only requires a URL update to get it working again.

Sure, just need to get my laptop to look it up.

Ok, so you'd use: `dgidb_url = 'http://www.dgidb.org/api/v2/interactions.json?genes='` to re-enable things, at least, that's the minimal change. What I'd prefer though would be if URLs (the dgidb, the install-data url, others?)...