From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Munyoki Kilyungi <me@bonfacemunyoki.com>
Cc: jgart <jgart@dismail.de>, guix-devel@gnu.org
Subject: Re: IDEA: missing-tests-pypi-error? condition
Date: Sat, 07 Oct 2023 12:05:45 -0400 [thread overview]
Message-ID: <87leceifja.fsf@gmail.com> (raw)
In-Reply-To: <87sf6nykxc.fsf@saitama.mail-host-address-is-not-set> (Munyoki Kilyungi's message of "Fri, 06 Oct 2023 15:50:23 +0300")
Hi,
Munyoki Kilyungi <me@bonfacemunyoki.com> writes:
> "jgart" <jgart@dismail.de> aliandika:
>
>>> 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.
>>
> Then given the above ...
>>> Adding extra glue can add unnecessary complexity.
>>
>> You're right. I thought about that after I sent the email with the idea ;()
>>
>
> PyPi unless we need to use upstream is the way to
> go ;)
Yes, I was thinking continuing to use PyPI, but attempt to find the
repository URL from PyPI's metadata and used that when generating a
package definition with the pypi importer.
I don't know how feasible that would be.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-10-07 16:06 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
2023-10-06 12:50 ` Munyoki Kilyungi
2023-10-07 16:05 ` Maxim Cournoyer [this message]
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=87leceifja.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--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).