Hello!
I am currently reviewing the Debian packaging at
https://salsa.debian.org/python-team/packages/python-jsonrpc-server of
the upstream project https://github.com/palantir/python-jsonrpc-server
Upstream uses 'python-jsonrpc-server' as the repository and also the
pip package name. Should we
Hi Otto,
* Otto Kekäläinen [2020-11-01 19:36]:
Upstream uses 'python-jsonrpc-server' as the repository and also the
pip package name. Should we follow that in Debian or perhaps use the
alternative name 'python3-pyls-jsonrpc'?
Is there some existing naming convention/policy about Python
On 2020-11-01 20:23:20 +0100 (+0100), Thomas Goirand wrote:
[...]
> However, if I am to put more efforts on stuff like that, my priority
> would be first on getting the reno release notes published in the Debian
> package. I've been thinking about this for a long time, and haven't
> figured out
> New/correct address is:
> Maintainer: Debian Python Team
Thanks. Now that this is clear I'll proceed to update it to all of the
packages I am involved in.
Hi!
> When you say "follow that", do you mean for the Debian source package
> name (.dsc, like dbus-python), or for the Debian binary package name
> (.deb, like python3-dbus)?
We'll go with 'python3-pyls-jsonrpc' for the binary package.
> The binary package name should be mechanically derived
On Sun, 01 Nov 2020 at 19:36:52 +0200, Otto Kekäläinen wrote:
> I am currently reviewing the Debian packaging at
> https://salsa.debian.org/python-team/packages/python-jsonrpc-server of
> the upstream project https://github.com/palantir/python-jsonrpc-server
>
> Upstream uses
On 10/31/20 1:10 PM, Jeremy Stanley wrote:
> On 2020-10-31 12:03:50 +0100 (+0100), Thomas Goirand wrote:
> [...]
>> On 10/31/20 3:07 AM, Jeremy Stanley wrote:
>>> I have to agree, though in the upstream projects with which I'm
>>> involved, those generated files are basically a lossy re-encoding
7 matches
Mail list logo
