pkgbuilds

This is a collection of the PKGBUILD files (Arch User Repository install files) that I maintain.

Feel free to submit PRs if you want to see a change or an update, I'll be likely to merge, test, and push soon.

python313
python312
python311 (current upstream Python version, so not available on AUR. Will be back once Arch updates to 3.12)
python310 (used to be the AUR version when [core] was still on 3.9, now somebody else is maintaining the AUR package. I'm still using this one since I prefer the build options.)
python39
python38
python36
hostmux
augenkrebs

Discontinued pkgbuilds

Archived pkgbuilds can be found in archived, which includes

python35 removed due to age

Python package FAQ

I'm mostly putting these here so I have a way to copy and paste a friendly answer for questions on aur.archlinux.org.

y u no optimizations??

This package intentionally doesn't use --enable-optimizations. Enabling optimizations adds a lot of build time – I for one would not upgrade my Python as regularly if every update took 25-40 minutes of heavy CPU use (depending on your machine, but laptop was pretty beefy when I got it three years ago, and even 3.11 takes 25 minutes on it). Adding the flag is easy to do on your own – grab the repo, add the flag, makepkg. Imo adding it by default would be a poor choice.

pls add provides=Python

Nope. Been there, done that, got chewed out for it. tl;dr: Provides=Python makes the system assume that if you have Python from core and Python from AUR installed, and you remove core Python, then all Python dependencies will continue working. Which they won't, obv, so adding provides=(Python) (yes, even with a version string!) is misleading and bad.

Usage for maintainers

In sub-directory: Edit PKGBUILD
makepkg --check
namcap PKGBUILD
namcap *.xz
makepkg --printsrcinfo > .SRCINFO
git commit -am 'Meaningful commit message'
git push
In root directory: git commit -am [package] Meaningful commit message