Add support for python 3.14 and remove support for Python 3.11 #67
Description
problem
To bump the Python version, all dependencies in the core pack need to support 3.14.
# core pack dependencies
packaging
PyYAML
diffpy.utils
diffpy.srfit
diffpy.structure
solution
Add python 3.14 support when the core pack can support python 3.14
status for each package
diffpy.utils: diffpy/diffpy.utils#360
diffpy.srfit: diffpy/diffpy.srfit#136
diffpy.structure: diffpy/diffpy.structure#148
Activity
[-]remove python 3.13 workflow pin when pyobjcryst and diffpy.srreal support python 3.14[/-][+]Add support for python 3.14 and remove support for Python 3.11[/+]cadenmyers13 commentedon Dec 18, 2025
@sbillinge I changed this issue a bit. Because cmi's only dependencies (technically) are only those in
core, I think this is a good plan moving forward with python version bumps. Essentially just make sure that everything withincoresupports the latest Python, then we can bump.How do you feel about doing a minor bump of cmi (3.1.2)? I would like to get the latest example scripts shipped with cmi before grenoble and it seems that we're not going to get the
coreorpdfpack up to python 3.14 before then. If you agree, I'll change this issue to 3.1.2 release: #96sbillinge commentedon Dec 19, 2025
ok, sounds good. We can do a minor bump
sbillinge commentedon Aug 13, 2026
closed by #112
cadenmyers13 commentedon Aug 13, 2026
@sbillinge This isn't closed yet. We need to think about how we want to handle this. If a pack, say
pdf, supports py311-313 and another supports 312-314 do we want to support all python versions 311-314? I think yes..?sbillinge commentedon Aug 13, 2026
Mmm, the packs are supposed to free us up from this though as it forces us to be backwards compatible to the beginning of time. I think no?
sbillinge commentedon Aug 13, 2026
Since now it's the beginning of time for packs I think it is ok that this version goes back to 3.11