Leo Franchi 501f063426 Replace email_to_domain with split_email_to_domain and resolve_email_to_domain ... Now that we support email aliases, we have to be careful when going from an email address to a domain that we assume we can use to get a Realm object for. When we care about the Realm's domain, we want to follow any RealmAliases that exist for a certain domain. When we just care about the original email address domain itself, for comparison or other purposes, use split_email_from_domain This removes the ambiguity of having to decide when to use email_to_domain + RealmAlias or just email_to_domain (imported from commit 0e199495502d946ce2e1aae56263e7e8665be4ed)		2013-11-26 10:45:01 -05:00
..
__init__.py	[schema] Support for authenticating Deployments via the API.	2013-10-25 14:13:30 -04:00
create_deployment.py	Fix create_deployment not actually setting base_site_url.	2013-11-14 11:16:15 -05:00
grant_invites.py	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00
populate_db.py	Replace email_to_domain with split_email_to_domain and resolve_email_to_domain	2013-11-26 10:45:01 -05:00
print_initial_password.py	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00
profile_request.py	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00
render_old_messages.py	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00
sync_api_key.py	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00
test_messages.txt	Split management commands for internal use into zilencer/	2013-11-04 11:58:52 -05:00