New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python package conflicts with crc32c #29
Comments
I guess one could argue that we should namespace the actual package as I haven't checked yet whether |
@dhermes might have some memory about considering use of the ICRAR version. |
The PR I just opened for GRMP pins to the existing version. If we are going to namespace this package, we would need to make a GRMP release with that new pin, then do the work and make a release here, then update GRMP to use the namespaced version and make a release. |
Prepare for upcoming version, which will namespace the module to avoid conflict with the ICRAR version. See: googleapis/python-crc32c#29
Avoids conflict with ICRAR version. Closes: #29
Prepare for upcoming version, which will namespace the module to avoid conflict with the ICRAR version. See: googleapis/python-crc32c#29
Avoid conflict with ICRAR version. Closes: #29
This package conflicts with the crc32c package, which is used in projects such as snakemake. This conflict means that older versions of Google client libraries need to be pinned in order to be able to install such packages. See: bioconda/bioconda-recipes#23799
The text was updated successfully, but these errors were encountered: