From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: Questions regarding Python packaging
Date: Mon, 9 Nov 2020 17:54:36 +0100 [thread overview]
Message-ID: <ce3a7b4a-6ce7-d579-4556-33841a9db3fd@crazy-compilers.com> (raw)
In-Reply-To: <20201108142717.lmud5h4gh44vtjc6@melmoth>
Hi,
seems like another messages of mine, regarding the first thread about a
poetry build system, did not make it to the list.
Am 08.11.20 um 15:27 schrieb Tanguy Le Carrour:
> I've just learned, by accident (working on `python-keyring` [1]), that
> `python setup.py install` was somehow deprecated
This statement is not exactly true - well, depending on interpretation
of "somehow". I've not set seen an official deprecation.
It's true that users are encouraged to use pip for installing packages.
But the official Python Packaging Tutorial [1] is still based on
setuptools (not even recommending a setup.cfg file). Thus setuptools
will be around for quite some more time, as will "python setup.py install".
In the future Python world, any build-tool can be specified in
"pyproject.toml". User will then call "pip install", and pip will
(AFAIU) call a Python function (aka entry-point) specified in that file.
(If this file does not exist, setuptools are assumed). For our
python-build-system, we would use "pip wheel" (for phase build) and "pip
install" (for phase install).
So, if we switch to "pip wheel" and "pip install", different python
build systems could share a common base, just redefining some
dependencies (setuptools, poetry, build, ...) and some tool-dependent
flags. Is this the direction you are working towards?
[1] https://packaging.python.org/tutorials/packaging-projects/
> in favor of tools like`pep517` or `build`.
Thanks for point to these, both are new to me.
"build" sounds interesting, esp. for guix: "It is a simple build tool
and does not perform any dependency management." This would help us
spliting dependency management and build phase. Anyhow, it's quite new
(half an year old) and implements a PEP 517 package builder - and PEP
517 (defining the build system in pyproject.toml) is not yet adopted widely.
"pep517" seems o be a library used for "build". Its high-level interface
has been deprecated in favor for "build".
I as just about to write "So, while this might be one road to go, this
is not of much use for us yet.". Anyhow, this might be a good base for
pep517 based packages. On the other hand: Maybe we'd better stick with
"pip wheel" and "pip install", see above.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2020-11-09 16:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 14:27 Questions regarding Python packaging Tanguy Le Carrour
2020-11-08 17:05 ` Leo Famulari
2020-11-10 8:35 ` Tanguy Le Carrour
2020-11-08 20:43 ` Michael Rohleder
2020-11-10 8:30 ` Tanguy Le Carrour
2020-11-09 16:54 ` Hartmut Goebel [this message]
2020-11-10 8:47 ` Tanguy Le Carrour
2020-11-10 8:53 ` Hartmut Goebel
2021-01-05 10:25 ` Lars-Dominik Braun
2021-01-06 15:32 ` Tanguy LE CARROUR
2021-01-22 8:38 ` Tanguy LE CARROUR
2021-01-23 12:34 ` Lars-Dominik Braun
2021-01-24 13:30 ` Tanguy LE CARROUR
2021-01-24 20:54 ` Ryan Prior
2021-01-25 11:47 ` Lars-Dominik Braun
2021-01-25 16:57 ` Ryan Prior
2021-02-05 10:40 ` Hartmut Goebel
2021-05-17 6:24 ` Lars-Dominik Braun
2021-06-06 16:44 ` Tanguy LE CARROUR
2021-06-06 19:44 ` Lars-Dominik Braun
2021-06-22 6:53 ` Removal of Python 2? Hartmut Goebel
2021-06-22 12:41 ` Konrad Hinsen
2021-06-23 15:26 ` Ludovic Courtès
2021-06-23 15:34 ` zimoun
2021-06-23 18:32 ` Konrad Hinsen
2021-06-22 18:02 ` Ryan Prior
2021-06-25 6:37 ` Konrad Hinsen
2021-06-22 7:00 ` Questions regarding Python packaging Hartmut Goebel
2021-06-28 11:59 ` Lars-Dominik Braun
2021-06-28 20:37 ` Hartmut Goebel
2021-06-29 7:20 ` Lars-Dominik Braun
2021-07-06 12:16 ` [bug#46848] " Lars-Dominik Braun
2021-07-07 15:01 ` Hartmut Goebel
2021-01-26 7:21 ` Tanguy LE CARROUR
2021-01-27 3:43 ` Maxim Cournoyer
2021-01-06 15:37 ` Tanguy LE CARROUR
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=ce3a7b4a-6ce7-d579-4556-33841a9db3fd@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
/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).