Strategy Design Pattern about axelrod HOT 3 CLOSED

Do we want to bother with this? The structure we have in place now would enable this to be done (I think), but it's still a fair amount of work as all the existing strategies would have to change.

In the short term, the main advantage would be to allow tournaments with more than one player executing the same strategy. If that's of interest, then I'll have a crack at it.

from axelrod.

In the short term, the main advantage would be to allow tournaments with more than one player executing the same strategy. If that's of interest, then I'll have a crack at it.

But this can already be done right?

import axelrod
P1 = axelrod.Cooperator()
P2 = axelrod.Cooperator()
P3 = axelrod.Cooperator()
P4 = axelrod.Defector()
A = axelrod.Tournament([P1, P2, P3, P4])
A.play().generate_scores()

Am I missing something?

Nice to keep this as an optional thing for once we've packaged this so people can run their own tournaments...

from axelrod.

True. Doesn't seem worth the effort at the moment, then.

Probably one to bear in mind in the run up to djangocon, if this gets in as a sprint.

from axelrod.