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


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

Re: How to watch pypi.org

Path csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!news.dns-netz.com!news.freedyn.net!aioe.org!bofh.it!news.nic.it!robomod
From Thomas Goirand <zigo@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: How to watch pypi.org
Date Sat, 31 Oct 2020 12:10:01 +0100
Message-ID <B5WVH-71D-3@gated-at.bofh.it> (permalink)
References <AWe7v-7OL-5@gated-at.bofh.it> <AWoqe-65e-9@gated-at.bofh.it> <B5Dq2-3F1-5@gated-at.bofh.it>
X-Original-To Debian Python <debian-python@lists.debian.org>
X-Mailbox-Line From debian-python-request@lists.debian.org Sat Oct 31 11:04:08 2020
Old-Return-Path <zigo@debian.org>
X-Amavis-Spam-Status No, score=-7.257 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, NICE_REPLY_A=-0.257] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -3.5
Organization Debian
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version 1.0
Content-Type text/plain; charset=utf-8
Content-Language en-US
Content-Transfer-Encoding 7bit
X-Mailing-List <debian-python@lists.debian.org> archive/latest/18754
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/a95cae00-b052-e8ac-5ce0-a9f0d521f03c@debian.org
Approved robomod@news.nic.it
Lines 40
Sender robomod@news.nic.it
X-Original-Date Sat, 31 Oct 2020 12:03:50 +0100
X-Original-Message-ID <a95cae00-b052-e8ac-5ce0-a9f0d521f03c@debian.org>
X-Original-References <CAOh_QLeAesodC=CCL9pNO3zjBG8T2GC4rHjtOKRE0v2MLTonfA@mail.gmail.com> <CAKTje6Eq_bJssv7KFCxnRFV4wKOZLd2veUX4JRgEZAoaKZ3Wag@mail.gmail.com> <CAOh_QLfPqLvvXVCHxro9POY54TStvThJTpuNAQbfqJ0Lp=-Msw@mail.gmail.com>
Xref csiph.com linux.debian.maint.python:12990

Show key headers only | View raw


On 10/30/20 3:18 PM, Fioddor Superconcentrado wrote:
> As I said I'm very new to this and all (python) packages I'm using
> lately use the usual python tools (pipy, setup.py, etc) and my first
> approach has been to stick as close as possible to the upstream
> procedures. But I might very likely be taking a wrong decision. What are
> the reasons to go for git instead of pypi? I see that it is 'more
> upstream' but it seems that everyone else is pointing to pypi as a
> distro-agnostic solution.

Pypi is often thought as a Python module source repository. It is *NOT*.
It is a repository for binaries to be consumed by pip. Therefore, the
tarballs may omit some artifacts, and add some more. For example, it's
preferable that the sources do not include the egg-info folder, or
pre-generated documentation. These must be built from source.

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 of
> metadata from the Git repositories themselves: AUTHORS file
> generated from committer headers, ChangeLog files from commit
> subjects, version information from tag names, and so on. Some of
> this information may be referenced from copyright licenses, so it's
> important in those cases for package maintainers to generate it when
> making their source packages if not using the sdist tarballs
> published by the project.

Unfortunately, the FTP masters do not agree with you. I've been told
that the OpenStack changelog is a way too big, and it's preferable to
not have it in the binary packages. Also, there's nothing in the Apache
license that mandates having an AUTHORS list as per what PBR builds. If
we are to care that much in OpenStack, then the license must be changed.

In Debian, quite the opposite, and like it or not (I personally don't
really feel the policy is right, but that's how it is), what Debian
cares is what's in the source code marked with "copyright (c) yeah,
copyright-holder", and this must already be in debian/copyright.

Cheers,

Thomas Goirand (zigo)

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-04 17:30 +0200
  Re: How to watch pypi.org Geert Stappers <stappers@stappers.nl> - 2020-10-04 17:50 +0200
    Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:10 +0100
  Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-04 17:50 +0200
    Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:10 +0100
  Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-05 04:30 +0200
    Re: How to watch pypi.org Scott Kitterman <debian@kitterman.com> - 2020-10-05 05:10 +0200
      Re: How to watch pypi.org, example Geert Stappers <stappers@stappers.nl> - 2020-10-05 08:20 +0200
    Re: How to watch pypi.org Fioddor Superconcentrado <fioddor@gmail.com> - 2020-10-30 15:20 +0100
      Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-30 15:30 +0100
      Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-31 02:40 +0100
        Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 03:40 +0100
          Re: How to watch pypi.org Paul Wise <pabs@debian.org> - 2020-10-31 05:30 +0100
      Re: How to watch pypi.org Thomas Goirand <zigo@debian.org> - 2020-10-31 12:10 +0100
        Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 13:20 +0100
          Re: How to watch pypi.org Thomas Goirand <zigo@debian.org> - 2020-11-01 20:30 +0100
            Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-11-01 21:10 +0100
        Re: How to watch pypi.org Andrey Rahmatullin <wrar@debian.org> - 2020-10-31 15:50 +0100
          Re: How to watch pypi.org Jeremy Stanley <fungi@yuggoth.org> - 2020-10-31 18:40 +0100

csiph-web