[Starlingx-discuss] REPLY: Python 3 Error in python 2.7 env when building iso
shuicheng.lin at intel.com
Mon May 6 01:12:21 UTC 2019
I agree with you it is a bug in starlingx script. It is not hit just because it is in error handle flow.
FileNotFoundError is a python3 only parameter, we should write the code be compatible with both python3 and python2.
Please feel free to submit a patch to fix it.
From: Song Gao song (高松) [mailto:gaosong.lc at inspur.com]
Sent: Monday, May 6, 2019 9:00 AM
To: michel.thebeau at windriver.com; starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] REPLY: Python 3 Error in python 2.7 env when building iso
Sorry for this lately reply! But how you solved this problem on your building host?
发件人: Michel Thebeau [mailto:michel.thebeau at windriver.com]
发送时间: 2019年4月29日 22:01
收件人: Song Gao song (高松) <gaosong.lc at inspur.com>; starlingx-discuss at lists.starlingx.io
主题: Re: [Starlingx-discuss] Python 3 Error in python 2.7 env when building iso
If memory serves me correctly, that's a version of mock that does not properly report python3 as a requirement. A month ago I fixed this on my build host by downgrading mock to a version that was not broken.
Google search is agreeing with my memory:
On Sun, 2019-04-28 at 02:11 +0000, Song Gao song (高松) wrote:
> Hi Folks:
> According to the Build Guide for stx.2019.05, there is an
> error found in the building container,
> /usr/lib/python2.7/site-packages/mockbuild/package_manager.py Line
> 162 will interrupt buiding
> Process By throwing out an FileNotFoundError. While, FileNotFoundError
> is an Python3 built-in error, not in python2.7. Just reporting to the
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
More information about the Starlingx-discuss