unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Tobias Geerinckx-Rice <me@tobias.gr>,
	mbakke@fastmail.com, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-xopen.
Date: Sun, 18 Dec 2016 11:23:26 +1000	[thread overview]
Message-ID: <f0516453-3390-6b21-bc56-5e12ac811921@uq.edu.au> (raw)
In-Reply-To: <dfdcebd3-be68-ddef-6c50-aa0a7f4115cc@tobias.gr>



On 18/12/16 11:00, Tobias Geerinckx-Rice wrote:
> Marius,
>
> On 16/12/16 17:09, Marius Bakke wrote:
>> Pypi archives are sometimes smaller than the raw sources
> Oh, I didn't know that.
>
>> or otherwise "prepared", but I guess no inherent benefits.
> Good point. I can certainly see people relying too heavily on GitHub
> (and similar) tarball auto-generation, while uploading a better one to
> PyPI that they've actually bootstrapped.
>
> Since this one builds fine, and the GitHub project is the official home
> page for better or worse, I'd vote against adding an ‘additional
> dependency on PyPI infrastucture’ as I think someone on the list put it.

Another reason for using pypi is that the github updater ignores tagged 
but not released 'releases', such as this. Perhaps we should change 
that, do others have an opinion?

Since using pypi is the way Python users expect to be able to install 
packages, making developers less concerned about their github releases 
than their pypi ones, I reckon sticking with pypi-uri is the way to go.

ben

  reply	other threads:[~2016-12-18  1:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 22:57 [PATCH] gnu: Add python-xopen Tobias Geerinckx-Rice
2016-12-15  9:20 ` Marius Bakke
2016-12-15 10:02   ` Tobias Geerinckx-Rice
2016-12-16 16:09     ` Marius Bakke
2016-12-18  1:00       ` Tobias Geerinckx-Rice
2016-12-18  1:23         ` Ben Woodcroft [this message]
2016-12-18 10:07           ` Hartmut Goebel
2016-12-18 16:21           ` Tobias Geerinckx-Rice
2016-12-16 20:19     ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0516453-3390-6b21-bc56-5e12ac811921@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).