Package Details: python38 3.8.20-1

Git Clone URL: https://aur.archlinux.org/python38.git (read-only, click to copy)
Package Base: python38
Description: Major release 3.8 of the Python high-level programming language
Upstream URL: https://www.python.org/
Keywords: python python3
Licenses: PSF-2.0
Submitter: rixx
Maintainer: rixx
Last Packager: rixx
Votes: 32
Popularity: 0.44
First Submitted: 2019-03-27 20:21 (UTC)
Last Updated: 2024-11-06 08:34 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5

max-k commented on 2020-12-03 15:09 (UTC)

Is there a problem ?

python3.8 --version
Python 3.9.0

harbind commented on 2020-12-03 08:28 (UTC)

python3.8-config does not work. It's a symlink to unexciting python3.8m-config.

rixx commented on 2019-06-05 10:18 (UTC)

I don't agree on the --enable-optimizations and --with-lto options: While they do improve Python speed noticeably, they also add considerable build time (think tens of minutes, at least, can range into an hour easily). I don't want the general Python 3.8 package to take this long to build – mainstream does not have the issue because the package is not built on every upgrade on every PC.

I fixed the failing symlinks, though, nd upgraded to 3.8.0b1

RunAndTumble commented on 2019-05-14 16:33 (UTC) (edited on 2019-05-14 16:52 (UTC) by RunAndTumble)

OK, when I try to build a4 version, first, I get this: configure: WARNING: unrecognized options: --with-threads However, it doesn't affect the process. The other problem is that it throws another error: ln: failed to create symbolic link '/home/user/build/python38/pkg/python38/usr/lib/python3.8/config-3.8m-x86_64-linux-gnu/libpython3.8m.so': No such file or directory and stops completely. Any ideas how to fix this?

P.S. It would be great to add --enable-optimizations and --with-lto as build parameters (python3.7 mainstream PKGBUILD has some detailed instructions).

rixx commented on 2019-04-25 12:36 (UTC)

Good point, I updated the URL.

zeust commented on 2019-04-25 10:25 (UTC)

Great package, works like a charm and does not conflict with Python stable! I do see that the upstream URL and the source download URL are still HTTP, it is better to change them to HTTPS. I did this myself locally before building the package (in both the PKGBUILD and the .SRCINFO) and can confirm that it works.

« First ‹ Previous 1 2 3 4 5