"fixture" modules incorrectly imported when using Pycharm
Bug #1879320 reported by
Rodolfo Alonso
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ovsdbapp |
Invalid
|
Undecided
|
Rodolfo Alonso | ||
Bug Description
Local "fixtures" modules are incorrectly imported when using a debugger like the Pycharm unit test runner. Python 3, by default, in case of having a local module named as a global module, imports the global first ("absolute_import" is the default behavior [1]). But when running the test cases with the Pycharm debugger, the local "fixture" module is imported first.
| Changed in ovsdbapp: | |
| assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to ovsdbapp (master) | #1 |
| Changed in ovsdbapp: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on ovsdbapp (master) | #2 |
| Changed in ovsdbapp: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/