Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/python-uvloop: add support for cython3
Date: Sun, 11 Feb 2024 22:57:51 +0100	[thread overview]
Message-ID: <ZclC3_dSvLTp6Ras@landeda> (raw)
In-Reply-To: <CADvTj4ppD06TSGnYUUBSzB_sV6vErb2ozyMuGr1QjyLtu_pvPA@mail.gmail.com>

James, All,

On 2024-02-11 14:39 -0700, James Hilliard spake thusly:
> On Sun, Feb 11, 2024 at 2:24 PM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2024-02-09 10:56 -0700, James Hilliard spake thusly:
> > > Add patches from pending upstream pull request which add cython3
> > > compatibility.
> > We are a little bit cautious at applying random patches that have not
> > yet been at least reviewd by upstream. In this case, there has not been
> > any upstream activity since the last release, and not muc before that
> > either...
> Well these patches are being used by gentoo so they are not entirely
> untested in the real world.

It's not that they are tested or not. It is about whether they'll have a
chance to be accepted upstream, or whether we'll have to carry and
maintain them forever in Buildroot.

Maybe it's time that someone pings upstream about that PR?

> > We have no in-tree user of uvloop, so I wonder whether it makes snse to
> > keep it, espcially since it mau be blocking the bumps of other packages
> > (like cython 3.x being required by whats-its-name).
> That's not entirely true, it's a common optional dependency for packages
> like python-uvicorn for example.

    $ git grep -i -E python.uvloop

would turn only python-uvloop itself, and its runtime test. If it
is only optional, and prevents us from updating unless we apply
non-upstreamable patches, then I'd argue we should drop it.

[--SNIP--]
> I'll fix and resend.

Thanks.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-11 21:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 17:56 [Buildroot] [PATCH 1/2] package/python-uvloop: add support for cython3 James Hilliard
2024-02-09 17:56 ` [Buildroot] [PATCH 2/2] package/python-cython: bump to version 3.0.8 James Hilliard
2024-02-11 21:30   ` Yann E. MORIN
2024-02-12  0:46     ` James Hilliard
2024-02-11 21:24 ` [Buildroot] [PATCH 1/2] package/python-uvloop: add support for cython3 Yann E. MORIN
2024-02-11 21:39   ` James Hilliard
2024-02-11 21:57     ` Yann E. MORIN [this message]
2024-02-12  0:13       ` Marcus Hoffmann via buildroot
2024-02-12  0:51         ` James Hilliard
2024-02-12 19:50           ` Arnout Vandecappelle via buildroot
2024-02-12 21:09             ` James Hilliard
2024-02-12 21:53               ` Arnout Vandecappelle via buildroot
2024-02-12 22:11                 ` James Hilliard

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

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

  git send-email \
    --in-reply-to=ZclC3_dSvLTp6Ras@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=james.hilliard1@gmail.com \
    --cc=joseph.kogut@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox