Skip to content

build[next]: Use dace release package from pypi#2600

Open
edopao wants to merge 1 commit into
GridTools:mainfrom
edopao:dace_switch_to_pypi_release
Open

build[next]: Use dace release package from pypi#2600
edopao wants to merge 1 commit into
GridTools:mainfrom
edopao:dace_switch_to_pypi_release

Conversation

@edopao
Copy link
Copy Markdown
Contributor

@edopao edopao commented May 12, 2026

Instead of using the gridtools package index, pull the dace pre-release package from PyPI index.

Copy link
Copy Markdown
Contributor

@philip-paul-mueller philip-paul-mueller left a comment

Choose a reason for hiding this comment

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

I am actually not sure if we should give up the index yet.
Because as soon as we need a special PR or so for DaCe we are back to the same solution as before.
For example we can not use the new GPU codegen until that is merged, which will take a long time.

Another question is what should happen with the GT4Py PyPI index?
This is also a question should we remove the entry from the pyproject.toml?

Maybe @egparedes you have some opinions on that.

Comment thread pyproject.toml
name = 'gridtools'
url = 'https://gridtools.github.io/pypi/'

# -- Example: {index = "gridtools", group = "dace-next"}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I have left this example as a reference in case we need to pull from the gridtools index.

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 this pull request may close these issues.

2 participants