yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #18307
[Bug 1350452] [NEW] doc/source/conf.py hits E265 PEP8 error
Public bug reported:
doc/source/conf.py hits E265 PEP8 check.
Note that this bug is hidden due to bug 1347472 now.
To enable pep8/flake8 check again ASAP, I would like to fix this later and exclude doc/source/conf.py from flake8 temporarily.
This bug is to track this temporary work around.
/doc/source/conf.py:60:21: E265 block comment should start with '# '
./doc/source/conf.py:145:1: E265 block comment should start with '# '
./doc/source/conf.py:150:1: E265 block comment should start with '# '
./doc/source/conf.py:171:1: E265 block comment should start with '# '
./doc/source/conf.py:191:1: E265 block comment should start with '# '
./doc/source/conf.py:195:1: E265 block comment should start with '# '
** Affects: horizon
Importance: Low
Assignee: Akihiro Motoki (amotoki)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1350452
Title:
doc/source/conf.py hits E265 PEP8 error
Status in OpenStack Dashboard (Horizon):
New
Bug description:
doc/source/conf.py hits E265 PEP8 check.
Note that this bug is hidden due to bug 1347472 now.
To enable pep8/flake8 check again ASAP, I would like to fix this later and exclude doc/source/conf.py from flake8 temporarily.
This bug is to track this temporary work around.
/doc/source/conf.py:60:21: E265 block comment should start with '# '
./doc/source/conf.py:145:1: E265 block comment should start with '# '
./doc/source/conf.py:150:1: E265 block comment should start with '# '
./doc/source/conf.py:171:1: E265 block comment should start with '# '
./doc/source/conf.py:191:1: E265 block comment should start with '# '
./doc/source/conf.py:195:1: E265 block comment should start with '# '
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1350452/+subscriptions
Follow ups
References