Skip to content
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

Officially support two-stage-bot, Trigger CI #107

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tae898
Copy link
Member

@tae898 tae898 commented Nov 23, 2023

We've only used this in testing, but it turns out that this is a useful feature.

@tae898 tae898 requested a review from miselico November 23, 2023 11:01
"""Bot which plays first the one, than the other startegy"""

def __init__(
self, bot1: Bot, bot2: Bot, name: Optional[str] = "ProbabilityBot"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you remove this default value?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops sorry . removed!

@miselico
Copy link
Contributor

I am overall in favor of having this. What I am a bit worried about is what to do with the trump and game end notification parts. This way they would go no-where, even if the underlying bots have an implementation.

This would mean that these could not be used out of the box for things like training a ML bot.

Second minor point is to immediately include the usage of this class in the test cases you refer to, to reduce code duplication.

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

Successfully merging this pull request may close these issues.

2 participants