-
-
Notifications
You must be signed in to change notification settings - Fork 366
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When using create_client()
from supabase-py
, the following DeprecationWarnings appear even though I do not pass timeout
or verify
parameters:
DeprecationWarning: The 'timeout' parameter is deprecated. Please configure it in the http client instead.
DeprecationWarning: The 'verify' parameter is deprecated. Please configure it in the http client instead.
These warnings are triggered internally by the SDK’s _init_postgrest_client
function.
To Reproduce
import os
from dotenv import load_dotenv
from supabase import create_client ,Client
load_dotenv()
SUPABASE_URL = os.environ.get("SUPABASE_URL")
SUPABASE_SERVICE_ROLE_KEY = os.environ.get("SUPABASE_SERVICE_ROLE_KEY")
supabase: Client = create_client(SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY)
data = supabase.table("reports").select("*").execute()
- No
timeout
orverify
parameters are passed by the user. - Warnings appear when
.execute()
is called to make a request.
Expected behavior
- No
DeprecationWarning
should appear unless the user explicitly passes deprecated parameters. - Internally, the SDK should avoid passing
timeout
andverify
toSyncPostgrestClient
and instead use thehttp_client
configuration.
Screenshots
N/A
System information
- OS: Windows
- Version of supabase-py: 2.21.1
- Python version: 3.13
- Browser: N/A
Additional context
- The warning is coming from the SDK internals (
_init_postgrest_client
→SyncPostgrestClient
).
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working