made PRs to postgrest-py to add proper sync support, and to add some pre-commit config

@User or @User , take a look when you can ☝️

ack

No, it is on the roadmap though

Noted, will take a look

😆 I'm on a bit of a PR spree here

I am trying to delete a record using supabase-py:

supabase.table('project_images').delete().filter(
                                                'project_id', 'eq', project_id).execute()

and I am receiving:

2021-10-26 17:06:41,402:ERROR - Traceback (most recent call last):
  File "/Users/titogarrido/Documents/Projetos/paint3/minination/minination-image-api/./main.py", line 363, in delete_project
    supabase.table('project_images').delete().filter(
  File "/Users/titogarrido/Documents/Projetos/paint3/minination/minination-image-api/venv/lib/python3.9/site-packages/supabase/lib/query_builder.py", line 33, in _execute_monkey_patch
    "data": response.json(),
  File "/Users/titogarrido/Documents/Projetos/paint3/minination/minination-image-api/venv/lib/python3.9/site-packages/requests/models.py", line 900, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/local/Cellar/python@3.9/3.9.7_1/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/usr/local/Cellar/python@3.9/3.9.7_1/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/Cellar/python@3.9/3.9.7_1/Frameworks/Python.framework/Versions/3.9/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

but I can't understand what I did wrong on this call... any clue?

seems that there is an issue open: https://github.com/supabase-community/supabase-py/issues/22

I would try to use the eq filter directly instead

@Tito

supabase.table('project_images').delete().eq('project_id', str(project_id)).execute()

@anand postgrest-py PR reviewed

changes made

code duplication is reduced via inheriting from a base client class

and honestly, adding unasync to recreate just one single method seems unnecessarily excessive

I see better auto-generated duplicated code than having an execute method that is synchronous and asynchronous at the same time. Because to use it without mypy showing an error for awaiting something that is not always awaitable, a cast would have to be performed whenever the execute method is used.

fair enough

does unasync preserve all types?

I think it will

It'll just not touch the annotations is what I inferred from reading about it

Okay, let's wait for leyniers PR to see how well it does, or if you think you can branch your current one you made a PR of and use unasync there, just so we don't wait for leynier. However you feel like depending on how busy you are 🙂

Ok, today later I will do a little PR so you can see unasync in action

thanks!

uhm, i'm quite sure that's a scam link. mods should probably delete that it's gone now

Hey - Just to be sure. The python client is not ready for production scale services, right?

Yeah I wouldn't use it just yet in anything critical. Works being done on it pretty quickly though!

Good - Looking forward to using it in the future!

Nope, anand is right. The client is not ready for production use at the moment. Do look out for updates w.r.t progress on launch week though 🙂

What is the best method to get only the last row from a table using python? Using the python client I tried to copy what was provided for JS, by doing something like:

python
data = supabase.table("test").select("*").order('id', { "ascending": False }).limit(1).execute()

But no luck (works when I remove the

.order()

).

.order

takes different parameters in postgrest-py I think; to get it in descending order you'd do

.order('id', desc=True)