First, thank you Mathieu for the work you are doing. Although people might not publicly say it, there are lots of us still using web.py in various places who would love a Py3 version.
As to the actual question, I would put all of the DB related things as a very low priority. There is a lovely python db module entitled "Peewee" - http://docs.peewee-orm.com/en/latest/ , which very much fits right in with web.py (in spirit and technically). I would much rather see us push web.py py3 users to this module (which is actively maintained and updated) and drop the current DB support. Peewee has connection pooling <http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#pool>, support for Sqlite, MySQL, Postgres and others. It is extremely easy to use, and supports modern features. I've been using web.py and Peewee on a medium traffic site with great results for the past 1.5 years now. It has been rock solid and the way forward In my opinion. -James On Tue, Jun 21, 2016 at 5:06 AM, qyb <[email protected]> wrote: > In my opinion, DBUtils' connection pool is a important feature. > > On Tue, Jun 21, 2016 at 4:57 PM, Mathieu Xhonneux <[email protected]> > wrote: > >> Hi, >> >> I've been hired by the CS departement of the Université Catholique de >> Louvain (UCL, Belgium) to port web.py to Python 3. We're using the >> framework in some of our internal tools and we do need a Py3 upgrade for >> them. >> >> I've already done some work, available here : >> https://github.com/Zashas/webpy/tree/py3 >> We saw that Anand began the migration 3 years ago and decided to pursue >> his work (making the codebase compatible with Py2 and Py3, which seems to >> me the best option, btw Django manages it successfully). I integrated the >> commits he already wrote back then, ported all the unittests to Py3 and now >> I'm busy making them pass in both versions of Python. >> >> The ORM seems to be OK (I'm kinda hoping the tests' coverage is wide >> enough), but it originally supports some DB backends that are either no >> longer maintained, or not ported to Py3 : >> >> - psycopg1 : evolved to psycopg2, I'm guessing that not much people >> are using it these days >> - pysqlite2 : not ported to Py3 >> - MySQLdb : not ported to Py3, but mysqlclient seems to be compatible >> and to do the job fairly enough >> - DBUtils : not ported to Py3 >> >> Maybe we should consider dropping support for these ? Their presence is >> not doing any harm in the codebase, but I don't think that psycopg1 and >> pysqlite2 are still useful, and removing them could clean the code a bit. >> >> Anyway, if anyone wants to follow my work, I'm open to any remark, >> suggestion or patch. I'm hoping to have ported everything by friday, but it >> will definitively require some testing. >> >> Mathieu >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "web.py" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/webpy. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/webpy. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/webpy. For more options, visit https://groups.google.com/d/optout.
