#16331: Game Theory: Build capacity to solve matching games in to Sage.
-------------------------------------+-------------------------------------
Reporter: vinceknight | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.4
Component: game theory | Resolution:
Keywords: Game Theory, | Merged in:
Matching Games, | Reviewers: Karl-Dieter Crisman,
Authors: Vince Knight, | Travis Scrimshaw
James Campbell | Work issues:
Report Upstream: N/A | Commit:
Branch: | 17748d15c0b0c11044fb7696022d4143fe1056e4
u/vinceknight/game_theory__build_capacity_to_solve_matching_games_in_to_sage_|
Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by tscrim):
Replying to [comment:99 kcrisman]:
> Hmm, I don't feel terribly strongly about this per se, but if it causes
things to be equal that shouldn't, that's a problem. How is the
`loads(dumps(x)) == x` holding up with this? Maybe one needs to have a
warning of player equality being only name equality in that function's
doc, anyway.
We need to define `==` on both players and games otherwise pickling won't
construct an "equal" object (as far as python knows). While this is
probably not a major thing as games and players are not hashable, I find
it strange that I can create two games from the same input data that
aren't equal. Also I agree that there needs to be a warning that player
equality is based on name alone.
--
Ticket URL: <http://trac.sagemath.org/ticket/16331#comment:108>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
