Package Details: python310 3.10.16-1

Git Clone URL: https://aur.archlinux.org/python310.git (read-only, click to copy)
Package Base: python310
Description: Next generation of the python high-level scripting language, version 3.10
Upstream URL: https://www.python.org/
Licenses: custom
Provides: python
Submitter: soh
Maintainer: soh
Last Packager: soh
Votes: 19
Popularity: 1.11
First Submitted: 2023-05-04 00:47 (UTC)
Last Updated: 2024-12-27 14:17 (UTC)

Dependencies (20)

Required by (13370)

Sources (1)

Latest Comments

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

soh commented on 2023-10-10 02:03 (UTC) (edited on 2023-10-10 02:14 (UTC) by soh)

@MarsSeed Thanks for your kind advice. You seem to also send this message to python39 and python38 packages. In my opinion, The python3X naming convention has come to existence for several years. It will make current users surprised and inconvenient if they use yay -Syu to upgrade their system. Also some official packages use naming convention like this too (without the -), e.g.:

We will not expect a python4 in the near future so I guess the three hundred and ten does not hampers the correction interpretation of version too much.

As for the provides field. I think the current one do follows the PKGBUILD on ArchWiki:

An array of additional packages that the software provides the features of (or a virtual package such as cron or sh). Packages providing the same item can be installed side-by-side, unless at least one of them uses a conflicts array. The version that the package provides should be mentioned (pkgver and potentially the pkgrel), in case packages referencing the software require one.

As for whether it is a drop-in replacement, in some sense, it is. It will give users great flexibility to rebuild all python-related packages against this specific version as long as there is no compatibility issues.

soh commented on 2023-10-10 01:47 (UTC)

@lachesis Sorry to hear about that. But my yay did these PGP keys importing work for me automatically. I guess you have to add auto-key-retrieve to the GPG configuration file?

MarsSeed commented on 2023-10-09 12:13 (UTC) (edited on 2023-10-09 12:16 (UTC) by MarsSeed)

Please kindly rename this package to python-3.10 to conform to Arch package naming guidelines (to the requirement that calls for attaching only the major version number directly to the package name, which in this case is 3 - three -, not 310 - three hundred and ten).

Also please remove the provides field. It is useless, and this package is not a drop-in replacement of repo's python package. Also, AUR helpers don't support versioned provides lookup.

Some good examples from repo:

Thank you in advance for your cooperation, and for maintaining this package.

lachesis commented on 2023-09-14 19:21 (UTC) (edited on 2023-09-14 19:21 (UTC) by lachesis)

I still receive the gpg error warning, even using yay. It tries to import 3 other keys:

:: PGP keys need importing:
 -> 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D, required by: python310
 -> E3FF2839C048B25C084DEBE9B26995E310250568, required by: python310
 -> A035C8C19219BA821ECEA86B64E628F8D684696D, required by: python310

Manually importing the key as requested works just fine, but why doesn't yay do that for me?

soh commented on 2023-06-18 14:45 (UTC)

@Jonny-Doe This seems to a benign warning. Also check here: https://bbs.archlinux.org/viewtopic.php?id=241153

Jonny-Doe commented on 2023-06-11 12:07 (UTC)

While building package, it throws a warning like this:

WARNING: Package contains reference to $srcdir

kaputtnik commented on 2023-05-13 08:33 (UTC)

@soh

Thanks that solved it.

soh commented on 2023-05-13 08:17 (UTC) (edited on 2023-05-13 08:18 (UTC) by soh)

@ kaputtnik If you run into this when using makepkg -si:

==> Verifying source file signatures with gpg...
    Python-3.10.11.tar.xz ... FAILED (unknown public key FFE87404168BD847)
==> ERROR: One or more PGP signatures could not be verified!

Simply running this will solve your problem

$ gpg --recv-key FFE87404168BD847
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key 64E628F8D684696D: public key "Pablo Galindo Salgado <pablogsal@gmail.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1

Use an AUR helper like yay, paru will also help.

diestl commented on 2023-05-11 15:13 (UTC)

@kaputtnik, you need to fetch the signing key used to sign the python 3.10 release. According to the download page from python.org, this is a key belonging to Pablo Galindo Salgado (https://www.python.org/downloads/).

You can fetch and import that key into your keyring with curl <url> | gpg --import -. The url you'll find on that download page.

kaputtnik commented on 2023-05-07 11:22 (UTC)

I get this gpg related error:

$:> LC_ALL=C makepkg ==> Making package: python310 3.10.11-1 (Sun May 7 13:14:51 2023) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found Python-3.10.11.tar.xz -> Found Python-3.10.11.tar.xz.asc ==> Validating source files with sha512sums... Python-3.10.11.tar.xz ... Passed Python-3.10.11.tar.xz.asc ... Skipped ==> Verifying source file signatures with gpg... Python-3.10.11.tar.xz ... FAILED (unknown public key FFE87404168BD847) ==> ERROR: One or more PGP signatures could not be verified!

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