Package Details: lib32-python 3.11.5-1

Git Clone URL: (read-only, click to copy)
Package Base: lib32-python
Description: Next generation of the python high-level scripting language
Upstream URL:
Licenses: custom
Provides: lib32-python3
Submitter: adsun
Maintainer: wxt1221
Last Packager: sbmomeni
Votes: 3
Popularity: 0.010887
First Submitted: 2018-04-22 19:35 (UTC)
Last Updated: 2023-09-14 15:56 (UTC)

Latest Comments

adam900710 commented on 2019-12-08 08:26 (UTC) (edited on 2019-12-08 09:37 (UTC) by adam900710)

Can we skip the tests for profile based optimization? (By removing the --enable-optimizations and --with-lto lines)

I don't really believe there are that many users using lib32-python as a daily driver, but a dependency for other lib32 packages.

In that case, a little slower is completely acceptable.

adsun commented on 2019-03-22 02:39 (UTC) (edited on 2019-03-22 02:41 (UTC) by adsun)

I modeled this PKGBUILD after the lib32-python2 PKGBUILD in the AUR. The reason for the strange "m" after "${_pybasever}" was because I wanted to follow the official python PKGBUILD, following its own include directory, "/usr/include/python3.7m". I don't use this package much anyway, so I am disowning this.

I tested it out though and "import pyexpat" does work on my system.

DarkShadow44 commented on 2019-03-21 19:03 (UTC) (edited on 2019-03-21 20:09 (UTC) by DarkShadow44)

Also, is it normal that you need to set


before it finds modules? Or is that something we can configure globally?

Similar for its own modules, it can't "import pyexpat", which should work.

DarkShadow44 commented on 2019-03-20 22:16 (UTC) (edited on 2019-03-20 22:16 (UTC) by DarkShadow44)

There are some strange paths in the PKGBUILD and lib32-distutils-sysconfig.patch:



What's the reason for the stray 'm' in there? Don't know if it's intended, but it's not consistent, breaking my builds. Can you please take a look?

llde commented on 2018-12-28 14:34 (UTC) (edited on 2018-12-28 14:46 (UTC) by llde)

There seems to be some issue in the package: 1)Some files are still putted in /usr/lib instead of /usr/lib32 2)The package contains a python3-config and a python-32-config. IT doesn't exist a python3-32-config file. This cause a conmflict issue when trying to install the package Also python 3.6 is still referenced in some bits of the PKGBUILD and the lib32-distutils-sysconfig.patch file