Package Details: python-quantities 0.16.2-1

Git Clone URL: https://aur.archlinux.org/python-quantities.git (read-only, click to copy)
Package Base: python-quantities
Description: Support for physical quantities with units, based on NumPy
Upstream URL: https://github.com/python-quantities/python-quantities
Licenses: BSD-3-Clause
Submitter: Axon
Maintainer: iyanmv
Last Packager: iyanmv
Votes: 7
Popularity: 0.67
First Submitted: 2017-03-29 07:06 (UTC)
Last Updated: 2025-11-03 11:47 (UTC)

Latest Comments

1 2 Next › Last »

iyanmv commented on 2025-11-08 13:20 (UTC)

micwoj92: for Python it gives tons of false positives and innocuous warnings.

micwoj92 commented on 2025-11-08 00:35 (UTC)

I understand namcap is only a tool, it lacks in lots of way (ruby, perl pkgs for example) but for python it is useful in finding dependency warnings/errors.

micwoj92 commented on 2025-11-08 00:34 (UTC)

It says "may or may not be listed". Well, you prefer one way I prefer the other. Whenever I build a package I find it I just comment it. I use the tooling and it says warning, so when I see it I try to find a way to silence it, in this case it would be by adding python to dependencies.

If you find anything in packages I (co)maintain (of if I was previous maintainer and is orphaned now) I will gladly have it updated and fixed.

iyanmv commented on 2025-11-08 00:02 (UTC)

micwoj92: I would appreciate good feedback and interesting suggestions, but this is not. And just after 2 mins checking your PKGBUILDs, I saw a few errors. So why don't you put the same effort in reviewing your PKGBUILDs and fixing the namcap errors (not warnings) in your own packages?

iyanmv commented on 2025-11-07 23:54 (UTC)

micwoj92: Do you mind sharing the exact point in the guidelines you refer to? Have you read this, for example?

In some cases this is not necessary and may or may not be listed, for example glibc cannot be uninstalled as every system needs some C library, or python for a package that already depends on another python- module, as the second module must per definition depend on python and cannot ever stop pulling it in as a dependency.

Honestly, I think this discussion is pointless. PKGBUILD is not broken, package builds correctly, and a namcap warning is a warning, not an error. From its manpage:

Warnings (designated by 'W:') are things that namcap thinks should be changed but if you know what you're doing then you can leave them.

I think I know what I'm doing.

micwoj92 commented on 2025-11-07 23:46 (UTC)

As python is direct dependency, I think it is a good reason to do this. It is a warning for a reason and that reason is package guidelines.

iyanmv commented on 2025-11-07 22:07 (UTC)

micwoj92: you keep asking this (like here) without giving a good reason. Just ignore the warnings from namcap. I only add python as dependency when it is needed, i.e., the package does not depend on any other python package. In this case, the dependency is clear since it depends on python-numpy, which depends on python (and many other things).

iyanmv commented on 2025-11-07 21:22 (UTC)

micwoj92: Why?

micwoj92 commented on 2025-11-07 21:01 (UTC)

Please add python to deps.

CatherineH commented on 2014-06-23 23:16 (UTC)

I installed this package without any problems, but if I go into python2 and try to import quantities, it says: [c2hollow@bluerocket python2-quantities]$ python2 Python 2.7.7 (default, Jun 3 2014, 01:46:20) [GCC 4.9.0 20140521 (prerelease)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import quantities Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named quantities

1 2 Next › Last »