aio-libs / aio-libs/aiopg

Roadmap after psycopg3 release

Aberta
#889 2 comentários 5 reações 0 responsáveis Ver no GitHub
enhancement question
Linguagem predominante
Python
Estrelas
1.4k
Forks
170
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

### Is your feature request related to a problem?

With the release of psycopg3 and its async capabilities, isn't this wrapper for the good-old synchronous psycopg2 unnecessary anymore?

### Describe the solution you'd like

At least I'd expect aiopg to mention its relation with psycopg3 and maybe declare sunset?

### Describe alternatives you've considered

During the timespan where other libraries that could rely on aiopg won't yet move to psycopg3, maybe aiopg2 should become a thin wrapper for psycopg3? E.g. SQLAlchemy won't support psycopg3 until their 2.0 release https://github.com/sqlalchemy/sqlalchemy/milestone/88

### Additional context

_No response_

### Code of Conduct

- [X] I agree to follow the aio-libs Code of Conduct

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.