Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #16600

Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC implementation for asyncio

From Simon Josefsson <simon@josefsson.org>
Newsgroups linux.debian.maint.python
Subject Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC implementation for asyncio
Date 2024-12-20 23:10 +0100
Message-ID <JVTm2-1c9a-31@gated-at.bofh.it> (permalink)
References <JVTm2-1c9a-33@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi Python Team,

I have prepared packaging of 'grpclib' and I'm new to Python packaging,
so I would appreciate open minded review of how this is packaged:

https://salsa.debian.org/python-team/packages/python-grpclib

Please bring up stylistic concerns, for me to learn.  I plan to upload
this to NEW shortly.

Some of the questions/concerns I have are:

- Do the /usr/bin binaries have to go in a separate package, or could
  they be in the python3-grpclib binary package?  I believe they are
  developer-only tools of limited applicability.

- Naming - right now it uses this style:

Source: python-grpclib
Package: python3-grpclib
Package: protoc-grpclib

  Does that make sense?  Upstream calls itself 'grpclib' but using
  'python-grpclib' in Debian seems nicer.  I see there is a
  'rustc-protoc' in the archive, maybe this should be
  'python-grpclib-protoc' instead?  Or 'protoc-python-grpclib'?  Or
  'protoc-grpclib-python'?

- This uses tarballs from pypi.debian.net, which isn't identical to
  upstream's GitHub git archive.  It seems tests/ are missing.  I've
  approached upstream about including them in the PyPI upload --
  https://github.com/vmagamedov/grpclib/issues/200 -- but I'm not sure
  what the best practices are here.  Is using the pypi.debian.net
  tarball recommended?  Or do people package the github.com tarball
  instead?  Or directly from git?  What do we do when some stuff is
  missing from the PyPI archive?

- Man pages are missing - the tools doesn't respond to -h or --help, I
  suppose this is an upstream request, or are there any other ideas on
  that?

- Others?

/Simon

Simon Josefsson <simon@josefsson.org> writes:

> Package: wnpp
> Severity: wishlist
> Owner: Simon Josefsson <simon@josefsson.org>
> X-Debbugs-Cc: debian-devel@lists.debian.org, debian-python@lists.debian.org
>
> * Package name    : python-grpclib
>   Version         : 2.0.0b7
>   Upstream Author : Vladimir Magamedov, et al
> * URL             : https://github.com/vmagamedov/grpclib
> * License         : BSD-3-Clause
>   Programming Lang: Python
>   Description     : Pure-Python gRPC implementation for asyncio
>
>  This is a Pure-Python gRPC implementation for asyncio.
>
> https://salsa.debian.org/python-team/packages/python-grpclib
>
> /Simon
>

Back to linux.debian.maint.python | Previous | NextNext in thread | Find similar


Thread

Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC  implementation for asyncio Simon Josefsson <simon@josefsson.org> - 2024-12-20 23:10 +0100
    Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC implementation for  asyncio Soren Stoutner <soren@debian.org> - 2024-12-21 18:40 +0100
    Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC  implementation for asyncio Simon Josefsson <simon@josefsson.org> - 2024-12-22 18:30 +0100
      Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC  implementation for asyncio Simon Josefsson <simon@josefsson.org> - 2024-12-23 11:00 +0100
      Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC  implementation for asyncio Julian Gilbey <julian@d-and-j.net> - 2024-12-23 21:10 +0100
        Re: Bug#1090912: ITP: python-grpclib -- Pure-Python gRPC  implementation for asyncio Simon Josefsson <simon@josefsson.org> - 2024-12-23 22:00 +0100

csiph-web