Package Details: python-kicadmodtree-git v1.1.2.r3307.401a7c67d-1

Git Clone URL: https://aur.archlinux.org/python-kicadmodtree-git.git (read-only, click to copy)
Package Base: python-kicadmodtree-git
Description: KiCad Footprint Generator, creating kicad footprints using python scripts
Upstream URL: https://gitlab.com/kicad/libraries/kicad-footprint-generator
Licenses: GPL
Conflicts: python-kicadmodtree
Provides: python-kicadmodtree
Submitter: rmsc
Maintainer: rmsc
Last Packager: rmsc
Votes: 0
Popularity: 0.000000
First Submitted: 2023-08-30 13:30 (UTC)
Last Updated: 2025-11-28 17:25 (UTC)

Latest Comments

micwoj92 commented on 2025-11-30 23:23 (UTC)

The upstream package actually seems to depend on python-future, so nothing I can do about that, really. Please open a bug report upstream:

How about you as a maintainer of this package take care of this? python-kicadmodtree package does not depend on python-futureso there is some discrepancy here.

I've updated the build system to the latest PEP, it now builds, but tests are failing.

This is also up to maintainer to check. It can be either upstream issue or something wrong with pkgbuild itself, it might require additional steps in order for tests to pass.

rmsc commented on 2025-11-28 17:28 (UTC)

The upstream package actually seems to depend on python-future, so nothing I can do about that, really. Please open a bug report upstream:

https://gitlab.com/kicad/libraries/kicad-footprint-generator/

I've updated the build system to the latest PEP, it now builds, but tests are failing.

dreieck commented on 2025-01-11 16:01 (UTC)

If possible, please remove the dependency on python-furure/ make the package working without python-future:

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

Regards and thanks for this package!