Re: [oi-dev] Python components
In regard to: [oi-dev] Python components, Nona Hansel said (at 5:59pm on...: I'm thinking about updating two Python packages - tqdm and colorama. Currently, there is variable PYTHON_VERSIONS= 3.5 in both Makefiles which means, if I understand it correctly, that the package is build for Python 3.5. Yes, and the implicit information you should take away from that is that those packages are *not* being built for the older Python 2.7. I wonder if I should let this variable like this or should I increase Python version. If so, to what version? Or should we have more versions at the same time? OI packages and provides multiple series of Python. You can have e.g. runtime/python-27 and runtime/python-35 installed at the same time, along with modules packaged for each. You should only increase PYTHON_VERSIONS *if* OI starts shipping a newer Python series. In that case, you would probably leave 3.5 there, but add the newer version too, so that these modules continue to be built for the 3.5 series, in addition to being built for the new series. As Andreas already said, it's a good idea to look at all the other python modules, to get an idea of which modules build for just a specific Python series and which build for any and all of the options that OI currently provides. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure / Division of Information Technology/701-231-1076 (Voice) North Dakota State University, Fargo, ND 58105-5164 ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Python components
Am 18.11.20 um 17:59 schrieb Nona Hansel: Hi, I'm thinking about updating two Python packages - tqdm and colorama. Currently, there is variable PYTHON_VERSIONS= 3.5 in both Makefiles which means, if I understand it correctly, that the package is build for Python 3.5. I wonder if I should let this variable like this or should I increase Python version. If so, to what version? Or should we have more versions at the same time? Thank you, Nona Hi Nona, PYTHON_VERSIONS expects a space separated list of versions, eg. PYTHON_VERSIONS= 3.5 3.7 3.8 For colorama this is accompanied by the special manifest file colorama-PYVER.p5m. PYVER is replaced by any member of the PYTHON_VERSIONS list. BTW: In cases like this it is helpful to search for similar cases, eg. with find . -name Makefile | xargs grep PYTHON_VERSIONS from within the components/python (or even from components) folder. It can also be interesting to read the macros in the make-rules folder (eg. grep there for PYTHON_VERSIONS to find references). Hope this helps, Andreas ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] Python components
Hi, I'm thinking about updating two Python packages - tqdm and colorama. Currently, there is variable PYTHON_VERSIONS= 3.5 in both Makefiles which means, if I understand it correctly, that the package is build for Python 3.5. I wonder if I should let this variable like this or should I increase Python version. If so, to what version? Or should we have more versions at the same time? Thank you, Nona ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
