Fixed the error I introduced when trying to fix pylint errors. There was a false positive on wrong-import-position in init.py. The blueprint registration requires that import be in the "wrong" position, so it was moved back and steps were taken to try and suppress the error unsuccessfully. I think it has to do with being inline with an import statement, rather than other code.
ANYWAY...Please merge this PR so we can push it to the dev-server.
Fixed the error I introduced when trying to fix pylint errors. There was a false positive on wrong-import-position in init.py. The blueprint registration requires that import be in the "wrong" position, so it was moved back and steps were taken to try and suppress the error unsuccessfully. I think it has to do with being inline with an import statement, rather than other code.
ANYWAY...Please merge this PR so we can push it to the dev-server.