Package Details: python39 3.9.20-1

Git Clone URL: https://aur.archlinux.org/python39.git (read-only, click to copy)
Package Base: python39
Description: Major release 3.9 of the Python high-level programming language
Upstream URL: https://www.python.org/
Licenses: PSF-2.0
Submitter: rixx
Maintainer: rixx
Last Packager: rixx
Votes: 25
Popularity: 0.28
First Submitted: 2021-12-13 11:56 (UTC)
Last Updated: 2024-11-06 08:35 (UTC)

Dependencies (16)

Required by (7)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

rixx commented on 2023-06-10 07:43 (UTC)

tkinter is an optdepend for this reason – there are plenty of distros that have tk as optional dependency, see for example ubuntu, where you install python3-tk, Fedora with python3-tkinter, brew, Windows, etc.

Having tkinter as optdepend is imo exactly the correct way to handle this (not everybody wants or needs tk in their Python).

(Side note: I don't think marking the package as out-of-date because you didn't receive a response in four days is the way to go in situations like this. To quote the wiki:

First, you should flag the package out-of-date indicating details on why the package is outdated, preferably including links to the release announcement or the new release tarball. You should also try to reach out to the maintainer directly by email. If there is no response from the maintainer after two weeks, you can file an orphan request. See AUR submission guidelines#Requests for details.)

nikdog commented on 2023-06-01 17:39 (UTC) (edited on 2023-06-01 17:59 (UTC) by nikdog)

Wait... if this package doesn't provide pip3.9 and

% python3.9 -m pip

/usr/bin/python3.9: No module named pip

How does one use python3.9 to pip user install a github project?

EDIT: NVM, python3.9 -m ensurepip --upgrade and fixed. Is there a reason this doesn't provide a pip3.9 by default? or an installed pip module? Is it a pain in the ass? or does it just make the legacy support package lightweight?

fboerman commented on 2023-03-22 16:41 (UTC)

keep getting this error when building, could somebody help?

./install-sh -c -m 644 ./Tools/gdb/libpython.py python-gdb.py
cp: failed to clone './_inst.29441_' from './Tools/gdb/libpython.py': Operation not permitted
make: *** [Makefile:688: python-gdb.py] Error 1
make: *** Waiting for unfinished jobs....
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: python39

rixx commented on 2023-02-21 14:34 (UTC)

patch is part of base-devel, which is assumed to be present for AUR packages.

the-k commented on 2023-02-21 14:16 (UTC)

patch package should be added to makedepends.

rixx commented on 2022-11-17 17:14 (UTC)

Done.

wint3rmute commented on 2022-11-17 16:51 (UTC)

After the recent update of the openssl package, ssl module in python3.9 stopped working and it's no longer possible to install libraries from pip due to the following error:

pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.

Reinstalling this AUR package has solved the problem for me. @rixx, please consider incrementing the pkgrel or epoch to force a rebuild for all users.

gchamon commented on 2022-08-02 19:16 (UTC)

cloning the AUR repo, removing --without-ensurepip and installing with makepkg -si worked fine to bring pip and setuptools back to python3.9 (without which I was unable to develop for AWS Lambda -- which supports python<=3.9 -- using pipenv and private packages).

I couldn't reproduce the conflict with system pip. Isn't make altinstall to take care of that? That is strange. In any case if there were steps to reproduce the conflict I could try taking a look at the installation process.

rixx commented on 2022-03-17 13:10 (UTC) (edited on 2022-03-17 13:12 (UTC) by rixx)

I don't see what's the problem

@lahwaacz I thought I had put that in my comment, but apparently not? Updates do not apply, complaining that /usr/bin/pip or /bin/pip exists in the filesystem (I swear I had intended to put that in my comment, sorry). Shipping a PKGBUILD that doesn't allow people to update isn't great, so I reverted the change for now.

you could just add something like rm -f "${pkgdir}/usr/bin/pip"

As I said: I do not have the time right now, so I chose to revert the change that breaks the package for people. Either I get around to tinkering with the PKGBUILD when I'm not working insane hours, or somebody sends in a patch.

« First ‹ Previous 1 2 3 4 Next › Last »