Re: Bug#892495: ITP: python3-aiohttp-swagger -- Swagger API Documentation builder for aiohttp server
- Date: Sat, 10 Mar 2018 18:26:52 +0000
- From: Ghislain Vaillant <ghisvail@xxxxxxxxx>
- Subject: Re: Bug#892495: ITP: python3-aiohttp-swagger -- Swagger API Documentation builder for aiohttp server
Le samedi 10 mars 2018 à 16:24 +0000, Joel Cross a écrit :
> > s/python3-aiohttp-swagger/python-aiohttp-swagger
> > for the name of the *source* package.
> > The python3- prefix is for the name of the *binary* package
> > targetting
> > the Python 3 interpreter.
> Oops, my apologies. I think 'aiohttp-swagger' would be the more
> appropriate name, do you agree? I will then use 'python3-aiohttp-
> swagger' as the binary package name (since the package will only be
> targeting Python 3).
It's up to you.
Tradiotionally, `python-foo` was used for Python libs and simply `foo`
for Python apps. Nowadays, people tend to stick to the upstream name,
unless it is too generic (for instance python-schema).
> > > I am interested in packaging a project that depends on this
> > > library,
> > > hence why
> > > I am packaging this library.
> > What's this project? Have you filed an ITP for it yet?
> The other project is one that has not yet been released under an
> open-source license, although I have it on good authority that it
> will be over the coming months. Sorry I can't tell you much more or
> file at ITP at present, but I will do as soon as I can.
Okay, then good luck with the packaging. I'd advise you to join and
maintain the package under the Debian Python Modules Team.