put the import of pexpect around a try statement so it can tell you
why it failed to import when in a system that has the module unreachable
the message that outputs is:
"No module named pexpect, import failed"
"Please install pexpect (python-pexpect)"
Signed-off-by: Benjamin Esquivel
---
meta
enembedded-core-boun...@lists.openembedded.org
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Benjamin
Esquivel
Sent: Friday, September 18, 2015 11:34
To: openembedded-core@lists.openembedded.org
Cc: paul.eggle...@linux.intel.com
Subject: [OE-core] [PATCH V2] selftest/buildo
On 21 September 2015 at 09:37, Istrate, Daniel AlexandruX <
daniel.alexandrux.istr...@intel.com> wrote:
> Just want to point out that 'pexpect' is an unused import in
> buildoptions.py. Unused imports are also unittest and logging.
> Instead of try-catch an import that is not used I think it's bes
@lists.openembedded.org;
paul.eggle...@linux.intel.com
Subject: Re: [OE-core] [PATCH V2] selftest/buildoptions: pexpect not a builtin
module
On 21 September 2015 at 09:37, Istrate, Daniel AlexandruX
mailto:daniel.alexandrux.istr...@intel.com>>
wrote:
Just want to point out that 'pexpect&#x
ur...@intel.com]
> Sent: Monday, September 21, 2015 13:20
> To: Istrate, Daniel AlexandruX
> Cc: Benjamin Esquivel; openembedded-core@lists.openembedded.org;
> paul.eggle...@linux.intel.com
> Subject: Re: [OE-core] [PATCH V2] selftest/buildoptions: pexpect not
> a builtin module
>
