Closed dfornika closed 1 month ago
I've found an alternative solution for this issue, which would just involve pinning setuptools=69
in our environment.yml file. That would be a more conservative change and wouldn't require extensive comparisons to other FluViewer outputs so we should do that before seriously considering updating spades to the v4 series.
We're experiencing some issues related to come sort of incompatibility between python
setuptools
andspades
, for the versions of those components that are being installed in our FluViewer environment in our BCCDC-PHL/fluviewer-nf pipeline:One possible solution could be to use spades v4.0.0 which is the latest release. But if we want to pursue that we should evaluate whether the assemblies produced by that version of spades are equivalent to the ones produced by spades v3.15.3, the version currently tagged in our environment.yml file:
https://github.com/BCCDC-PHL/FluViewer/blob/455ae76207a30b00a0997140f85d406b2854f592/environment.yaml#L12