Skip to content

Update PyTorch to 2.15.0, Python to 3.14 - #1183

Merged
BenjaminBossan merged 3 commits into
masterfrom
pytorch-2.15.0
Nov 10, 2026
Merged

BenjaminBossan merged 3 commits into
masterfrom
pytorch-2.15.0

Conversation

@BenjaminBossan

@BenjaminBossan BenjaminBossan commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

torch:

  • Add 2.15.0 to CI and docs
  • Remove 2.11.0
  • Bump 2.14.0 to 2.14.1

From checking the changelog, there should be no need for further changes in skorch.

Python

  • Add 3.14 to CI, docs, pyproject.toml
  • Remove 3.10 (EOL)
  • Bump 2.14.0 to 2.14.1
  • Update pandas test
  • Remove sacred from extended deps for Python 3.14, as importing it raises an error (AttributeError: module 'pkgutil' has no attribute 'find_loader'); sacred hasn't been updated for over a year, so unsure if it's ever going to be fixed

- Add torch 2.15.0 to CI and docs
- Remove 2.11.0
- Bump 2.14.0 to 2.14.1

From checking the changelog, there should be no need for further
changes in skorch.
- Python 3.10 is EOL and removed
- Python 3.14 is added
- Update pandas test
@BenjaminBossan BenjaminBossan changed the title Update PyTorch to 2.15.0 Update PyTorch to 2.15.0, Python to 3.14 Nov 5, 2026
Sacred cannot be imported, as it raises this error:

> AttributeError: module 'pkgutil' has no attribute 'find_loader'

Not sure if this is going to be fixed, sacred hasn't been updated in
over a year at the time of writing.

@thomasjpfan thomasjpfan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

sacred hasn't been updated for over a year, so unsure if it's ever going to be fixed

If it makes things easier, I would even be okay with dropping sacred.

Otherwise LGTM

git clone https://github.com/skorch-dev/skorch.git
cd skorch
conda create -n skorch-env python=3.10
conda create -n skorch-env python=3.12

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Should this be 3.11?

BTW I'm okay with even setting it to the newest support Python version.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I went with 3.12 here for consistency, e.g. with the README:

skorch/README.rst

Lines 186 to 197 in 066927b

conda create -n skorch-env python=3.12
conda activate skorch-env
python -m pip install torch
python -m pip install .
If you want to help developing, run:
.. code:: bash
git clone https://github.com/skorch-dev/skorch.git
cd skorch
conda create -n skorch-env python=3.12

@BenjaminBossan

Copy link
Copy Markdown
Collaborator Author

If it makes things easier, I would even be okay with dropping sacred.

Not sure if anyone is using the Sacred callback, but I think as long as it still works (i.e. until Python 3.13 is EOL), the cost of keeping it around is minimal, so I'd just leave it for the time being.

@BenjaminBossan
BenjaminBossan merged commit 71d639f into master Nov 10, 2026
16 checks passed
@BenjaminBossan
BenjaminBossan deleted the pytorch-2.15.0 branch November 10, 2026 00:54
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