Replace relative imports to make isort happy

[amw]

README suggest running flake8 before contributing, but current master reports issues.

$ flake8
./example/tests/test_views.py:14:1: I001 isort found an import in the wrong position

This fixes the current issue. Long term you'd probably want to add flake8 to the test suite and reject PRs that have flake8 problems. If you don't care about flake8 issues then maybe we should remove it from README?

[codecov]

Codecov Report

Merging #681 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #681      +/-   ##
==========================================
- Coverage   95.96%   95.96%   -0.01%     
==========================================
  Files          54       54              
  Lines        2728     2727       -1     
==========================================
- Hits         2618     2617       -1     
  Misses        110      110

Impacted Files	Coverage Δ
example/api/resources/identity.py	100% <100%> (ø)	⬆️
example/tests/test_utils.py	100% <100%> (ø)	⬆️
example/tests/test_views.py	100% <100%> (ø)	⬆️
example/tests/test_filters.py	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c6cceb...00ac7c3. Read the comment docs.

[sliverc]

This change raises an error for me locally. Could it be that you have an outdated isort?

Also see #686

What I find really odd though is why CI is green as flake8 is already enforced. When I run tox -e flake8 locally with this change it also fails. 🤔

[amw]

You mean it raises an isort error or does the app/pytest fail?

I don't think my isort is outdated. It's version is locked by requirements file.

$ cat requirements-development.txt | grep isort
flake8-isort==2.7.0
isort==4.3.21
$ pip freeze | grep isort
flake8-isort==2.7.0
isort==4.3.21
$ pytest -q -o console_output_style=classic
.........................................................................................................................................................................................................
201 passed in 7.41 seconds

[sliverc]

Odd I get the exact same error you get with the same isort version you use but with using your fix.

Most likely an oddness in isort itself. However I don't think using relative and absolute imports mixed is a good idea. So updated this PR not to use relative imports which should also fix this error.