I was hitting this exact same issue in one of my projects today. This
has always been a difficulty with integrating Koji's client library
into other projects.
It would be great to have Koji on PyPI.
Even if we could not do that, it would be great to simply have
setup.py at the root of the tree so I can install directly from
On Fri, Feb 3, 2017 at 8:04 AM, Pavol Babincak <pbabinca(a)redhat.com> wrote:
> I'm using koji as a python package in my scripts. Usually I develop them
> inside of a virtual environment. I do not use system packages in
> Currently I'm not able to install koji and it dependencies inside virtualenv
> easily. Having koji in PiPy would help me. That way I can just specify it in
> my requirements.txt or in install_requires of my setup.py. I *guess* one
> way to do that is to have setup.py in koji code and add some extra steps as
> part of the release process to publish it there.
> What do you think about this?
> For some time now I use my own setup.py. I guess it is not ready for PR so
> I'd love to see comments on this as well:
>  Among other reasons I'd like to have environment isolated from the
> system as much as possible.
>  I have never maintained package on PiPy.
> Pavol Babincak
> koji-devel mailing list -- koji-devel(a)lists.fedorahosted.org
> To unsubscribe send an email to koji-devel-leave(a)lists.fedorahosted.org