supabase-py
supabase-py copied to clipboard
chore: Tox configuration scripts
What kind of change does this PR introduce?
Project maintenance, dev workflow enhancement.
What is the current behavior?
https://github.com/supabase-community/supabase-py/issues/696
What is the new behavior?
Move away from Makefiles to tox configuration scripts. tox is tailor made for python projects compared to Makefiles and allows for venv management and test automation + standardization in CI workflows.
For eg, the below config will run our tests against multiple python environments, to help guard against any breaking changes we introduce and thus ensuring backward compatibility.
[tox]
isolated_build = True
envlist = format, py37, py38, py39, py310, py311, py312
Additional context
Tests against all supported versions can be launched using a single tox command and optionally running tests against specific versions is also supported using the tox -e argument.
Sorry for the noise, CI finally looks green ✅
@mansueli , @J0 -- any further thoughts on this?
Hey @tinvaan,
I'll have a deeper look soon and get back
Resolved merge conflicts & painted CI green again.
/cc @J0
@tinvaan,
Thanks for the PR! I think the maintaining team will need to look through this before we can decide whether to move forward as it affects the development flow. It may take a while.
cc: @silentworks @mansueli
Closing this PR for the reasons given on https://github.com/supabase/supabase-py/issues/696#issuecomment-2306620767.