[openstack-dev] [tox/pep8] different result between running tox and pep8

Xiangfei Zhu xiangfeiz at vmware.com
Fri Jul 10 03:33:01 UTC 2015


Not sure if what I met if the same as yours.

In my case, "pep8 ." reported many errors located in the virtual environment folder. In my case, things like:

./.venv/lib/python2.7/site-packages/virtualenv.py:260:13: E265 block comment should start with '# '

To work around it, I use "pep8 <subfolder name of the package, e.g. nova, cinder>".

Hope this helps.


From: Gareth <academicgareth at gmail.com<mailto:academicgareth at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, July 10, 2015 11:15 AM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [tox/pep8] different result between running tox and pep8

Hi guys

My problem looks simple:

Running "tox -e pep8", the result says ok, not pep8 mistakes.
Running "pep8 .", a lot of pep8 mistkes come out.

But in your project's tox.ini, there isn't such a long ignore list. So what makes this difference happen?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150710/37be2960/attachment.html>

More information about the OpenStack-dev mailing list