[opensuse-factory] Using Python 3 in VirtualBox
Hi, I have finished converting VirtualBox from Python 2.7 to 3.6, and I am currently testing it. No problems with the new package have been found, once it built without error. Most of the changes were contained within the VB files; however, the system macro py_compile found in /usr/lib/rpm/macros is hardwired to use the "python" command, which causes it to try to use Python 2.7. My hack is to add a new version of that macro using python3 to the VB spec file. It works, but I am wondering if the system version should use __python, or some other macro. Is this situation worthy of a bug report? As far as I can tell, all supported versions of openSUSE contain Python 3.6. Should I push this change to Factory as soon as the testing is complete? What about Leap 15.0 and Leap 42.3 updates? Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On jeudi, 31 mai 2018 18.03:57 h CEST Larry Finger wrote:
Hi,
I have finished converting VirtualBox from Python 2.7 to 3.6, and I am currently testing it. No problems with the new package have been found, once it built without error.
Most of the changes were contained within the VB files; however, the system macro py_compile found in /usr/lib/rpm/macros is hardwired to use the "python" command, which causes it to try to use Python 2.7. My hack is to add a new version of that macro using python3 to the VB spec file. It works, but I am wondering if the system version should use __python, or some other macro. Is this situation worthy of a bug report?
As far as I can tell, all supported versions of openSUSE contain Python 3.6. Should I push this change to Factory as soon as the testing is complete? What about Leap 15.0 and Leap 42.3 updates?
Thanks,
Larry
Not sure which process you've used, but I guess that all the multiversion python we have should address your need. Can you share a link about your build test ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe supporter GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/01/2018 02:09 AM, Bruno Friedmann wrote:
On jeudi, 31 mai 2018 18.03:57 h CEST Larry Finger wrote:
Hi,
I have finished converting VirtualBox from Python 2.7 to 3.6, and I am currently testing it. No problems with the new package have been found, once it built without error.
Most of the changes were contained within the VB files; however, the system macro py_compile found in /usr/lib/rpm/macros is hardwired to use the "python" command, which causes it to try to use Python 2.7. My hack is to add a new version of that macro using python3 to the VB spec file. It works, but I am wondering if the system version should use __python, or some other macro. Is this situation worthy of a bug report?
As far as I can tell, all supported versions of openSUSE contain Python 3.6. Should I push this change to Factory as soon as the testing is complete? What about Leap 15.0 and Leap 42.3 updates?
Thanks,
Larry
Not sure which process you've used, but I guess that all the multiversion python we have should address your need.
Can you share a link about your build test ?
Bruno, Thanks for looking at this. The revised project is at https://build.opensuse.org/package/show/home:lwfinger:branches:openSUSE:Fact.... That is just a temporary repo and will not ever be pushed upstream. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Bruno Friedmann
-
Larry Finger