Use case of this library only for self-bots?

[sla-te]

I have a couple projects where I utilize selfbots as well as regular bots to make some use cases work properly. - Earlier I had my own fork of discord.py that I mainted and enhanced with stuff for self-botting. - Now im not sure but as far as I can tell all bot-related features are being removed in this fork, is that right? So basically id have to use this fork for self-bots and a different fork for actual bots.

So if what I explained above is correct, that would it be considerable to rename the package to discord_self or something alike, so that it is possible to install this work together with another fork and import from them separately, as in:

import discord_self
import discord

class MyBot(discord.Client)
    pass

class MySelfBot(discord_self.Client)
    pass

or am i missing something obvious, that I could utilize to make this work? As far as I know it might not be too cool to install two packages with the same name "discord" in the same venv and it probably doesnt work as well because you cant import from them properly anymore as import discord would reference both of these packages.

[caiocinel]

There's a renamed branch that change package to selfcord.

https://github.com/dolfies/discord.py-self/tree/renamed

[sla-te]

Ah, I missed that one, ugh, have to rewrite all changes I had already applied in my fork to the development branch. It will be hard to keep that branch up to date with the development branch, maybe should make this branch the new default?

[sla-te]

Rebased development in now, was quicker than I thought x)

[dolfies]

Is there a specific reason you're using development? renamed is already based on the latest released (stable) version.

[sla-te]

Hmm, not really I just like to be up to date but already figured it will be wiser to use the current version of the renamed branch

[dolfies]

Yeah, development is really volatile. I don't recommend using it unless you need one of the changes.