Войти в систему

Home
    - Создать дневник
    - Написать в дневник
       - Подробный режим

LJ.Rossia.org
    - Новости сайта
    - Общие настройки
    - Sitemap
    - Оплата
    - ljr-fif

Редактировать...
    - Настройки
    - Список друзей
    - Дневник
    - Картинки
    - Пароль
    - Вид дневника

Сообщества

Настроить S2

Помощь
    - Забыли пароль?
    - FAQ
    - Тех. поддержка



Пишет LWN.net ([info]syn_lwnheadline)
@ 2020-03-13 16:11:00


Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Varrazzo: Thinking psycopg3
Psycopg is the database adapter used
by most Python programs needing to work with the PostgreSQL database
manager. In this
blog post
, psycopg maintainer Daniele Varrazzo looks forward to the
next major version. "There is a chance now to rethink how thick the
C libpq wrapper should be. We can reduce the C implementation to a minimal
wrapper around the libpq (replaceable by a CFFI Python wrapper if compiling
C is not available on the client), using it as a foundation to build a
familiar DBAPI blocking interface. A blocking behaviour is not bad in
itself: it allows to write most of the programs, the ones which don't need
crazy concurrency, in a simple and familiar paradigm; the async layer would
be available under the hood to squeeze the best performance in programs who
have embraced an asynchronous pattern and framework.
"


(Читать комментарии) (Добавить комментарий)