-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Add pgscatalog.core #48453
Add pgscatalog.core #48453
Conversation
@BiocondaBot please add label |
@BiocondaBot please fetch artifacts |
Package(s) built are ready for inspection:
Docker image(s) built:
|
recipes/pgscatalog.core/meta.yaml
Outdated
|
||
requirements: | ||
host: | ||
- python >=3.11,<4.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK support for Python 3.11 & 3.12 is available only in the bulk
branch for now.
In master
branch the available Python versions are 3.8, 3.9 and 3.10.
I wonder how this worked here.
The logs show that Python 3.12 has been installed - python: 3.12.3-hab00c5b_0_cpython
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I've downgraded the minimum version to 3.10 in a patch release (pgscatalog-core 0.2.1)
When I check the new logs and artifacts they're being built with 3.12 still - will the latest commit be OK to merge or do I have to put an upper limit on the python version range?
@BiocondaBot please fetch artifacts |
Package(s) built are ready for inspection:
Docker image(s) built:
|
@nebfield Support for 3.11 & 3.12 is really close - #33333 (comment) |
I still don't understand why/how it uses 3.12 for the build in |
Add pgscatalog.core, a python package which contains core tools for working with polygenic scores (PGS) and the PGS Catalog