-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
MNT: Remove uproot-base build ouptut #158
MNT: Remove uproot-base build ouptut #158
Conversation
@conda-forge-admin, please rerender |
For recipe/meta.yaml:
|
@conda-forge-admin, please rerender |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
* As of v5.4.0 the requirements of the uproot-base and uproot build outputs are identical. This removes the need for uproot-base and the feedstock can now produce just the uproot build output. * Rerender the meta.yaml using 'grayskull pypi uproot' * Use the stable docs URL. * Bump the build number.
a8ea086
to
39b6473
Compare
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.10.01.17.37.14
@jpivarski @conda-forge/scikit-hep this is ready for review now. |
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.
It looks good to me, and I'm in favor of replacing the uproot-base
+ uproot
combination with just uproot
.
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/{{ name }}-{{ version }}.tar.gz | ||
url: https://pypi.org/packages/source/{{ name[0] }}/{{ name }}/uproot-{{ version }}.tar.gz |
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.
I understand that there's only one package now, but why should uproot
be hard-coded?
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.
@jpivarski This is the behavior of grayskull
(c.f. https://github.com/conda/grayskull/blob/3402aa08db001d43bbed6a3f0d340e0f0183a715/grayskull/strategy/pypi.py#L126-L143). I wondered the same thing, but I haven't bothered to ask on https://github.com/conda/grayskull.
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.
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.
I'm going to merge this in, but if there's some answer from the grayskull
team that makes us think we should change from what they do then we can open a fix PR.
v5.4.0
the requirements of theuproot-base
anduproot
build outputs are identical. This removes the need foruproot-base
and the feedstock can now produce just theuproot
build output.meta.yaml
usinggrayskull pypi uproot
.Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)