From nobody Thu Jan 09 15:25:47 2025 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YTTBv4G6mz5l0LL for ; Thu, 09 Jan 2025 15:25:59 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTTBv3kJ8z4Dvk; Thu, 9 Jan 2025 15:25:59 +0000 (UTC) (envelope-from eduardo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736436359; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TPXpe1kBIkzXYp6a/d+bSRF6VMCE+5KWdvaoCT3T1QU=; b=tVD7qUVyMKvsur9YIlhjE2f8uOIYio4i+1l7qXUALAtyHt5VVkKSSISmRJlJHv4oIBX622 RQXztvYUU6jHTC0lLkyX3HB+se7jAPITJawJkZdBGQqQ/HNCS2HeftGYcYrymLQDL4+1fQ 9Av2hsvFKjWQ8XMW2FIeZ3ugKED2rUZk1JYeDCex9H4PPx4ZXXLzNFqXR+qV1cDk9sAHBL 7GH62a4XnSTQrexhmsjpcIQQsRhup5rjvWM78icQ2Y2R+WrjX1LiDFEDDeAlnDhtLpGf/o 7zDHUyXkjLBSfseKQ58ZbS3RlqfkUKTxeYvT78w0zrLAEcKbc3ra41BEMqTZtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736436359; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TPXpe1kBIkzXYp6a/d+bSRF6VMCE+5KWdvaoCT3T1QU=; b=DYHin6LjPjk7exCYpf/x6crBXd7gL+j6TDu/akWq71TdeQnBbIgxlYibuq/BTe7tdYS5Gy ZjpekQykARFcKywktu+4FtHG7oNEqJ/Op6h3zh95bNWtiSmRQE7ZzwLy0P8iZRHDDPsQXy FbcLmLUXgCFMjBHTClfAD7MQOtva3XZGmfYRJAv5PcZKAhOvv5NvRhj3vxZWhk5JdrkWy9 LqTVr0Lz6CMGPy7Iou1HzYxfKgQL7Do/Gd4fpZvDZUGyOlsGS/pSoLbPrlhZIeFhiAEfrz Y0xAip0XDLrY2t74FZohLcpBILyM/HWz92ojI4ghcN8PPx30XtObCmve0iIAjw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736436359; a=rsa-sha256; cv=none; b=JMAqAsxiXeVNdjM0tV4IuIyaCUav4g8Ftm4X3MGwlcszuuVXFH+ogLvfZWiTsTH31zF0wb PA2Zj0dj+A75dTYJ0OUAzuvA3j9H5gL2aTsikarR0JSDumOhD4fbqxhRd81l4fFEA3CW2T NP7oMYlzWH6aYdlCRq7evN7yxGTBUoNISBDw8erpsivGKHP0iW7rB1XfaDiagsAeu2ER7a wqSrmimckaEj1/4vGLnLzdxNoYUelco/3QSXl/M8J6M6f0qgu24VWawiSB5HFK+A2uhdE+ zM7ZWp36rc504Z695YtS3ayYsl+Ijh70ve1jb17D84B2eEtC06fj1YcrTwD4KQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) (Authenticated sender: eduardo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4YTTBv2xjVz4tc; Thu, 09 Jan 2025 15:25:59 +0000 (UTC) (envelope-from eduardo@freebsd.org) Received: by mail-qk1-f175.google.com with SMTP id af79cd13be357-7b6ffda45f3so10679985a.2; Thu, 09 Jan 2025 07:25:59 -0800 (PST) X-Gm-Message-State: AOJu0YxyQFT0EWSY4EtWmrOZvYJWsRCgeFDdXq1FGzjapOmwTN7ykBrs 84jxQMuvANsOvvpi/wFtKlqzjP8E4lBRYCqjV4Xsa/v9xtNOY5QLyoa0RFPp51LwL89qe5XcPLr IcgMTgm+QWOVIE19z4twFBn5TkgM= X-Google-Smtp-Source: AGHT+IFVNvUosVWQUIKYI92FnNDQhJ0uVemk+dDZqVRy98u/gnWZKhYueXtkm6vHe6KuaYhkPpn4r2G4ng0OgCYQjv4= X-Received: by 2002:ac8:5e4a:0:b0:467:825e:133b with SMTP id d75a77b69052e-46c7108eed3mr35701481cf.13.1736436358883; Thu, 09 Jan 2025 07:25:58 -0800 (PST) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 References: <97ad2d36-ed8d-47a5-ad74-b4b5ace3a14a@freebsd.org> In-Reply-To: <97ad2d36-ed8d-47a5-ad74-b4b5ace3a14a@freebsd.org> From: Nuno Teixeira Date: Thu, 9 Jan 2025 15:25:47 +0000 X-Gmail-Original-Message-ID: X-Gm-Features: AbW1kvZvoXsbwJCe2JeCgcq73_Cjf0q3M8-GqdIrrdyRqyZzRkWrSIkXX6o0Hdw Message-ID: Subject: Re: Python: Switch from distutils to pep517 To: Charlie Li Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="00000000000058aed6062b4798ab" --00000000000058aed6062b4798ab Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Charlie, Thanks for clarification and I'm looking for pep517 to get updated soon. What a commiter can do about this? Each python port that I come cross with in bugzilla that uses distutils, I check if pep517 is possible and then I try to convince maintainer to use that build instead. Some maintainers go for new build (sometimes adding pytest to it too) others prefers to wait until it is *really* deprecated. I don't know if a decision of a mass change will be made or not, but as committer, I'm thinking opening PRs for ports where pep517 do work. Maybe a master PR should exist to connect all indidual PRs. With an updated pep517 wiki this will be easier to execute. Thoughts? Thanks, Charlie Li escreveu (quinta, 9/01/2025 =C3=A0(s) 05:4= 1): > Nuno Teixeira wrote: > > Hello all, > > > > How is the status of switching from deprecated distutils to pep517 buil= d? > > I remember some time ago to see some changes but it seems to stalled no= w. > > > Not stalled. Not every Python package in the wild has flipped to PEP-517 > yet. > > For people upgrading to pep517, are depends correct? > > > > BUILD_DEPENDS=3D \ > > ${PY_SETUPTOOLS} \ > > ${PYTHON_PKGNAMEPREFIX}wheel>0:devel/py-wheel@${PY_FLAVOR} > > > > Or ${PY_SETUPTOOLS} should be replaced with ? > > ${PYTHON_PKGNAMEPREFIX}setuptools>0:devel/py-setuptools@${PY_FLAVOR} > > > The latter. Originally I implemented ${PY_SETUPTOOLS} when > devel/py-setuptools58 was still viable for the remaining > USE_PYTHON=3Ddistutils cases, but both significant changes in later > devel/py-pyproject-hooks breaking setuptools 58 (and rendering > maintenance uneconomical) and continued maintenance of setup() direct > execution obviated that plan. Until I update devel/py-setuptools itself, > which will specify devel/py-wheel as both {BUILD,RUN}_DEPENDS, you will > need to also specify the latter in each setuptools PEP-517 consumer. > > I will update the documentation (mostly the wiki?) accordingly. > > -- > Charlie Li > ...nope, still don't have an exit line. > --=20 Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org --00000000000058aed6062b4798ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Charlie= ,

Thanks for clarification and I'm looking for pep517 to g= et updated soon.

What a commiter can do about this?
E= ach python port that I come cross with in bugzilla that uses distutils, I c= heck if pep517 is possible and then I try to convince maintainer to use tha= t build instead.
Some maintainers go for new build (sometimes addi= ng pytest to it too) others prefers to wait until it is *really* deprecated= .

I don't know if a decision of a mass change will be made= or not, but as committer, I'm thinking opening PRs for ports where pep= 517 do work.
Maybe a master PR should exist to connect all indidua= l PRs.

With an updated pep517 wiki this will be easier to exec= ute.

Thoughts?

Thanks,

C= harlie Li <vishwin@freebsd.org> escreveu (quinta, 9/01/2025 =C3=A0(s) 05:41):
Nuno Teixeira wrote:
> Hello all,
>
> How is the status of switching from deprecated distutils to pep517 bui= ld?
> I remember some time ago to see some changes but it seems to stalled n= ow.
>
Not stalled. Not every Python package in the wild has flipped to PEP-517 yet.
> For people upgrading to pep517, are depends correct?
>
> BUILD_DEPENDS=3D \
> ${PY_SETUPTOOLS} \
> ${PYTHON_PKGNAMEPREFIX}wheel>0:devel/py-wheel@${PY_FLAVOR}
>
> Or ${PY_SETUPTOOLS} should be replaced with ?
> ${PYTHON_PKGNAMEPREFIX}setuptools>0:devel/py-setuptools@${PY_FLAVOR= }
>
The latter. Originally I implemented ${PY_SETUPTOOLS} when
devel/py-setuptools58 was still viable for the remaining
USE_PYTHON=3Ddistutils cases, but both significant changes in later
devel/py-pyproject-hooks breaking setuptools 58 (and rendering
maintenance uneconomical) and continued maintenance of setup() direct
execution obviated that plan. Until I update devel/py-setuptools itself, which will specify devel/py-wheel as both {BUILD,RUN}_DEPENDS, you will need to also specify the latter in each setuptools PEP-517 consumer.

I will update the documentation (mostly the wiki?) accordingly.

--
Charlie Li
...nope, still don't have an exit line.


--
Nuno Teixeira
--00000000000058aed6062b4798ab--