getUserNames() raises when no user found

Request	LDAP User Folder -- bug report -- by P.-J. Grizel
Posted on	Jun 1, 2005 4:55 am
Subscribe	Enter your email address to receive mail on every change to this issue.

	Resolve by Jens Vagelpohl on Jun 1, 2005 5:21 am
	`Hi Pierre-Julien, This was fixed in CVS for getUserNames already, and I just added fixes for the remaining places. Please test CVS HEAD and let me know if there are any problems. Thanks! jens`


	Initial Request by P.-J. Grizel on Jun 1, 2005 4:55 am
	`See the following code snippet in getUserNames() : loginlist = self.getAttributesOfAllObjects( self.users_base, ldap_scopes[self.users_scope], user_filter, (self._login_attr,))[self._login_attr] if the getAttributesOfAllObjects() call return an empty dictionnary (which is the case if no user is found), this code raises instead of returning an empty list. The problem exists (at least) in getUserNames(), getUserIds() and getUserIdsAndNames() methods.`

dataflake.org