unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: "Munyoki Kilyungi" <me@bonfacemunyoki.com>, guix-devel@gnu.org
Subject: Re: IDEA: missing-tests-pypi-error? condition
Date: Fri, 06 Oct 2023 11:10:10 +0000	[thread overview]
Message-ID: <68f27945f4065f83c97931351c2ef01e@dismail.de> (raw)
In-Reply-To: <87v8bkxgl3.fsf@saitama.mail-host-address-is-not-set>

> Sometimes, PyPI versions lag behind upstream versions.

Hi Bonz,

Yes, in my experience that has sometimes been the case because maintainers don't make timely releases to PyPI.

> What's the policy on this. Shouldn't we prefer upstream over PyPI? 

Our importer works with the JSON API that PyPI provides at https://pypi.org/pypi/baz/json

See here:

https://git.savannah.gnu.org/cgit/guix.git/tree/guix/import/pypi.scm?h=master#n141

That API provides a lot of package data that GitHub does not track in a unified and structured way.

> Adding extra glue can add unnecessary complexity.

You're right. I thought about that after I sent the email with the idea ;()

Doing my best to make inboxes a happier place,

jgart


  parent reply	other threads:[~2023-10-06 11:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 13:08 IDEA: missing-tests-pypi-error? condition jgart
2023-10-06  9:09 ` Munyoki Kilyungi
2023-10-06 13:03   ` Maxim Cournoyer
2023-10-06 15:00     ` Munyoki Kilyungi
2023-10-07 16:07       ` Maxim Cournoyer
2023-10-08 13:11       ` jgart
2023-10-08 16:17         ` Luis Felipe
2023-10-09  0:52         ` Maxim Cournoyer
2023-10-09 13:36         ` Josselin Poiret
2023-10-09 13:57         ` jgart
2023-10-09 17:17           ` Maxim Cournoyer
2023-10-12  5:49             ` Efraim Flashner
2023-10-06 11:10 ` jgart [this message]
2023-10-06 12:50   ` Munyoki Kilyungi
2023-10-07 16:05     ` Maxim Cournoyer

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=68f27945f4065f83c97931351c2ef01e@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=me@bonfacemunyoki.com \
    /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).