Skip to content
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

Release 2021.11.0 with grayskull #28

Merged
merged 8 commits into from
Nov 11, 2021

Conversation

charlesbluca
Copy link
Member

@charlesbluca charlesbluca commented Nov 10, 2021

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

Closes #29

Main change we need here is the Dask pinning in the first commit, the rest is optional suggestions made when generating the recipe with grayskull.

cc @quasiben

@conda-forge-linter
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • requirements: run: dask==2021.10.0 must contain a space between the name and the pin, i.e. dask ==2021.10.0

number: 0
script: {{ PYTHON }} -m pip install . --no-deps -vv
skip: true # [py2k]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be added because of the selector below. So makes sense

@jakirkham
Copy link
Member

Would suggest taking the dependencies before and after and sorting them. Then doing a diff on those. That should help clarify what has actually changed. Also raised issue ( conda/grayskull#259 ) on keeping these in the original order

@conda-forge-linter
Copy link
Contributor

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 (recipe) and found it was in an excellent condition.

@charlesbluca
Copy link
Member Author

Resorted the dependencies here to match the original ordering to simplify the diff

- python >=3.6
- setuptools_scm
- python
- setuptools-scm
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be fine. We provide both - & _

Copy link
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Charles! 😄

Raised a few issues based on trying things here. Made a few observations above. Some are actionable. Though some are not.

- pandas >=1.0.0
- jpype1 >=1.0.2
- openjdk >=8
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Obviously we want to keep this. Raised issue ( conda/grayskull#261 )

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also want to keep the maven build requirement?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry missed that. Agree we want to keep that. Commented above

Comment on lines -34 to +37
- prompt_toolkit >=3.0.8
- pygments >=2.7.3
- nest-asyncio >=1.0.0
- tabulate >=0.8.9
- prompt-toolkit
- pygments
- nest-asyncio
- tabulate
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While it may seem surprising that these constraints were dropped, that did happen in the setup.py. So this is expected behavior (at least from Grayskull). Whether they should or shouldn't be there upstream is another question

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point - I notice that those packages are constrained by the CI environment so I can open an issue to keep track of making those consistent for the next release

- pygments
- nest-asyncio
- tabulate
- importlib-metadata # [py<38]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is picked up from upstream and expected. This is also why the package can no longer be noarch

recipe/meta.yaml Outdated

test:
imports:
- dask_sql
- dask_sql.input_utils
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this is here. We can drop this. Raised issue ( conda/grayskull#262 )

Comment on lines +46 to +47
- dask-sql-server --help
- dask-sql --help
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These seem like a good idea to check :)

requires:
- pip

about:
home: http://github.com/nils-braun/dask-sql/
summary: SQL Query Layer for dask
home: http://github.com/dask-contrib/dask-sql/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad it caught this 😄

Copy link
Member Author

@charlesbluca charlesbluca Nov 10, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It actually didn't catch this one 🙁 this was one of the few things I changed manually

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting if I run this locally, Grayskull seems to get this right. It should just be grabbing it from here. Could you please recheck?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah my bad, I'm thinking of the change I made to the summary - this was caught by grayskull 🎉

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok. In that case we might want to update this line

@jakirkham
Copy link
Member

We should also re-render now that the package is not noarch

@jakirkham
Copy link
Member

Adding to arch migrations ( conda-forge/conda-forge-pinning-feedstock#2160 ) since this will be not be noarch any more. This should help us provide packages on other architectures (like ARM)

recipe/meta.yaml Outdated
Comment on lines 19 to 20
build:
- maven >=3.6.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please keep this too

@jakirkham
Copy link
Member

Windows Python 3.9 failures appear to be due to missing jpype1 packages. PR ( conda-forge/jpype1-feedstock#40 ) should resolve that.

Copy link
Member

@quasiben quasiben left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the comments @jakirkham and the work here along with grayskull @charlesbluca :)

@jakirkham jakirkham added the automerge Merge the PR when CI passes label Nov 10, 2021
@charlesbluca
Copy link
Member Author

@conda-forge-admin, please restart CI

@github-actions
Copy link
Contributor

github-actions bot commented Nov 11, 2021

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

@jakirkham
Copy link
Member

Rerunning CI now that jpype1 has been built, uploaded, and mirrored

@github-actions github-actions bot merged commit 305f80d into conda-forge:master Nov 11, 2021
@jakirkham
Copy link
Member

Noticed a clobber warning in the log. Mentioned here ( conda-forge/openjdk-feedstock#59 (comment) )

@jakirkham
Copy link
Member

jakirkham commented Nov 11, 2021

Looks like packages are up and available from the CDN 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge the PR when CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants