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
Migrate Dayong's design model and implement slash commands #4
Labels
Comments
huenique
added
enhancement
New feature or request
question
Further information is requested
labels
Aug 29, 2021
Go for #3 |
huenique
added a commit
that referenced
this issue
Sep 21, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Sep 27, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 11, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 12, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 12, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 12, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 12, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 12, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
huenique
added a commit
that referenced
this issue
Oct 13, 2021
- Switch bot framework from discord.py to hikari - Use pydantic for data type validation - Use rich for prettier console logging - Add settings module for storing constants used accross Dayong's modules - Rename extensions directory from cogs to components - Separate bot config from bot session - Implement interfaces NOTE: For interfaces, see PEP 544 -- Protocols: Structural subtyping (static duck typing)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The sole maintainer of discord.py has ceased the development of their API wrapper. This is my first time making a complete discord bot, so I wasn't aware of this matter.
The reason I chose discord.py was because of its popularity and that it was a fast and mature library. Now that discord.py is essentially dead, we're left with a few options:
If you read Danny's announcement, Discord is forcing bot developers to use slash commands. Dayong will die in 8 or 9 months if we continue using discord.py's design model.
Regarding our remaining options, from a project maintainer's point of view, the first one sounds like our top choice, but we don't have to abandon Python just yet. Personally, I think the second or third is our best option. For number 2, I'm looking into other libraries, such as hikari, which is starting to gain traction after the announcement. For number 3, there's discord-interactions, which is a discord.py extension for supporting slash commands.
The text was updated successfully, but these errors were encountered: