I've noticed that setup.py is explicitly referenced in several places: https://github.com/search?q=repo%3Adask%2Fdask-image+setup.py&type=code

Perhaps most critically in

(replacement might be python -m build? Not sure whether build would need to be added as a dependency)

and

underlying the gpuci failure (replacement might be python -m pip install -e . ?).

Yeah in terms of CI changes with setup.py. Would suggest going the pip install route for now. That is pretty close to what we were doing before

The conflict is probably due to PR ( #336 ). Though think we can just delete the file again during conflict resolution

I merged main to start testing this branch

The gpuCI fails with the following errpr:

09:53:55 python: can't open file '/workspace/setup.py': [Errno 2] No such file or directory

Could it be that "setup.py" is mentioned somewhere in the Jenkins configuration?

From CI:

python: can't open file '/workspace/setup.py': [Errno 2] No such file or directory

Looks like this code needs an update:

Edit: It is probably worth using git grep to find any more setup.py references and replacing them. A quick GH search reveals a few setup.py usages (notably in docs)

I had overseen the code you referenced somehow, thanks for the clarification John 🙏

@GenevieveBuckley Would you like me to help completing this PR?

PR #370 adds python 3.12 support. This PR should also have python 3.12 support.

@GenevieveBuckley Would you like me to help completing this PR?

Sorry I didn't see your message earlier @m-albert
Of course, if you want to give it a go I'm very happy for you to do that 😄

Decision: I'm going to try replacing versioneer with setuptools-scm as part of this PR.
It seems simpler for maintenance, and looks like it will have better long term support. Fingers crossed for a smooth transition 🤞

Ok, done. There's still a few GPU CI things left to take care of, and that work is happening in separate PRs.

Hooray! 🎉

Thanks Genevieve! 🙏

@GenevieveBuckley 🚀