Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

obj.locks.get('access_type') doesn't return a string #282

Closed
Griatch opened this issue Jan 22, 2014 · 2 comments
Closed

obj.locks.get('access_type') doesn't return a string #282

Griatch opened this issue Jan 22, 2014 · 2 comments
Labels
bug An actual error or unwanted behavior.

Comments

@Griatch
Copy link
Member

Griatch commented Jan 22, 2014

From daniel@benoy.name on October 03, 2012 03:53:31

A) What steps will reproduce the problem? @py self.locks.get('puppet') B) What is the expected output? What do you see instead (tracebacks, error messages)? The documentation says it returns a string, but apparently it returns something else.

self.locks.get('puppet')
<<< (u'%s or %s or %s', ((<function id at 0x1cac140>, [u'#1'], {}), (<function perm at 0x1ca8de8>, [u'Immortals'], {}), (<function pperm at 0x1ca8ed8>, [u'Immortals'], {})), u'puppet:id(#1) or perm(Immortals) or pperm(Immortals)') C) What version/revision of Evennia are you using? On what operating system? Give as much information as possible to make it easier for developers to recreate the problem. Latest version from mercurial at the time of bug filing. D) Please provide any additional information or suggestions below. I want to check to see if a specific check's lock string has a specific value. It seemed by the documentation that 'get()' was what I needed. Let me know if there's a better option.

Original issue: http://code.google.com/p/evennia/issues/detail?id=282

@Griatch
Copy link
Member Author

Griatch commented Jan 22, 2014

From daniel@benoy.name on October 02, 2012 19:33:22

I did self.locks.get('puppet')[2] and got the expected results.

@Griatch
Copy link
Member Author

Griatch commented Jan 22, 2014

From griatch on October 14, 2012 03:40:38

This issue was closed by revision ec0fc57f1af4 .

Status: Fixed

@Griatch Griatch closed this as completed Jan 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An actual error or unwanted behavior.
Projects
None yet
Development

No branches or pull requests

1 participant