Re: Bug#890523: ITP: python3-anosql -- A Python library for using SQL
Le jeudi 15 février 2018 à 10:05 -0500, Florian Grignon a écrit :
> Package: wnpp
> Severity: wishlist
> Owner: Florian Grignon <email@example.com>
> * Package name : python3-anosql
The name for the source package should use the python- prefix as in
Python the language. The python3- prefix is intended for the binary
package providing the modules for the Python 3 interpreter.
> Version : 0.2.0
> Upstream Author : Honza Pokorny <firstname.lastname@example.org>
> * URL : https://github.com/honza/anosql
> * License : BSD
> Programming Lang: Python
> Description : A Python library for using SQL
> A Python library for using SQL.
> Inspired by the excellent Yesql library by Kris Jenkins. In my mother
> tongue, ano means yes.
> This Python library is becoming popular amoung the Python community
> working with PostgreSQL and SQLite. This library has currently
> (15/02/2018) 66 stars github, and is referenced in some books (like
> MasteringPostgreSQL from Dimitry Fontaine). The library is simple and
> small. It is tested on Travis CI, and has a github repository
> I am an experienced Python web developper, and I use this library in
> small personnal project, alongside Flask and psycopg2. This is, from
> these three libraries the only one I'm packaging myself with the
> buildsystem. I took example on the Flask packaging system and it
> like a charm out of the box.
> This library is a very small library that helps Python project to use
> raw SQL queries. This can be seen as a competitor of ORM. And as
> performance becomes more and more important with the size of a Python
> project, the need to use raw SQL instead of ORM becomes inevitable.
> Raw SQL queries also gives much more flexibility and features to the
> developper compared to the ORM.
> This library doesn't have any dependencies. It can be used alongside
> psycopg2 for PostgreSQL or sqlite for SQLite databases engine.
> As a full-time computer scientist, I have time to create and maintain
> on my professionnal and personnal time. I will search for a sponsor
> guide me through the steps of creating and maintaining a debian
> I'd like to include the package, in a second time, to the Debian
> Module Team, and include myself to the team.
Thank you for the comprehensive description and personal motivation.
You did not mention why this package needs to be packaged though (as
opposed to being installed via pip). Is it required by another package
(or upcoming update of) currently in the archive?