Package Details: python2-setuptools 2:44.1.1-2

Git Clone URL: (read-only, click to copy)
Package Base: python2-setuptools
Description: Easily download, build, install, upgrade, and uninstall Python packages
Upstream URL:
Licenses: PSF
Provides: python2-distribute
Replaces: python2-distribute
Submitter: jelly
Maintainer: tallero
Last Packager: jelly
Votes: 22
Popularity: 1.49
First Submitted: 2022-09-22 16:43 (UTC)
Last Updated: 2022-09-22 16:43 (UTC)

Latest Comments

1 2 Next › Last »

gnaggnoyil commented on 2022-12-03 07:58 (UTC)

@eclairevoyant I'm sure I'm using python2. I've also tried building in a clean chroot and the result was the same.

eclairevoyant commented on 2022-11-30 11:07 (UTC)

This package builds fine. Make sure you're using python2, not python2-bin, and ensure you're building in a clean chroot.

superyu1337 commented on 2022-11-19 00:25 (UTC)

@jbbjarnason after a lot of fiddling around yesterday night, i got it to work by using PYTHONHOME=/usr

I also had pyenv setup previously, which I removed.

jbbjarnason commented on 2022-11-18 10:13 (UTC)

I am getting similar error as @ak2021 and @superyu1337. Both on my laptop and workstation (both running vanilla arch).

Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Traceback (most recent call last):
  File "", line 13, in <module>
    import subprocess
  File "/usr/lib/python2.7/", line 72, in <module>
    import select
ImportError: No module named select
==> ERROR: A failure occurred in build().
 -> error making: python2-setuptools

superyu1337 commented on 2022-11-18 00:22 (UTC)

I keep getting this error:

Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site

drws commented on 2022-10-31 03:53 (UTC) (edited on 2022-10-31 03:53 (UTC) by drws)

I have been able to build the package by fixing the PKGBUILD with @emceebois's solution:

build() {
  cd setuptools-$pkgver
  python2 || true
  echo "Version:$pkgver" > setuptools.egg-info/PKG-INFO
  python2 build

However, this appears to be a bug in we are working around. This should be only a temporary solution. Has anybody reported or find it reported yet?

emceebois commented on 2022-10-26 19:21 (UTC)

I'm not familiar with the PKGBUILD system to be honest but if there's some way to inject arbitrary terminal commands in the PKGBUILD and doesn't do anything weird with folder ownership or permissions when it creates the .egg-info folder then you should be able to create the .egg-info folder, create the PKG-INFO file, and inject the correct string into it before trying to run the command.

gnaggnoyil commented on 2022-10-26 17:55 (UTC)

@emceebois Thanks for your workaround. Do you know how can we modify PKGBUILD so that we can apply your workaround and then run makepkg to build the package?

emceebois commented on 2022-10-25 16:59 (UTC)

Hey @gnaggnoyil, @jester, @kamazeuci, et al. It seems like the process is trying and failing to infer the version number of the package which it's supposed to put into the setuptools.egg-info folder it creates. I was able to get around this error by doing the following:

  1. Clone the repo
  2. Go into the src/setuptools-44.1.1 folder
  3. Manually run the command python2 (this will fail and generate the error, but it creates the setuptools.egg-info folder)
  4. Manually create the PKG-INFO file inside of setuptools.egg-info
  5. Edit PKG-INFO to read the following: Version:44.1.1
  6. From the src/setuptools-44.1.1 folder, re-run python2 This should succeed
  7. Finally, run sudo python2 install

chowbok commented on 2022-10-24 07:12 (UTC)

This package doesn't compile with python2-bin. You need to compile and install the regular python2 AUR package.