Guidelines say: ... There is an exception to this rule. If the upstream source has "py" (or "Py") in its name, you can use that name for the package. So, for example, pygtk is acceptable ... Ergo, why is it python-tag instead of the upstream 'tagpy'? Additional info:
Well, the guidelines say "can", not "must" or even "should"... and since I really like the idea of isolating as much as possible extensions and modules under a particular package namespace, I went for "python-tag". I've added "Provides: tagpy = %{version}-%{release}" for the next devel rebuild, so that "yum install tagpy" at least works, if it can make things less confusing.