APKBUILD examples:Python - Revision history

WhyNotHugo at 21:55, 7 April 2026

2026-04-07T21:55:22Z

← Older revision		Revision as of 21:55, 7 April 2026
Line 1:		Line 1:
	~~A lot of~~ Python packages use ~~the ''setuptools'' or ''distutils'' framework. This mean that the~~ build() and ~~the~~ package() ~~section looks a bit~~ different compared to an application which uses ''make''.		Typical Python packages use Python-specific build systems, making their <code>build()</code> and <code>package()</code> functions different compared to an application which uses ''make''.

	== Considerations ==		== Considerations ==
Line 8:		Line 8:

	For an 'executable' (for example, <code>black</code>, <code>binwalk</code>), you generally don't need to prefix it.		For an 'executable' (for example, <code>black</code>, <code>binwalk</code>), you generally don't need to prefix it.

	~~There’s no exact rule if the prefix should be used for tools and applications written in Python, it varies.~~

	=== arch ===		=== arch ===

	; noarch : Use for pure Python packages (i.e. without compiled code).		; noarch : Use for pure Python packages (i.e. without compiled code).
	; all (and others) : Use for packages with native extensions (i.e. with compiled code). '''Do not''' add python3 to <tt>depends=</tt> (it's auto-detected via dynamic linking to python library).		; all (and others) : Use for packages with native extensions (i.e. with compiled code).

			=== depends ===

			'''Do not''' add python3 to <tt>depends=</tt> (it's auto-detected via dynamic linking to python library).

	=== source ===		=== source ===
Line 35:		Line 37:
	<pre>		<pre>
	pkgname="py3-foo"		pkgname="py3-foo"
			_pyname=foo
	...		...
	depends="py3-bar py3-baz"		depends="py3-bar py3-baz"
Line 40:		Line 43:
	checkdepends="py3-pytest"		checkdepends="py3-pytest"
	subpackages="$pkgname-pyc"		subpackages="$pkgname-pyc"
			source="$pkgname-$pkgver.tar.gz::https://github.com/xyz/foo/archive/refs/tags/v$pkgver.tar.gz"
			builddir="$srcdir/$_pyname-$pkgver"
	...		...

	build() {		build() {
	gpep517 build-wheel \		gpep517 build-wheel --wheel-dir .dist --output-fd 3 3>&1
	--wheel-dir dist \
	--output-fd 3 3>&1 ~~>&2~~
	}		}

	check() {		check() {
	python3 -m venv --clear --system-site-packages testenv		python3 -m venv --clear --system-site-packages testenv
	testenv/bin/python3 -m installer dist/*.whl		testenv/bin/python3 -m installer .dist/*.whl
	testenv/bin/python3 -m pytest		testenv/bin/python3 -m pytest
	}		}
Line 60:		Line 63:
	</pre>		</pre>

	Depending on the <code>build-backend</code> in the pyproject.toml, ~~you might need~~ py3-setuptools or py3-flit-core or py3-poetry-core or py3-hatchling at build time. If a project specifies literally <code>flit</code> or <code>poetry</code>, patch it to use the <code>-core</code> variant.		Depending on the <code>build-backend</code> in the pyproject.toml, the package should depend on py3-setuptools, py3-flit-core, py3-poetry-core or py3-hatchling at build time. If a project specifies literally <code>flit</code> or <code>poetry</code>, patch it to use the <code>-core</code> variant.

	[[Category:Development]] [[Category:Python]]		[[Category:Development]] [[Category:Python]]

Psykose: gpep517 only

2023-05-11T07:06:02Z

gpep517 only

← Older revision		Revision as of 07:06, 11 May 2023
Line 30:		Line 30:

	== Examples ==		== Examples ==

	~~=== setup.py invocation ===~~

	~~If the project has a setup.py, then the APKBUILD goes as follows:~~

	~~<pre>~~
	~~pkgname="py3-foo"~~
	~~_pyname="foo"~~
	~~...~~
	~~makedepends="python3-dev"~~
	~~checkdepends="py3-pytest"~~
	~~subpackages="$pkgname-pyc"~~
	~~...~~

	~~build() {~~
	~~python3 setup.py build~~
	}

	~~check() {~~
	~~pytest~~
	}

	~~package() {~~
	~~python3 setup.py install --skip-build --root="$pkgdir"~~
	}
	~~</pre>~~

	~~However, even with a setup.py, you can use the pep517 build process. If a project does not have a setup.py and only has a pyproject.toml, then you can only use the pep517 build process below.~~

	=== pep517 invocation ===		=== pep517 invocation ===

Psykose: /* arch */

2023-04-30T01:33:06Z

arch

← Older revision		Revision as of 01:33, 30 April 2023
Line 13:		Line 13:
	=== arch ===		=== arch ===

	; noarch : Use for pure Python packages (i.e. without compiled code)~~. Also add python3 to <tt>depends=</tt>~~.		; noarch : Use for pure Python packages (i.e. without compiled code).
	; all (and others) : Use for packages with native extensions (i.e. with compiled code). '''Do not''' add python3 to <tt>depends=</tt> (it's auto-detected via dynamic linking to python library).		; all (and others) : Use for packages with native extensions (i.e. with compiled code). '''Do not''' add python3 to <tt>depends=</tt> (it's auto-detected via dynamic linking to python library).

Psykose: /* pep517 invocation */

2023-04-30T01:32:36Z

pep517 invocation

← Older revision		Revision as of 01:32, 30 April 2023
Line 64:		Line 64:
	pkgname="py3-foo"		pkgname="py3-foo"
	...		...
	depends="~~python3~~ py3-bar py3-baz"		depends="py3-bar py3-baz"
	makedepends="py3-gpep517 py3-setuptools py3-wheel python3-dev"		makedepends="py3-gpep517 py3-setuptools py3-wheel python3-dev"
	checkdepends="py3-pytest"		checkdepends="py3-pytest"

Psykose: /* setup.py invocation */

2023-04-30T01:32:28Z

setup.py invocation

← Older revision		Revision as of 01:32, 30 April 2023
Line 39:		Line 39:
	_pyname="foo"		_pyname="foo"
	...		...
	~~depends="python3"~~
	makedepends="python3-dev"		makedepends="python3-dev"
	checkdepends="py3-pytest"		checkdepends="py3-pytest"

Psykose: add -pyc

2023-04-20T08:57:03Z

add -pyc

← Older revision		Revision as of 08:57, 20 April 2023
Line 42:		Line 42:
	makedepends="python3-dev"		makedepends="python3-dev"
	checkdepends="py3-pytest"		checkdepends="py3-pytest"
			subpackages="$pkgname-pyc"
	...		...

Line 67:		Line 68:
	makedepends="py3-gpep517 py3-setuptools py3-wheel python3-dev"		makedepends="py3-gpep517 py3-setuptools py3-wheel python3-dev"
	checkdepends="py3-pytest"		checkdepends="py3-pytest"
			subpackages="$pkgname-pyc"
	...		...

Psykose: clear for venv

2023-02-07T05:39:50Z

clear for venv

← Older revision		Revision as of 05:39, 7 February 2023
Line 76:		Line 76:

	check() {		check() {
	python3 -m venv --system-site-packages testenv		python3 -m venv --clear --system-site-packages testenv
	testenv/bin/python3 -m installer dist/*.whl		testenv/bin/python3 -m installer dist/*.whl
	testenv/bin/python3 -m pytest		testenv/bin/python3 -m pytest

Psykose: modernise

2023-01-30T14:07:55Z

modernise

← Older revision		Revision as of 14:07, 30 January 2023
Line 18:		Line 18:
	=== source ===		=== source ===

	Most Python packages are published in [https://pypi.python.org/pypi PyPI] (the Python Package Index).		Most Python packages are published in [https://pypi.python.org/pypi PyPI](the Python Package Index).
	If the package has a source tarball available in PyPI (that’s true for most packages), and it contains tests (some explicitly remove them from PyPI), you should reference it in <tt>source=</tt> as:		If the package has a source tarball available in PyPI (that’s true for most packages), and it contains tests (some explicitly remove them from PyPI), you should reference it in <tt>source=</tt> as:

Line 31:		Line 31:
	== Examples ==		== Examples ==

	=== ~~Package for setuptools/~~setup.py ~~build~~ ===		=== setup.py invocation ===

	If the project has a setup.py, then the APKBUILD ~~is very simple~~:		If the project has a setup.py, then the APKBUILD goes as follows:

	<pre>		<pre>
Line 57:		Line 57:
	</pre>		</pre>

	~~Note that PyPI tarballs can contain~~ a ~~generated~~ setup.py ~~that does not exist in the upstream repo - this means~~ you ~~must~~ use the pyproject.toml ~~method if~~ you ~~change sources~~.		However, even with a setup.py, you can use the pep517 build process. If a project does not have a setup.py and only has a pyproject.toml, then you can only use the pep517 build process below.

	=== ~~Package for pyproject.toml build~~ ===		=== pep517 invocation ===

	<pre>		<pre>
	pkgname="py-foo"		pkgname="py3-foo"
	~~_pyname="PyFoo~~"
	...		...
	depends="python3 py3-bar py3-baz"		depends="python3 py3-bar py3-baz"
	makedepends="py3-gpep517 py3-~~installer~~ python3-dev py3-~~wheel~~"		makedepends="py3-gpep517 py3-setuptools py3-wheel python3-dev"
			checkdepends="py3-pytest"
	...		...

Line 72:		Line 72:
	gpep517 build-wheel \		gpep517 build-wheel \
	--wheel-dir dist \		--wheel-dir dist \
	--output-fd 1		--output-fd 3 3>&1 >&2
	}		}

	check() {		check() {
	pytest		python3 -m venv --system-site-packages testenv
			testenv/bin/python3 -m installer dist/*.whl
			testenv/bin/python3 -m pytest
	}		}

	package() {		package() {
	python3 -m installer -d "$pkgdir" \		python3 -m installer -d "$pkgdir" \
	dist/~~PyFoo-$pkgver-py3-none-any~~.whl		dist/*.whl
	}		}
	</pre>		</pre>

	Depending on the <code>build-backend</code> in the pyproject.toml, you might need py3-setuptools or py3-flit-core or py3-poetry-core or py3-hatchling at build time.		Depending on the <code>build-backend</code> in the pyproject.toml, you might need py3-setuptools or py3-flit-core or py3-poetry-core or py3-hatchling at build time. If a project specifies literally <code>flit</code> or <code>poetry</code>, patch it to use the <code>-core</code> variant.

	~~Sometimes you might have to pass the path~~ to the ~~built package to run tests:~~

	<~~pre~~>
	~~check() {~~
	~~python3 -m venv --system-site-packages testenv~~
	~~testenv/bin/python3 -m installer \~~
	~~dist/PyFoo~~-~~$pkgver-py3-none-any.whl~~
	~~testenv/bin/python3 -m pytest~~
	}
	</~~pre~~>

	[[Category:Development]] [[Category:Python]]		[[Category:Development]] [[Category:Python]]

Psykose: fd1. one day i'll get it right

2022-12-02T08:03:36Z

fd1. one day i'll get it right

← Older revision		Revision as of 08:03, 2 December 2022
Line 72:		Line 72:
	gpep517 build-wheel \		gpep517 build-wheel \
	--wheel-dir dist \		--wheel-dir dist \
	--output-fd 2		--output-fd 1
	}		}

Psykose: fd2

2022-11-23T07:20:25Z

fd2

← Older revision		Revision as of 07:20, 23 November 2022
Line 72:		Line 72:
	gpep517 build-wheel \		gpep517 build-wheel \
	--wheel-dir dist \		--wheel-dir dist \
	--output-fd 1		--output-fd 2
	}		}