Tags: lincc-frameworks/python-project-template
Tags
Add testing stage for trying against lowest pinned versions. (#515) * Add testing stage for trying against lowest pinned versions. * Update copier.yml Co-authored-by: Konstantin Malanchev <hombit@gmail.com> --------- Co-authored-by: Konstantin Malanchev <hombit@gmail.com>
Adding "better" python version propagation, and removing hardcoded py… …thon versions. (#484) - There are now three defined python versions you can use in templates, they are derived from python_versions and available through jinja macros. - py.pref(), py.max(), and py.min() are the macros, using the preferred import {%- import 'python-versions.jinja' as py -%}. Notably this is the only type of import that copier will accept in files who's pathnames contain templates. which eliminates several more syntactically ergonomic methods of achieving this same interface. - py.pref(python_versions), the preferred version, is the "middle-est" in the python_versions list, see python-versions.jinja for the math. For the default case where python_versions = [3.9,3.10,3,11], 3.10 is the preferred python version. - Hardcoded mentions of python 3.9 and python 3.10 have been set to py.min(python_versions) or py.pref(python_versions) respectively so that this change does not affect projects using the default configuration, and any python upgrade compatibility issues can be deferred until either the project template or an individual project changes python version support. - References to python_versions[0] have been replaced with py.min(python_versions) for consistency.
PreviousNext