Fabien Pertuy

Looks like @apeltzer was well inspired to test a rebuild, this issue may be solved with current PR. Could anyone help testing package indicated here: https://github.com/bioconda/bioconda-recipes/pull/15605#issuecomment-496219028. Just follow the instructions...

Thanks for reporting @tillea ! Can you give more information on the package (version, repo) for the record?

Just to mention, this could probably be solved using **explicit** relative imports for all the modules packed in `AlignQC`. ```python from __future__ import absolute_import # Not necessary for python 2.6+...

Hello @asarnow , can you tell me if there's any issue with using the conda-forge packages with `topaz`? I was thinking that the package could belong to Conda-forge/Bioconda organizations, and...

Here's the PR, I tested locally and the dependencies should dynamically change bewteen CPU and GPU depending on hardware availability. It's possible to force installing GPU version with [this trick](https://conda-forge.org/docs/user/tipsandtricks/#installing-cuda-enabled-packages-like-tensorflow-and-pytorch)....

Is the team supporting Windows install? It looks like the Windows build [finds a topaz.exe binary](https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1327214&view=logs&j=53c3d5f4-e7c7-5b53-4b94-211701b2ba17&t=8f042650-8479-5761-7a4a-8d021c0bb2de&l=2401), which doesn't comply with noarch packages. It is not clear where it comes from.

> Is the team supporting Windows install? It looks like the Windows build [finds a topaz.exe binary](https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1327214&view=logs&j=53c3d5f4-e7c7-5b53-4b94-211701b2ba17&t=8f042650-8479-5761-7a4a-8d021c0bb2de&l=2401), which doesn't comply with noarch packages. It is not clear where it comes...