Edit This Page ⓘClicking 'Edit This Page' will open a new tab or window to edit this page on the Git forge. You'll need to be signed into the forge to edit. Close the edit page to return to this one.
(note by Bill)
reviewed several PyPI module build tools and settled on two prospects:
flit: simple to put into practice; minimal metadata requiredhatch: also simple; metadata seems more complicated; also supports more options(also experimented with using build and twine modules: very simple; does not support dependencies so that is not suitable for Massive Wiki publishing.)
important to create and use test.pypi.org to work out the use details; requires creating a login and an API key
reading the flit documentation, care must be taken to insure that testing uses the test.pypi.org system; seems easy to end up using the default, which is the main PyPI server, and that needs to be avoided.
test.pypi.org here: Using .pypirc, Controlling package uploadsquestions to answer:
__init.py__ file?version descriptor? (reason for this question: some docs show it in the pyproject.toml file which seems like a terrible place -- once all that metadata is set up just leave that file alone; some docs show it imported into the __init.py__ file, but how is that used?; flit wants the version descriptor at the top of the source file -- OK, that seems maintainable )Hatch: About - Hatch (pypa.io)
Twine: twine · PyPI
Build: build · PyPI
An example of a good documentation practice to emulate: The Most Complete Guide for Creating a Good PyPI Package | by Elise Landman | Towards Data Science