Closed dolfies closed 2 years ago
Thank you for all your work in maintaining this library. <3
2.0 will never release now anymore though, as official discord.py development has stopped. So maybe that changes the future quite a bit? And now official bots are becoming more restricted than ever, with required slash commands only and similar apparently in the future, so this will be very different from the official discord.py if it would start existing again. So I guess you will just continue development of the now abandoned 2.0 but in a self bot direction, which would lead to not needing to do many changes (as that isn't changing much yet)?
Wow. Apparently a clusterfuck took place overnight.
I will definitely continue development. I'm pretty sure I'll be able to maintain the library itself (even without upstream existing anymore), but I'm worried about typing.
Discord.py has added type-checking to the entire library, and I don't know if I'm up to the task of maintaining and fixing the bugs related to that (on top of having to type the code I write).
I'm sure that this library is going to be getting more attention now that Discord is fucking over bots, so contributors (especially related to typing) are greatly appreciated.
UPDATE: Now that I'm back from vacation, I'm beginning to work on v2.0.
There's probably going to be one more version before 2.0 with some bugfixes.
What will happen with v2.0?
Some people have been asking if this fork will be updated to discord.py v2.0.
I talked about this in my previous announcement but I'll discuss it in more detail here.
Short answer:
Yes.
Long answer:
v2.0 has a huge amount of changes, and drops the incomplete support discord.py had for the user API.
In order to update this fork to v2.0, I'll need to:
You can probably guess that this won't be fast.
However, since I'm starting now (while the new version is in alpha), the fork's v2.0 won't be far behind the official release of v2.0.
~Dolfies