Re: PyPI source or github source?

To: debian-python@lists.debian.org
Subject: Re: PyPI source or github source?
From: Brian May <bam@debian.org>
Date: Sat, 18 Mar 2017 17:37:43 +1100
Message-id: <[🔎] 87efxvf5u0.fsf@prune.linuxpenguins.xyz>
In-reply-to: <[🔎] 33ab6218-ea1a-bed7-6a57-fbccf9cf7c74@debian.org>
References: <[🔎] 85r323gw48.fsf@benfinney.id.au> <[🔎] 874lyzi6d9.fsf@prune.linuxpenguins.xyz> <[🔎] CAKTje6GfiRvwTLqMcZ9CvxTQefYXidkMRG+2-k=Lvdhb03jFnA@mail.gmail.com> <[🔎] 1489314850.2669.18.camel@gmail.com> <[🔎] 33ab6218-ea1a-bed7-6a57-fbccf9cf7c74@debian.org>

Thomas Goirand <zigo@debian.org> writes:

> IMO, upstream are right that the PyPi releases should be minimal. They
> are, from my view point, a binary release, not a source release.

To go against this, often PyPI releases contain *.pyc files. Looking at
django-filter 0.13.0 right now.
-- 
Brian May <bam@debian.org>

Reply to:

References:
- GnuPG signatures on PyPI: why so few?
  - From: Ben Finney <bignose@debian.org>
- PyPI source or github source?
  - From: Brian May <bam@debian.org>
- Re: PyPI source or github source?
  - From: Paul Wise <pabs@debian.org>
- Re: PyPI source or github source?
  - From: Ghislain Vaillant <ghisvail@gmail.com>
- Re: PyPI source or github source?
  - From: Thomas Goirand <zigo@debian.org>

Prev by Date: Re: Updating Celery, Kombu, python-amqp
Next by Date: Re: Updating Celery, Kombu, python-amqp
Previous by thread: Re: PyPI source or github source?
Next by thread: Re: PyPI source or github source?
Index(es):
- Date
- Thread