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

crick source install blocking 3.9 CI #8369

Closed
charlesbluca opened this issue Nov 21, 2023 · 0 comments · Fixed by dask/crick#41
Closed

crick source install blocking 3.9 CI #8369

charlesbluca opened this issue Nov 21, 2023 · 0 comments · Fixed by dask/crick#41

Comments

@charlesbluca
Copy link
Member

charlesbluca commented Nov 21, 2023

It looks like the source install of crick is blocking 3.9 testing at the conda env creation:

https://github.com/dask/distributed/actions/runs/6939884322/job/18877927806

Think this is due to pip pulling the recently released setuptools=69, which is resulting in some new warnings:

      /tmp/pip-build-env-qcsag53s/overlay/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:75: _MissingDynamic: `description` defined outside of `pyproject.toml` is ignored.
      !!
      
              ********************************************************************************
              The following seems to be defined outside of `pyproject.toml`:
      
              `description = 'High performance approximate and streaming algorithms'`
      
              According to the spec (see the link below), however, setuptools CANNOT
              consider this value unless `description` is listed as `dynamic`.
      
              https://packaging.python.org/en/latest/specifications/declaring-project-metadata/
      
              To prevent this problem, you can list `description` under `dynamic` or alternatively
              remove the `[project]` table from your file and rely entirely on other means of
              configuration.
              ********************************************************************************

Think doing something like #7629 for the project should resolve things here

cc @jrbourbeau @milesgranger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants