systematic use of from __future__ import absolute_import
. it eliminates import NAME
confusion with very common names (eg. import ldap
is very ambiguous: can be a ldap module from realms-wiki, a ldap module from flask-ldap-login, or python-ldap
module.
also cleant up a bit the import towards PEP8: builtin modules first, then 3rd party python packages, then local packages
This commit is contained in:
parent
2919be6b87
commit
2731531768
38 changed files with 156 additions and 42 deletions
|
@ -1,3 +1,5 @@
|
|||
from __future__ import absolute_import
|
||||
|
||||
from ..models import Auth
|
||||
|
||||
Auth.register('oauth')
|
||||
|
|
|
@ -1,8 +1,10 @@
|
|||
from __future__ import absolute_import
|
||||
|
||||
from flask import session
|
||||
from flask_login import login_user
|
||||
from flask_oauthlib.client import OAuth
|
||||
|
||||
from realms import config
|
||||
from .... import config
|
||||
from ..models import BaseUser
|
||||
|
||||
config = config.conf
|
||||
|
|
|
@ -1,3 +1,5 @@
|
|||
from __future__ import absolute_import
|
||||
|
||||
from flask import Blueprint, url_for, request, flash, redirect, session, current_app
|
||||
from .models import User
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue