Conversation
|
Might need to create a new version tag with this pushed to bioconda? |
|
@ppreshant this would be a perfect place for a bioconda script patch that could probably be made by using here is the example that Bryce introduced to me earlier (and I applied for some of the first bioconda builds goofs): "To do this, you make whatever changes you want in your project's source, then pipe the git diff output between the commit you want to use and the commit that is tied to the release on bioconda. That diff file is a "patch" that you can add to the bioconda recipe. For example:" |
|
That's a good idea. Since there's some 7 commits, it might also be good + easier to release a new version tag
|
|
Yep, go ahead and do a release with |
- lemur's bioconda is not updated with latest patch. Discussion ongoing at [lemur/pull16](treangenlab/lemur#16)
When testing some of the Somatem scripts, we recently installed lemur from bioconda and the recent pandas update to v3.0.1 has created
ValueError: You are trying to merge on int64 and str columns for key 'Target_ID'in theEM_stepfunction.See error here (partial copy from Somatem nextflow.log script):
lemur_pandas_error.txt
To fix this, I made both
self.P_rgs_df.reset_index()andself.Fkeys into strings before merging.Tested and works as before!