Caelia Renee Chapin

Actually, I guess that change should be in SequenceRowStack rather than SS_RowStack. Also, on further thought, I guess this can't do any harm, since for any given version of Python there should never be any ambiguity in method resolution, i.e. every subclass of SequenceRowStack should be affected the same way, right?

Okay, I've taken a look at the code, and I believe I have found a better answer. [I'm hesitant to say it is the solution, since I haven't done any serious work in Python for over a decade, and have never looked at the Pysol codebase before] The issue seems to arise from the difference in method resolution between old- and new- style classes. I determined this by going back to the v2.1 source code and comparing program behavior between Python2 and Python3. And I found that under Python2, ScorpionRowStack.canMoveCards...

Okay, I've taken a look at the code, and I believe I have found a better answer. [I'm hesitant to say it is the solution, since I haven't done any serious work in Python for over a decade, and have never looked at the Pysol codebase before] The issue seems to arise from the difference in method resolution between old- and new- style classes. I determined this by going back to the v2.1 source code and comparing program behavior between Python2 and Python3. And I found that under Python2, ScorpionRowStack.canMoveCards...