Hi Nadar,

we do have a set of things scheduled for a version 3.0 of
the DB API (see the python.org wiki), but nothing related to
async I/O yet.

FWIW: I think the existing APIs can be used in an async form
as well, without having to specify new ones, by simply
providing an async entry point at the module level or
even making the DB module itself be async only.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/



On 11.10.2018 21:48, Nader Hamady wrote:
> Hello.
> 
> Reaching out to find out if there have been any discusdions around a 3.0
> Database API Specification - Or something broader around async
> specifications for dabatase transactions.
> 
> Thanks in advance,
> 
> -N
> 
> 
> 
> Hello.
> 
> Reaching out to find out if there have been any discusdions around a 3.0
> Database API Specification - Or something broader around async
> specifications for dabatase transactions.
> 
> Thanks in advance,
> 
> -N
>   
> -- 
> Nader B. Hamady
> 
> 
> _______________________________________________
> DB-SIG maillist  -  DB-SIG@python.org
> https://mail.python.org/mailman/listinfo/db-sig
> 

_______________________________________________
DB-SIG maillist  -  DB-SIG@python.org
https://mail.python.org/mailman/listinfo/db-sig

Reply via email to