Personal/realms-wiki
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

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.

Browse source 
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:
stef 2016-08-20 00:48:00 +02:00 • committed by Stephane Martin
parent 2919be6b87
commit 2731531768
38 changed files with 156 additions and 42 deletions
Download patch file Download diff file Expand all files Collapse all files

8
realms/modules/auth/ldap/views.py
View file

@ -1,7 +1,15 @@
<<<<<<< HEAD
from flask import current_app, request, redirect, Blueprint, flash, url_for, session
from ..ldap.models import User
=======
from __future__ import absolute_import
from flask import current_app, request, redirect, Blueprint, flash, url_for
>>>>>>> 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.
from flask_ldap_login import LDAPLoginForm
from .models import User
blueprint = Blueprint('auth.ldap', __name__)