From 06d680cded4b4601b10018ff83f7c19049bedb3e Mon Sep 17 00:00:00 2001 From: Calen Pennington Date: Wed, 21 May 2014 14:38:16 -0400 Subject: [PATCH] Don't use Empty directly, let the manager handle it --- common/djangoapps/student/roles.py | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/common/djangoapps/student/roles.py b/common/djangoapps/student/roles.py index 26bb5941d1..cd69ed385d 100644 --- a/common/djangoapps/student/roles.py +++ b/common/djangoapps/student/roles.py @@ -72,7 +72,7 @@ class RoleBase(AccessRole): """ Roles by type (e.g., instructor, beta_user) and optionally org, course_key """ - def __init__(self, role_name, org='', course_key=CourseKeyField.Empty): + def __init__(self, role_name, org='', course_key=None): """ Create role from required role_name w/ optional org and course_key. You may just provide a role name if it's a global role (not constrained to an org or course). Provide org if constrained to @@ -81,9 +81,6 @@ class RoleBase(AccessRole): """ super(RoleBase, self).__init__() - if course_key is None: - raise TypeError('course_key must be CourseKeyField.Empty or a valid CourseKey') - self.org = org self.course_key = course_key self._role_name = role_name