Hey Gabe, We've had many discussions on this in the past couple of months. The underlying problem is that each distro has decided to do something different with /usr/bin/python. Some of them allow it to point to python3 others force it to point to python2. This screws up Scons, our scripts, and lots of other things.
The only solution, as far as we can tell, is to drop support for python2 and switch everything to use python3. I think we should do this after gem5-20.1 is released. I've found that if you install python3 and create a symlink from /usr/bin/python to /usr/bin/python3 (apt install python-is-python3 on Ubuntu, but not possible on OpenSUSE except manually, not sure about arch) thing work OK. Cheers, Jason On Tue, Aug 25, 2020 at 11:42 PM Gabe Black via gem5-dev <gem5-dev@gem5.org> wrote: > Hi folks. We've been moving to python 3 for many things, but for gem5's > built in python, aka config scripts, we still default to python 2 instead > of python 3. When do we plan to change that? I ask because I ran into a > problem where the python 2.7 pyconfig.h doesn't compile correctly on my > desktop, and since 2.7 is EOL I don't think my distribution (Arch Linux) is > going to fix it. > > I can get it to work by manually saying I want to use python3-config, but > would it make sense for that to be the default? > > Gabe > _______________________________________________ > gem5-dev mailing list -- gem5-dev@gem5.org > To unsubscribe send an email to gem5-dev-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
