Open jsheunis opened 11 months ago
I think the unwritten policy with Python tends to be going along with the Python release life cycle. With 3.7 EOL in June 2023 (and 3.8 set for Oct 2024), I think 3.8 is a good idea.
I am less sure about DataLad. Typically very few changes should affect the template as such (although blame suggests that the latest update was indeed done following such change), but with the general tendency to always favor the latest, perhaps we should?
My thoughts match those of @mslw with regard to Python. With regard to DataLad I'm also hesitant; my line of thought goes into the direction of availability of DataLad 0.19 across different systems, some Linux distributions tend to lag behind for a while. E.g. https://packages.debian.org/search?keywords=datalad&searchon=names&suite=stable§ion=all
In https://github.com/datalad/datalad-extension-template/blob/main/setup.cfg#L14-L17:
should we go to latest datalad version? and what about python?