Dne 3.2.2017 v 16:04 Pavol Babincak napsal(a):
Hi,
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[1] in
virtualenv.
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*[2] 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?
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.
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:
https://pagure.io/fork/pbabinca/koji/blob/setup_WIP/f/setup.py
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.
[1] Among other reasons I'd like to have environment isolated from the
system as much as possible.
[2] I have never maintained package on PiPy.
--
Tomas Kopecek <tkopecek(a)redhat.com>
Release Engineering Development, RedHat