All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Weihmann <kweihmann@outlook.com>
To: Ross Burton <ross@burtonini.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] python3-installer: add installer module
Date: Thu, 10 Mar 2022 20:03:44 +0100	[thread overview]
Message-ID: <AM9PR09MB46420D97FB3AE4F4349E2A4BA80B9@AM9PR09MB4642.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <CAAnfSTujN-T=7kfEfrmcs3XXdsAB2XL3=p9gtCWCyn__dhT2Pg@mail.gmail.com>



On 10.03.22 19:25, Ross Burton wrote:
> 
> On Thu, 10 Mar 2022 at 17:36, Konrad Weihmann <kweihmann@outlook.com 
> <mailto:kweihmann@outlook.com>> wrote:
> 
>     Sorry to say that - but to me (even though it's more work) pip seems to
>     be the better option - the proposed tool is ~8 months old and not part
>     of pypa community as it seems - so in comparison to pip this could not
>     be labeled "battle proven".
> 
> 
> It’s not that unheard of, for example the flit_core bootstrap 
> documentation says to use it:
> 
> https://flit.readthedocs.io/en/latest/bootstrap.html 
> <https://flit.readthedocs.io/en/latest/bootstrap.html>
> 
> It also does one job and just one job, which is A Very Good Thing.

Still doesn't make it the best choice TBH.
Just diving into the code makes me wonder about a lot, like

- can this tool run on non arm/aarch64/x86/x86-64 hosts 
(https://github.com/pradyunsg/installer/blob/fad2894a572d5497a3dceec58407c276f21e8c11/src/installer/utils.py#L140) 
- in its full feature set? - the assumptions made by this function, 
makes me think, it doesn't
- support of this here https://github.com/pradyunsg/installer/issues/98, 
should be given by a matured tool

> 
>     Especially as the second patch of the series removes the possibility to
>     use the tooling proposed by python upstream for installing stuff.
> 
> 
> Do you mean Pip here? That’s one option.  Installing a wheel is a 
> glorified unzip, pip brings a lot of baggage that we don’t care about.
> 
> I should make it clear that this class is not for installing arbitrary 
> wheels, it installs a wheel we just built and in the future will build 
> the wheel too.

Then that's definitely missing in the commit message, that this should 
be an option and not the default

> 
>     If one would want to have that kind of tooling the switch from pure
>     setup.py to toml and friends could have been done already a year ago
>     (python-build was the originally proposed tool iirc) - so this feels to
>     me like a step in the wrong direction (esp. the part that this would
>     rely on a tool **not** supported by upstream)
> 
> 
> Adding support for build is next on the list.
> 
> Ross
> 

Anyway, I think in before this patch series the switch to wheels was 
good enough to work with it, now it's just introducing another tool - 
that doesn't feel right to me, but I will stop arguing about that


  reply	other threads:[~2022-03-10 19:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 17:16 [PATCH 1/2] python3-installer: add installer module Ross Burton
2022-03-10 17:16 ` [PATCH 2/2] pip_install_wheel: use installer instead of pip Ross Burton
2022-03-10 21:19   ` [OE-core] " Richard Purdie
2022-03-10 17:36 ` [OE-core] [PATCH 1/2] python3-installer: add installer module Konrad Weihmann
2022-03-10 18:25   ` Ross Burton
2022-03-10 19:03     ` Konrad Weihmann [this message]
2022-03-10 19:29       ` Ross Burton
2022-03-11  4:17     ` Tim Orling
2022-03-11 13:13   ` Ross Burton
2022-03-10 21:21 ` Richard Purdie

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=AM9PR09MB46420D97FB3AE4F4349E2A4BA80B9@AM9PR09MB4642.eurprd09.prod.outlook.com \
    --to=kweihmann@outlook.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.