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?
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
[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.
Hi Pavol,
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 Git/Pagure.
- Ken
On Fri, Feb 3, 2017 at 8:04 AM, Pavol Babincak pbabinca@redhat.com wrote:
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?
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
[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.
Pavol Babincak _______________________________________________ koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
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.
On Wed, Feb 08, 2017 at 10:32:11AM +0100, Tomas Kopecek wrote:
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.
+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 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@redhat.com> Release Engineering Development, RedHat
koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
Guys, Try to add rpm-py-installer to the setup.py install_requires, that I developed recently. https://github.com/junaruga/rpm-py-installer
This installs the rpm python module from PyPI. This has been used in a project rebase-helper. https://github.com/rebase-helper/rebase-helper/blob/master/setup.py#L82
My apologies for my terrible mails.
I tried to post many times after joining this mailing list yesterday and today. Because I could not receive it.
Please delete those mails.
I am sorry.
Jun
On Mon, Sep 18, 2017 at 4:49 PM, Jun Aruga jaruga@fedoraproject.org wrote:
Guys, Try to add rpm-py-installer to the setup.py install_requires, that I developed recently. https://github.com/junaruga/rpm-py-installer
This installs the rpm python module from PyPI. This has been used in a project rebase-helper. https://github.com/rebase-helper/rebase-helper/blob/master/setup.py#L82 _______________________________________________ koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
Guys,
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
Try to add rpm-py-installer to the setup.py install_requires, that I developed recently for an another project. https://github.com/junaruga/rpm-py-installer
This installs the rpm python module from PyPI.
This has been used in a project rebase-helper. https://github.com/rebase-helper/rebase-helper/blob/master/setup.py#L82
Guys
https://pagure.io/fork/pbabinca/koji/blob/setup_WIP/f/setup.py # In a perfect world this would suffice: # 'rpm', # But rpm isn't available on PyPI so it needs to be installed other way.
Try to add `rpm-py-installer` in the `setup.py` `install_requires`.
This is a installer to install the rpm python package from PyPI, I developed recently, facing same kind of situation in another project.
https://github.com/junaruga/rpm-py-installer
This has been used in a project 'rebase-helper`. https://github.com/rebase-helper/rebase-helper/blob/master/setup.py#L82
Friendly ping on this.
I ran into an issue in a separate project that would benefit from this. Just linking the two together: https://github.com/fedora-infra/pdc-updater/issues/26
Hi Ralph,
The discussion is also in this page: https://pagure.io/koji/issue/458
The reason of that koji not in pypi is the dependency python module "rpm-python" is not in pypi. And there is a reason that RPM project does not manage "rpm-python" in pypi [1].
Now I am working for the installer to install rpm-python from pypi with high priority.
I was success to remove rpm-devel dependency from the installer. But I have to remove one more devel dependency from the installer before the new version release of the installer. After that, koji can use the installer and download rpm-python from pypi.
[1] https://github.com/rpm-software-management/rpm/issues/273
Jun
On Tue, Oct 3, 2017 at 8:28 PM, Ralph Bean rbean@redhat.com wrote:
Friendly ping on this.
I ran into an issue in a separate project that would benefit from this. Just linking the two together: https://github.com/fedora- infra/pdc-updater/issues/26 _______________________________________________ koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
Dne 3.10.2017 v 20:28 Ralph Bean napsal(a):
Friendly ping on this.
I ran into an issue in a separate project that would benefit from this. Just linking the two together: https://github.com/fedora-infra/pdc-updater/issues/26 _______________________________________________ koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
I've uploaded koji-1.14 to testpypi. But as Jun Aruga mentioned, I'm waiting for his fixes, so we don't need manual step in virtualenvs, for production PyPi.
https://testpypi.python.org/pypi/koji
Tomas and Ralph,
I released the new version of the installer that does not need rpm-devel now.
The detail is here. https://pagure.io/koji/issue/458#comment-470467
Regards, Jun
On Wed, Oct 4, 2017 at 12:44 PM, Tomáš Kopeček tkopecek@redhat.com wrote:
Dne 3.10.2017 v 20:28 Ralph Bean napsal(a):
Friendly ping on this.
I ran into an issue in a separate project that would benefit from this. Just linking the two together: https://github.com/fedora-infr a/pdc-updater/issues/26 _______________________________________________ koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
I've uploaded koji-1.14 to testpypi. But as Jun Aruga mentioned, I'm waiting for his fixes, so we don't need manual step in virtualenvs, for production PyPi.
https://testpypi.python.org/pypi/koji
--
Tomas Kopecek <tkopecek@redhat.com> Release Engineering Development, RedHat
koji-devel mailing list -- koji-devel@lists.fedorahosted.org To unsubscribe send an email to koji-devel-leave@lists.fedorahosted.org
koji-devel@lists.stg.fedorahosted.org
-
Jun Aruga -
Jun Aruga -
Ken Dreyer -
Matt Prahl -
Pavol Babincak -
Ralph Bean -
Tomas Kopecek -
Tomáš Kopeček