special method __neq__ is actually called __ne__
Closed this issue · 2 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. Vector2 and Vector3 implement the special method __neq__
2. I assume that actually __ne__ was meant.
3. I attached the trivial patch
Original issue reported on code.google.com by lorenz.q...@gmail.com
on 20 Apr 2009 at 7:58
Attachments:
GoogleCodeExporter commented
I encountered this problem, too. Do you have any plans to fix this?
Original comment by mikke...@gmail.com
on 29 Aug 2009 at 12:13
- Added labels: ****
- Removed labels: ****
GoogleCodeExporter commented
Thanks for the report. Fixed now.
Original comment by tart...@gmail.com
on 26 Aug 2010 at 2:30
- Changed state: Fixed
- Added labels: OpSys-All
- Removed labels: ****