Hi guys, currently most Python packages in the Build Service are inconsistently named. For instance, upstream 'pyenchant' is named python-enchant, 'Cheetah' is named python-cheetah. There are plenty of other examples. I'd like to propose a different scheme (much like our Ruby and Perl packages): * Python application packages are named like $UPSTREAM_NAME * Python libraries are named python-$UPSTREAM_NAME Upstream names means what is found on PyPi (pypi.python.org). PyPi names make the most sense as upstream projects names clash sometimes, PyPI names are unique. Here are some examples: * 'bpython' stay 'bpython' as it is an app * 'IPython' would become 'ipython', as this is the PyPi package name (not the app name) * 'python-enchant' becomes 'python-pyenchant' * 'python-cheetah' becomes 'python-Cheetah' * 'python-twitter' becomes 'python-python-twitter' While the last example doesn't look too fancy, this generally has huge advantages. First of all users now have a clue what to search for. More importantly, there's a clear dependency between package name and upstream name, which helps a lot for automatic spec file generation (BuildRequires/Requires). For some newer packages, this seem to have happened already. I'd suggest that when a new upstream version for a 'broken' package is available, an entirely new package (with correct name) is added and the old one obsoleted. Python applications should also Provide: python-$UPSTREAM_NAME to be compatible with the above scheme. As an example, I added the package 'python-pyenchant' to devel:languages:python, that obsoletes/provides the older 'python-enchant'. -------------------------------------------------------------------------------- Regarding BuildRequires/Requires, we may even want to adopt the Perl package scheme. For the package 'python-py2pack' this would look like: BuildRequires: python-devel BuildRequires: python(Jinja2) >= 2.5 BuildRequires: python(argparse) Requires: python(Jinja2) >= 2.5 Requires: python(argparse) This needs some tool support, off course. -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com