You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the past owner owner of the package (see PyPI author). We've since renamed the supabase_py pypi namespace to supabase and we want to delete all traces of the past package supabase_py so devs don't get confused. Unfortunately, while deleting the package we neglected to account for one of the versions 0.0.2 and we are currently unable to delete the package.
We would like to reacquire the namespace so we can delete the package entirely
We believe the last remaining version of the package is owned by fedden (GH username), once of the past maintainers. We attempted contacting him via Github and email but were unable to reach him.
Let us know if further information is needed.
Thanks!
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project to be claimed
PROJECT_NAME
: https://pypi.org/project/supabase-pyYour PyPI username
USER_NAME
: https://pypi.org/user/joelleeReasons for the request
I'm the past owner owner of the package (see PyPI author). We've since renamed the
supabase_py
pypi namespace tosupabase
and we want to delete all traces of the past packagesupabase_py
so devs don't get confused. Unfortunately, while deleting the package we neglected to account for one of the versions 0.0.2 and we are currently unable to delete the package.We would like to reacquire the namespace so we can delete the package entirely
Maintenance or replacement?
Maintenance
Source code repositories URLs
Active repository: https://github.com/supabase-community/supabase-py/issues
Contact and additional research
We believe the last remaining version of the package is owned by fedden (GH username), once of the past maintainers. We attempted contacting him via Github and email but were unable to reach him.
Let us know if further information is needed.
Thanks!
Code of Conduct
The text was updated successfully, but these errors were encountered: