Hi all, Please consider including the attached patch. With this patch, cmake searches for the correct path of the python2 interpreter and uses that path for calling python, instead of just calling "python". This fixes a bug on Fedora, which no longer has an unversioned python interpreter (i.e., only python2 and python3). It should also avoid using python3 on accident. On a related note, are there any plans to switch to python3? I only had a quick glance and there are some incompatibilities, but most of them seem to be rather straight-forward to fix. Thanks! Till
Hi! Thanks for the patch! On 14.07.2018 13:36, Till Hofmann wrote:
On a related note, are there any plans to switch to python3? I only had a quick glance and there are some incompatibilities, but most of them seem to be rather straight-forward to fix.
Well if you send in a patch to make it work with python3 it will certainly be welcome. -richy.
Hi all, it looks like that patch never made it into the repository. Was that an oversight or is there something wrong with the patch? I'd be happy to fix any issues, so we can remove the patch downstream. Thanks! Till On 7/14/18 1:36 PM, Till Hofmann wrote:
Hi all,
Please consider including the attached patch. With this patch, cmake searches for the correct path of the python2 interpreter and uses that path for calling python, instead of just calling "python".
This fixes a bug on Fedora, which no longer has an unversioned python interpreter (i.e., only python2 and python3). It should also avoid using python3 on accident.
On a related note, are there any plans to switch to python3? I only had a quick glance and there are some incompatibilities, but most of them seem to be rather straight-forward to fix.
Thanks! Till
On 17.02.19 18:56, Till Hofmann wrote:
it looks like that patch never made it into the repository. Was that an oversight or is there something wrong with the patch? I'd be happy to fix any issues, so we can remove the patch downstream.
Sorry, I had forgotten about this. Back when you first sent this, I asked to consider python3. Does anything speak against porting the Python code to Python3? -richy.
On 17.02.19 18:56, Till Hofmann wrote:
it looks like that patch never made it into the repository. Was that an oversight or is there something wrong with the patch? I'd be happy to fix any issues, so we can remove the patch downstream.
I applied '2to3' to scripts/yaptu.py and it was just a one-line fix. This way, GiNaC does not depend on any specific version of Python. Please check if this fixes your issue. -richy.
participants (2)
-
Richard B. Kreckel
-
Till Hofmann