emit warning while running flake8 without virtual env
Bug #1215401 reported by
Kui Shi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Opinion
|
Wishlist
|
Kui Shi | ||
Bug Description
run_tests.sh -N -p
it will call the flake8 installed on your host to detect PEP8, and
the flake8 plugin "OpenStack hacking" may not installed on your
host, so this command may not detect the OpenStack Style Commandment
supplied by hacking(e.g H202).
run_tests.sh -p
it will call the flake8 from virtual env, flake8 plugin "OpenStack
hacking" installed in virtual env will be triggered.
The result from "run_tests.sh -p" should be trusted, and jenkins uses
virtual env to run flake8 too.
When "-N" is enabled, emit warning to remind user.
| Changed in keystone: | |
| assignee: | nobody → Kui Shi (skuicloud) |
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #2 |
| Changed in keystone: | |
| status: | New → In Progress |
| Changed in keystone: | |
| importance: | Undecided → Wishlist |
| status: | In Progress → Opinion |
| Changed in keystone: | |
| status: | Opinion → In Progress |
| Changed in keystone: | |
| status: | In Progress → Opinion |
To post a comment you must log in.
I manage my own venv for development (as do several other developers), so I call run_tests.sh with -N to avoid a second venv being created... so you're intending to unconditionally harass me with warnings?