[aur-general] python2-simpleparse replaces python-simpleparse / balazar removal

Joao Cordeiro jlcordeiro at gmail.com
Wed Dec 15 06:45:39 EST 2010

On Wed, Dec 15, 2010 at 11:30 AM, Martti Kühne <mysatyre at gmail.com> wrote:

> python-simpleparse [1] is not supporting python 3.x atm. I just
> uploaded a package with correct naming.

> cheers
> mar77i

On Wed, Dec 15, 2010 at 11:41 AM, Evangelos Foutras <foutrelis at gmail.com>wrote:

> On Wed, Dec 15, 2010 at 1:30 PM, Martti Kühne <mysatyre at gmail.com> wrote:
> Deleted both of them, thanks.

It seems to me that having two packages (python-* and python2-*) would make
sense only if that package worked _both_ with python2 and python3. In this
particular case, where simpleparse works with python2 only, I don't
understand why we can't have it with the original name depending on python2.
There are two main advantages:
1) You don't have unnecessary dupes, making it easier for someone searching
for packages. Also you would avoid having a package that does not work but
isn't outdated or needing any kind of work (besides changing python
2) Someone who installed python-simpleparse some months ago would have his
package updated and working without any extra work.

Please understand that I'm just a normal user and my opinion is worth almost
nothing. However, because I adopted a few fine packages that only needed
some python2 work, I really wanted to bring this up and understand what is
the better way to solve it.

Should all foo packages that stopped working because of python3 be deleted
and replaced with python2-foo? It doesn't make any sense to me.

More information about the aur-general mailing list