Skip to content

skpkg: update to latest scikit-package standards, add Python 3.14 support, remove Python 3.11 support - #1292

Open
danielsirakov wants to merge 9 commits into
regro:mainfrom
danielsirakov:skpkg-update
Open

skpkg: update to latest scikit-package standards, add Python 3.14 support, remove Python 3.11 support#1292
danielsirakov wants to merge 9 commits into
regro:mainfrom
danielsirakov:skpkg-update

Conversation

@danielsirakov

@danielsirakov danielsirakov commented Aug 6, 2026

Copy link
Copy Markdown

I ran scikit package update, updated to add Python 3.14 support, and removed Python 3.11 support.

@sbillinge ready to review

Closes #1271
Closes #1264
Closes #1262
Closes #1246
Closes #1215
Closes #1210
Closes #1208

@sbillinge sbillinge left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this looks great. I just had a couple of questions

Comment thread .github/workflows/build-wheel-release-upload.yml Outdated
Comment thread .github/workflows/tests-on-pr.yml Outdated
c_extension: false
headless: false
python_version: 3.13
python_version: 3.14

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this maybe needs to be deleted. Was it added by skpkg or manually edited by @danielsirakov ? Please maybe check some other of our diffpy packages.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I think I manually changed the version number, but I can't remember exactly. Besides the changed version number, the file is exactly how it was before I ran the package update. I checked diffpy.srfit, and it has a tests-on-pr.yml file that looks identical but does not have python_version and run: pip install gooey lines. I'm not 100 percent sure, but I feel like those lines might not have been included in the scikit template. What exactly should I delete? Thank you!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yes, please remove the python version number and the pip install gooey lines

@sbillinge sbillinge Aug 6, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Also remove the pip install gooey logic

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@sbillinge I just checked, and gooey is imported at the top of a lot of the helper files, meaning that I can't remove its logic without breaking the imports, if you're referring to gooey logic in regolith as a whole. There isn't any more gooey logic in the tests-on-pr.yml file. It turns out gooey is actually listed in requirements\pip.txt, so I can still remove this line because it's redundant. I'll remove both lines now and push.

@danielsirakov

Copy link
Copy Markdown
Author

@sbillinge just made the quick change to maintainers

@sbillinge

Copy link
Copy Markdown
Contributor

@danielsirakov I responded to your questions for hte last couple of changes.

@danielsirakov

Copy link
Copy Markdown
Author

@sbillinge I just removed the python-version and gooey lines from tests-on-pr.yml. Let me know if there's anything else I need to change. Thank you!

@sbillinge

Copy link
Copy Markdown
Contributor

For some reason the tests are queued and stalled. It may be a good idea to generate a new commit and push it and see if we can trigger the CI

@danielsirakov

Copy link
Copy Markdown
Author

@sbillinge I merged your changes into my local and now the CI passes. Thank you!

@sbillinge

Copy link
Copy Markdown
Contributor

@sbillinge I merged your changes into my local and now the CI passes. Thank you!

tests are not running in CI. We need to trigger it. That is why I am asking you to generate a new commit and push it to try and unstick it.

@sbillinge

Copy link
Copy Markdown
Contributor

@danielsirakov sorry, I forgot to tag you on this.

@danielsirakov

Copy link
Copy Markdown
Author

@sbillinge I see, I thought the merge would get tracked as a new commit. I just pushed an empty commit, does that unstick it?

@sbillinge

Copy link
Copy Markdown
Contributor

@danielsirakov now it is not even running the news check. Either we broke the CI scripts with the skpkg update, or some weird thing has happened to GitHub.

I recommend that we maybe close the PR and then create a brand new PR. Maybe create a new branch from this branch and push that to origin and make a new PR from that? Also, take a look at changes in the GH Actions scripts and see if we can see anything odd.

@sbillinge

Copy link
Copy Markdown
Contributor

I think the github actions issue may be resolved. Please can you try another push? @danielsirakov

@danielsirakov

Copy link
Copy Markdown
Author

@sbillinge Sorry for the delay, I was travelling. I just pushed another empty commit. On my end, it looks like everything is passing, but please let me know if there are any issues again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment