Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Dask version semantics overly strict in pyproject.toml #278

Closed
JSKenyon opened this issue May 25, 2023 · 1 comment · Fixed by #279
Closed

Dask version semantics overly strict in pyproject.toml #278

JSKenyon opened this issue May 25, 2023 · 1 comment · Fixed by #279

Comments

@JSKenyon
Copy link
Collaborator

  • dask-ms version: master
  • Python version: 3.8.10
  • Operating System: Ubuntu 20.04 LTS

Description

I believe that some of my dependency woes stem from the ^version syntax in pyproject.toml. The versioning of dask means that ^2022.9.1 will never allow the installation of a 2023.x.x version. Would it be more sensible to specify >=2022.9.1?
@sjperkins
Copy link
Member

Yep, let me try this locally

@sjperkins sjperkins mentioned this issue May 25, 2023
Merged
2 tasks
@sjperkins sjperkins mentioned this issue May 31, 2023
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade package versions to 2023 versions ratt-ru/dask-ms
2 participants
@sjperkins @JSKenyon