Skip to content

Commit 1f4169b

Browse files
fix(content): remove shim references (#49)
1 parent 0248240 commit 1f4169b

File tree

1 file changed

+1
-38
lines changed

1 file changed

+1
-38
lines changed

guide/docs/prerequisites/migrating-from-dpy.mdx

+1-38
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ As discussed above, rewriting your code from an older `discord.py` version to `d
7171
changes. But if you're migrating from `discord.py 2.0`, all that's left now is changing the library references
7272
throughout the code, since the base code for both the libraries is practically the same.
7373

74-
There are three ways to switch between libraries:
74+
There are two ways to switch between libraries:
7575

7676
#### Replace `discord` with `disnake`
7777

@@ -95,42 +95,5 @@ import disnake as discord
9595
from disnake.ext import commands
9696
```
9797

98-
#### Using the `discord` shim
99-
100-
Using the `discord` shim allows you to use `disnake`, without the need to import it directly or importing it as
101-
discord - thus eliminating the need to change your code at all. To install the shim, you can use the following command
102-
in your terminal:
103-
104-
<Tabs groupId="operating-systems">
105-
<TabItem value="windows" label="Windows">
106-
107-
```
108-
py -3 -m pip install disnake[discord]
109-
```
110-
111-
</TabItem>
112-
<TabItem value="macos" label="macOS">
113-
114-
```
115-
python3 -m pip install disnake[discord]
116-
```
117-
118-
</TabItem>
119-
<TabItem value="linux" label="Linux">
120-
121-
```
122-
python3 -m pip install disnake[discord]
123-
```
124-
125-
</TabItem>
126-
</Tabs>
127-
128-
:::warning
129-
130-
We don't recommend using the shim, as it is updated less frequently and may break the behaviour of
131-
interactions/components in some cases. If possible, proceed with one of the other two procedures mentioned.
132-
133-
:::
134-
13598
And that's it! Since `disnake` is a fork of `discord.py`, it inherits a lot of similarities - though we recommend you to
13699
always run your code to fix any possible issues.

0 commit comments

Comments
 (0)