Skip to content

Consider dropping custom Python operators #71

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

Open
pombredanne opened this issue Jun 19, 2017 · 3 comments
Open

Consider dropping custom Python operators #71

pombredanne opened this issue Jun 19, 2017 · 3 comments

Comments

@pombredanne
Copy link
Collaborator

@Kronuz @bastikr I am not sure that I have a need to build boolean expression using overloaded operators in Python and this introduces subtle bias and behaviors in many places.

Do you have a use for them? (as opposed to build an expression from a parsed string or building an expression from nested Python objects)

This would mean dropping the dunder methods from here:

def __and__(self, other):

__and__ , __mul__ , __invert__ , __or__ and __add__ and possibly __nonzero__ and __bool__

@pombredanne
Copy link
Collaborator Author

This would eventually keep the python boolean logic completely separate from this library boolean logic.

@pombredanne
Copy link
Collaborator Author

Alternatively, this could be something that could be made optional and not available on a systematic basis.

@pombredanne
Copy link
Collaborator Author

Ping? any feedback on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant