Search Criteria
Package Details: pipdeptree 4.2.5-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/pipdeptree.git (read-only, click to copy) |
|---|---|
| Package Base: | pipdeptree |
| Description: | Command line utility to show dependency tree of Python packages |
| Upstream URL: | https://github.com/tox-dev/pipdeptree |
| Keywords: | cli dependency python tree |
| Licenses: | MIT |
| Submitter: | SpotlightKid |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 12 |
| Popularity: | 0.79 |
| First Submitted: | 2015-12-02 21:32 (UTC) |
| Last Updated: | 2026-09-08 18:35 (UTC) |
Dependencies (12)
- glibc (glibc-gitAUR, glibc-git-native-pgoAUR, glibc-eacAUR)
- libgcc (libgcc-fast-optimizedAUR, libgcc-snapshotAUR)
- python
- python-nabAUR
- python-nab-indexAUR
- python-nab-projectAUR
- cargo (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rust, rustup) (make)
- meson-python (make)
- python-build (make)
- python-installer (make)
- python-ninjaAUR (make)
- python-wheel (make)
Latest Comments
1 2 Next › Last »
flylightning commented on 2026-09-04 15:48 (UTC)
There's issue of upgrading pipdeptree with paru shows error when tries to replace python-nab-python with python-nab-provider:
My workaround is remove the pipdeptree package then install it again:
Other workaround maybe is to ignore dependency checks when upgrade with sth. like
-d, I did not test it and I do not careyochananmarqos commented on 2026-07-22 14:10 (UTC)
@Dominiquini: An Arch Package Maintainer asked me to switch my AUR Python packages from using PyPI to use the source repo while he was importing a few to the repos. I forget what the reasoning was now.
Dominiquini commented on 2026-07-21 23:23 (UTC)
@yochananmarqos: What is the problem in using the PyPI version instead of the GitHub?
yochananmarqos commented on 2026-07-21 22:44 (UTC) (edited on 2026-07-21 22:45 (UTC) by yochananmarqos)
@Dominiquini: No worries. Now you can use
pipdeptreeto help you with your other Python AUR packages; i.e.,Dominiquini commented on 2026-07-21 21:13 (UTC)
@yochananmarqos: Sorry about that—I should have waited for your reply! Since you were active in the thread, I figured that if you didn't want to be involved, you'd simply remove yourself... I'm glad you accepted. I think I'll disown myself, since I don't have much to contribute here! Thanks.
yochananmarqos commented on 2026-07-21 18:18 (UTC)
@Dominiquini: Sure, I'll be a Co-Maintainer...oh, I see I already am.
By the way, it's polite to ask if someone wants to be a Co-Maintainer before adding them. ;)
Dominiquini commented on 2026-07-21 18:13 (UTC)
@yochananmarqos: I copied from other python packages that I maintain! I don't quite understand how compiling Python projects works... Are you interested in being a co-maintainer of the package?
yochananmarqos commented on 2026-07-21 18:09 (UTC) (edited on 2026-07-21 18:14 (UTC) by yochananmarqos)
@Dominiquini: As I mentioned, only one build backend is used in a project. Since
meson-python/python-ninjais the new backend,python-setuptoolsandpython-hatchling/python-hatch-vcsare no longer required.Also, the 4.10 release was only for PyPI.
yochananmarqos commented on 2026-07-21 16:07 (UTC)
@Dominiquini: The architecture is now 'x86_64' as it includes an ELF file. Only one Python build backend is ever required and every one included is not needed. As @patlefort mentioned, it requires
meson-python&python-ninjato build.See my PKGBUILD.
1 2 Next › Last »