python-sig in pkgdb2?

Thomas Spura tomspur at
Tue Oct 7 13:41:23 UTC 2014

2014-10-07 9:10 GMT+02:00 Bohuslav Kabrda <bkabrda at>:
> ----- Original Message -----
>> Hi all,
>> there just was a request to test groups for pkgdb2 [1] and I thought
>> it might be a good opportunity to maybe start sharing at least some
>> core python packages among a few people.
>> For instance, I maintain ipython and the dependency chain when other
>> maintainers chose to orphan something I need for it (or ipython
>> introduces a new dependency). Such packages are good candidates to be
>> maintained by a group of people, so updates can be managed better and
>> several people have an eye on them.
>> What do others think about that? Who else would be interested in
>> starting a common python-sig group in pkgdb2?
> I'm generally +1 for this, although I think people should still first try to contact the primary maintainer and then patch things themselves. For example, in python{,3}.spec, we're trying to follow a certain style of patch naming to keep things consistent and it's very disconcerting when a proven packager who needs to fix something creates a patch that completely ignores this...
> But yeah, I do agree that this is a good idea :)

All members of the python-sig group have commit rights, no matter if
they are proven packagers or "just" members.

Hmm, maybe python{2,3}, pypy etc can be left out of the python-sig? I
really think that nobody of that group will touch the main python
package unless they really know what they do or file a bug instead...

> Will you start the group, Tom?

I will. Thanks for all the feedback.

>> Greetings,
>>     Tom
>> [1]
> --
> Regards,
> Slavek Kabrda
> _______________________________________________
> python-devel mailing list
> python-devel at

More information about the python-devel mailing list