On Wed, Feb 08, 2017 at 10:32:11AM +0100, Tomas Kopecek wrote:
Dne 3.2.2017 v 16:04 Pavol Babincak napsal(a):
>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
>What do you think about this?
If there is not too much hassle around that (and I've scanned through the
PyPi docs and it seems, that release is one-liner) we can possibly do that.
Not sure yet, how it deals with our prehistorical python compatibility, but
if some people are using it this way, it is worth to explore.
+1. This would be very nice. I would use it everywhere!
A snag you may run into is that the 'rpm' library (a dependency) is
not on pypi. If you can make that optional to install the koji client
lib, that would be best from my PoV.
>For some time now I use my own setup.py. I guess it is not ready
>so I'd love to see comments on this as well:
I would say, it's still worth to open PR, so we can discuss it in pagure,
which is still little bit more visible than this mailing list.
> Among other reasons I'd like to have environment isolated from the
>system as much as possible.
> I have never maintained package on PiPy.
Tomas Kopecek <tkopecek(a)redhat.com>
Release Engineering Development, RedHat
koji-devel mailing list -- koji-devel(a)lists.fedorahosted.org
To unsubscribe send an email to koji-devel-leave(a)lists.fedorahosted.org