Search Criteria
Package Details: pip2pkgbuild 0.5.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/pip2pkgbuild.git (read-only, click to copy) |
---|---|
Package Base: | pip2pkgbuild |
Description: | Create PKGBUILD files for Python modules fetched with PIP |
Upstream URL: | https://github.com/wenLiangcan/pip2pkgbuild |
Keywords: | packaging pip pkgbuild python |
Licenses: | MIT |
Conflicts: | python2-pip2pkgbuild |
Submitter: | wenLiangcan |
Maintainer: | RubenKelevra |
Last Packager: | RubenKelevra |
Votes: | 25 |
Popularity: | 0.007117 |
First Submitted: | 2015-09-15 12:49 (UTC) |
Last Updated: | 2024-08-09 05:27 (UTC) |
Dependencies (5)
- python (python37AUR, python311AUR, python310AUR)
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
Latest Comments
« First ‹ Previous 1 2 3 4 Next › Last »
mreeves87 commented on 2024-05-05 05:13 (UTC)
It looks like the upstream package is itself incompatible with python 3.12.
frankspace commented on 2023-12-16 19:46 (UTC)
Nope. I still need to install python-setuptools. If I don't, I get the following error:
I may not be understanding this correctly, but it looks as if pip2pkgbuild permits creation of PEP517 PKGBUILDs, not necessarily that it is itself a PEP517 package. According to section 4.2 of the wiki, if there's no pyproject.toml or build-system table, and it has a setup.py file, then it uses setuptools or distutils; and I notice the upstream package does in fact have a setup.py file in it.
wenLiangcan commented on 2023-12-06 12:54 (UTC)
Added python-wheel, according to the wiki only those three packages are required as mkdepends for PEP517 based package. Let me know if you encounter problem without python-setuptools.
frankspace commented on 2023-12-03 18:58 (UTC)
This will not compile in a chroot for me without also explicitly installing python-setuptools and python-wheel. I don't know whether those are dependencies or makedependencies, but would you please consider adding them as some kind of dependencies? Thank you!
jose1711 commented on 2023-11-09 13:16 (UTC)
conflicts with
python2-pip2pkgbuild
wenLiangcan commented on 2023-08-14 13:17 (UTC)
Alright, done.
MarsSeed commented on 2023-08-13 02:18 (UTC)
In that case, it would be welcome if you could create a separate PKGBUILD for the Python2 variant.
For those who want to use python-aur-deploy, having to compile and install python2 is an extra and unnecessary burden, wasted time, and additional source of potential build failure.
wenLiangcan commented on 2023-08-13 02:10 (UTC)
That’s an option for users who want to use Python 2. It maybe is not useful for you, but not everyone else.
MarsSeed commented on 2023-08-13 01:01 (UTC)
Please kindly remove the unused python2 subpackage.
« First ‹ Previous 1 2 3 4 Next › Last »