Logger doesn't properly terminate when client is closed.

[Jolinator]

Summary

When closing the client object and creating a new one and connecting, the logger persists and repeats outputs. I'm guessing you need to remove the logger in or after client.close()?

Reproduction Steps

If you create a client instance, close it with await client.close(), reset the variables and the event handler, and run it again, the logger persists and repeats the connection message twice (logging in using a static token... etc.).

This is because it is attached to the module itself (_log = logging.getLogger(__name__) in gateway.py).

If you repeat this process 3 times you get 3 loggers and so on.

Minimal Reproducible Code

import discord
import asyncio
from time import sleep     
intents = discord.Intents.default()
client = discord.Client(intents=intents)
@client.event
async def on_ready():
    print(f'Logged in as {client.user} (ID: {client.user.id})')
    print('------')
    sleep(1)
    await client.close()

client.run(TOKEN)
sleep(2)
   
intents = discord.Intents.default()
client = discord.Client(intents=intents)
@client.event
async def on_ready():
    print(f'Logged in as {client.user} (ID: {client.user.id})')
    print('------')
    sleep(1)
    await client.close()
    
client.run(TOKEN)

Expected Results

2025-11-30 05:45:04 INFO discord.client logging in using static token
2025-11-30 05:45:05 INFO discord.gateway Shard ID None has connected to Gateway (Session ID: SESSION_ID_1).
Logged in as CLIENT_USER_OUTPUT (ID: ID_OUTPUT)

2025-11-30 05:45:10 INFO discord.client logging in using static token
2025-11-30 05:45:11 INFO discord.gateway Shard ID None has connected to Gateway (Session ID: SESSION_ID_2).
Logged in as CLIENT_USER_OUTPUT (ID: ID_OUTPUT)

Actual Results

2025-11-30 05:45:04 INFO discord.client logging in using static token
2025-11-30 05:45:05 INFO discord.gateway Shard ID None has connected to Gateway (Session ID: SESSION_ID_1).
Logged in as CLIENT_USER_OUTPUT (ID: ID_OUTPUT)

2025-11-30 05:45:10 INFO discord.client logging in using static token
2025-11-30 05:45:10 INFO discord.client logging in using static token
2025-11-30 05:45:11 INFO discord.gateway Shard ID None has connected to Gateway (Session ID: SESSION_ID_2).
2025-11-30 05:45:11 INFO discord.gateway Shard ID None has connected to Gateway (Session ID: SESSION_ID_2).
Logged in as CLIENT_USER_OUTPUT (ID: ID_OUTPUT)

Intents

discord.Intents.default()

System Information

• Python v3.13.5-final
• discord.py v2.6.4-final
• aiohttp v3.13.2
• system info: Windows 10 10.0.19045

Checklist

• I have searched the open issues for duplicates.
• I have shown the entire traceback, if possible.
• I have removed my token from display, if visible.

Additional Context

If it really is as simple as just closing the logger when closing the client I can do a PR maybe?

[pythonmcpi]

I'm pretty sure the issue is that client.run() unconditionally calls utils.setup_logging() here. To fix your example code, you'd pass log_handler=None during the second .run() call to suppress setting up logs again. I'm not sure if this behavior should be considered a library bug as .run() probably isn't meant to be called multiple times.

Another alternative would be to set up your event loop yourself, call utils.setup_logging() once on start, then use client.start() to start the bot.

[Jolinator]

There is many ways to work around the duplicated logger externally (clearing all loggers each loop, setting log_handler = None manually, create logger only initially with utils.setup_logging() etc.), I just thought this might be unintended. My specific bot needs to be able to end itself run non-async code and then reboot in scope (it even has a command to do just that) so I would also like to know if there is a better way to do it than creating a new client and closing it in a loop?