On 27.05.2013 22:36, Zack Buhman wrote:

I was in the process of creating a python3 package [1] for flask, but I've noticed python2-flask [2] seems to conflicts+replace "python-flask". I imagine this was for historical reasons, but this introduces probably unintentional behavior when a package provides python-flask (the python3 version of flask):

:: python-flask-git and python2-flask are in conflict (python-flask). Remove python2-flask? [y/N]

Would it be appropriate to (directly) contact said TU about his package, or is it innappropriate to expect TUs to yield to AUR packages/maintainers?

Thanks.

[1] http://ix.io/5OI [2] https://www.archlinux.org/packages/community/any/python2-flask/

This should be considered a bug. I fixed the package and pushed it. However, is there really any merit in making a python-flask-git package? flask doesn't even work on python3. Next time please just contact me directly for tiny things like these. For bigger stuff, report bugs. Sven

On 28.05.2013 00:28, Zack Buhman wrote:

On Tue, May 28, 2013 at 12:19:49AM +0200, Sven-Hendrik Haase wrote:

...

Next time please just contact me directly for tiny things like these. I'll keep this in mind.

...

This should be considered a bug. I fixed the package and pushed it. Thanks.

...

However, is there really any merit in making a python-flask-git package? Yes, for a flask package for python3.

...

flask doesn't even work on python3. I'm afriad upstream disagrees with you. They haven't made a release yet, however, thus the -git package.

Oh, I wasn't aware of the sprint branch which apparently aims for python3 support. I, for one, would appreciate python3 support.