Skip to content

Comments

25 check if we need to upgrade to python 313 and validate compatibility pybis custom parsers etc if compatibility issues arise keep python312 lucaszimm#28

Merged
LucasZimm merged 5 commits intocookiecutterinstallfrom
25-check-if-we-need-to-upgrade-to-python-313-and-validate-compatibility-pybis-custom-parsers-etc-if-compatibility-issues-arise-keep-python312-lucaszimm
Feb 16, 2026
Merged

25 check if we need to upgrade to python 313 and validate compatibility pybis custom parsers etc if compatibility issues arise keep python312 lucaszimm#28
LucasZimm merged 5 commits intocookiecutterinstallfrom
25-check-if-we-need-to-upgrade-to-python-313-and-validate-compatibility-pybis-custom-parsers-etc-if-compatibility-issues-arise-keep-python312-lucaszimm

Conversation

@LucasZimm
Copy link
Collaborator

  • upgrades python version to 3.13

…e-to-python-313-and-validate-compatibility-pybis-custom-parsers-etc-if-compatibility-issues-arise-keep-python312-lucaszimm
@LucasZimm LucasZimm self-assigned this Jan 12, 2026
@LucasZimm
Copy link
Collaborator Author

  • only openbis-upload-helper[dev]==0.1.0 requires Python version (3.12.12) for now

@JosePizarro3
Copy link
Member

probably you need to modify the github actions (in .github/workflows/*.yaml) to fix this

Also, do we want to bump the Python version to 3.13? We might wana just change the testing and building of the actions while leaving the requires-python>=3.12

…e-to-python-313-and-validate-compatibility-pybis-custom-parsers-etc-if-compatibility-issues-arise-keep-python312-lucaszimm
…e-to-python-313-and-validate-compatibility-pybis-custom-parsers-etc-if-compatibility-issues-arise-keep-python312-lucaszimm
@LucasZimm LucasZimm merged commit da6c27e into cookiecutterinstall Feb 16, 2026
2 checks passed
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