[Linaro-validation] About the adb command on LAVA

2013-07-16 Thread YongQin Liu
Hi, All >From this file: http://bazaar.launchpad.net/~linaro-validation/lava-lab/salt-states/view/head:/adb/init.sls we can see that the /usr/local/bin/adb file should be a symbolic of /usr/ local/android-sdk-linux/platform-tools/adb but now it's a normal file(the adb wrapper before): liuyq0307

Re: [Linaro-validation] Test Framework and Tools

2013-07-16 Thread Milo Casagrande
On Tue, Jul 16, 2013 at 12:52 PM, Zygmunt Bazyli Krynicki wrote: > > Mocker and mock are totally different. Mock is in stdlib since 3.3 so it is > likely the future but I found mocker easier to use and understand (I'm also > the current maintainer for mocker, if inactive a bit). > > As for nose/py

Re: [Linaro-validation] PEP8 checker variability

2013-07-16 Thread Neil Williams
On Tue, 16 Jul 2013 10:13:50 +0200 Milo Casagrande wrote: > I usually use pep8 and pyflakes directly from the command line. What's the general feeling about adding comments which override certain (non-PEP8) checks? PyCharm can inspect code and provide overrides for certain functions, e.g.: clas

Re: [Linaro-validation] Test Framework and Tools

2013-07-16 Thread Zygmunt Bazyli Krynicki
Hi Mocker and mock are totally different. Mock is in stdlib since 3.3 so it is likely the future but I found mocker easier to use and understand (I'm also the current maintainer for mocker, if inactive a bit). As for nose/py.test: both are a bit non standard. I would strongly recommend that you u

[Linaro-validation] Test Framework and Tools

2013-07-16 Thread Milo Casagrande
Hello everyone, one of the discussion we had during connect was to find (and use) a common testing framework for unit (and maybe beyond) tests. What we should use is probably a framework that still supports all the unittest based tests we already have in our projects. Following also other people

Re: [Linaro-validation] PEP8 checker variability

2013-07-16 Thread Milo Casagrande
On Tue, Jul 16, 2013 at 10:26 AM, Zygmunt Bazyli Krynicki wrote: > Just put the required version of flake8 > in some git repo and have people install that if you want standalone > "offline" things to work. I guess we will have to do that, yes. There are people that do not use deb based distros, s

Re: [Linaro-validation] PEP8 checker variability

2013-07-16 Thread Zygmunt Bazyli Krynicki
Hi Milo I don't think that there's any sane way to get consistent checks without using flake8 (which indeed uses pep8 and others internally) from pypi. There is just too much variability in the packaged versions out there. It's doable but IMHO it's not worth the hassle. Just put the required versi

Re: [Linaro-validation] PEP8 checker variability

2013-07-16 Thread Milo Casagrande
I usually use pep8 and pyflakes directly from the command line. As Zygmut said, pflake8 is a handy tool (if I'm not wrong it runs pep8 and pyflakes). Before a commit I run the files also under pylint, but it is a manual process since it can report lots of warnings that one can actually ignore. I