You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We at GenomeNext enjoy using Anaconda to help manage packages, however I have noticed during an attempt to upgrade some of our systems to Python3.7 that bam-readcount interferes with our upgrade process. It looks like it has been built for Python 3.5 and 3.6 but not 3.7, the new Anaconda standard deployment version. Maybe this could be a relatively easy update to make?
The text was updated successfully, but these errors were encountered:
Bam-readcount is still active, but we don't have a lot of bandwidth for support or maintenance at the moment. We didn't make the conda package for the software - looks like an end user did. Perhaps they'd be willing to update that code? bioconda/bioconda-recipes#4816
Bam-readcount is still active, but we don't have a lot of bandwidth for support or maintenance at the moment. We didn't make the conda package for the software - looks like an end user did. Perhaps they'd be willing to update that code? bioconda/bioconda-recipes#4816
The bioconda recipes is really quite simple to maintain, especially if you are a dev and know how to build your tool. I just discovered bam-count and now I'm not going to use it because it's not active on conda. So many people use conda for their env deps in projects, so you would only get a wider userbase by maintaining the recipe.
Hi,
We at GenomeNext enjoy using Anaconda to help manage packages, however I have noticed during an attempt to upgrade some of our systems to Python3.7 that bam-readcount interferes with our upgrade process. It looks like it has been built for Python 3.5 and 3.6 but not 3.7, the new Anaconda standard deployment version. Maybe this could be a relatively easy update to make?
The text was updated successfully, but these errors were encountered: