Bump jishaku from 1.20.0.220 to 2.3.0

[dependabot]

Bumps jishaku from 1.20.0.220 to 2.3.0.

Release notes

Sourced from jishaku's releases.

jishaku 2.3.0

https://pypi.org/project/jishaku/2.3.0/ https://github.com/Gorialis/jishaku/tree/2.3.0 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-3-0

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

Install specifically this version of jishaku (not recommended):

pip install -U jishaku==2.3.0

Artifacts are included with this release for debugging convenience.

jishaku 2.2.0

https://pypi.org/project/jishaku/2.2.0/ https://github.com/Gorialis/jishaku/tree/2.2.0 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-2-0

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

Install specifically this version of jishaku (not recommended):

pip install -U jishaku==2.2.0

Artifacts are included with this release for debugging convenience.

jishaku 2.1.0

https://pypi.org/project/jishaku/2.1.0/ https://github.com/Gorialis/jishaku/tree/2.1.0 https://jishaku.readthedocs.io/en/latest/whatsnew.html#version-2-1-0

It is advised that you install jishaku directly through the pip package manager.

Install the latest version of jishaku:

pip install -U jishaku

... (truncated)

Changelog

Sourced from jishaku's changelog.

Version 2.3.0

As discord.py development has ceased, this update serves to set the expectations for Jishaku going forward.

I have already gone over everything in my README writeup, so I will reproduce it here for your convenience.

As of the 27th of August 2021, `discord.py has ceased development <https://gist.github.com/Rapptz/4a2f62751b9600a31a0d3c78100287f1>`_.
Jishaku will continue to be maintained targeting both the PyPI version and the latest git revision &lt;https://github.com/Rapptz/discord.py/tree/45d498c1b76deaf3b394d17ccf56112fa691d160&gt;_ as of the archive, until at least the date of the slash command mandate (currently speculated to be around April 2022).
As all trusted contributors have rejected continuing the library, I do not have enough trust in any forks to target those instead. The existing forks are handled by inexperienced developers, and I figure this will continue to be the case in the future, as all of the developers experienced enough to carry the torch do not want to maintain the library for similar reasons to Danny himself.
However, if you personally decide that you wish to use a fork, I will allow Jishaku to honor your decision by removing the discord.py package requirement. This means, from now on, installing jishaku will not automatically handle installing discord.py, you must choose a version to use yourself. Any fork that you use must be compatible with the original (in that it supplies the discord module and its namespaces).
When April 2022 comes, I will make a decision at the time as to whether I want to continue maintaining Jishaku. I still enjoy making and maintaining bots, but implementing Jishaku under the philosophies I have defined so far will likely be impossible under the new slash commands, and I don't really want to compromise my work for the sake of appeasing a company that doesn't care for its developers.
I hope you've found Jishaku useful, and hopefully it will get to live on in one way or another.

Version 2.2.0

The jsk sudo, jsk su and jsk in commands have been removed and replaced with a single command that handles all three at once.

jsk exec now automatically handles IDs or mentions for channels, users, or threads (only with discord v2.0a+). Aliases with a postfix ! bypass checks and cooldowns, like jsk sudo used to do.

Example of how the commands change with this release:

• jsk su @user command -> jsk exec @user command
• jsk in #channel command -> jsk exec #channel command
• jsk in #channel jsk su @user command -> jsk exec #channel @user command or jsk exec @user #channel command
• jsk sudo command -> jsk exec! command

This allows combinations that were previously not possible, for example, jsk exec! #channel @user command now executes a command as a user in another channel or thread, bypassing any checks or cooldowns that user or channel has against the command.

The flag system (i.e. the JISHAKU_FLAG=... system) has been rewritten to use various degrees of lazy evaluation. This means setting flags like JISHAKU_HIDE and JISHAKU_RETAIN need only precede loading the Jishaku extension, as opposed to the entire module.

Flags that only evaluated at command runtime will now have their changes take effect immediately. For example, executing os.environ['JISHAKU_NO_UNDERSCORE'] = '1' no longer requires a reload to take effect.

A programmatic interface for flags is available, however, its use is discouraged except in subclass initialization, due to the fact that the changes will NOT persist across reloads of the extension.

.. code:: python3

jishaku.Flags.NO_UNDERSCORE = True

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)