From: Doug Hellmann d...@doughellmann.com
To: openstack-dev openstack-dev@lists.openstack.org
Date: 07/28/2015 07:59 PM
Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
from requirements.txt
snip
I replied on both patches, but I'll repeat it here for a broader
audience
On 30 July 2015 at 02:48, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Louis Taylor's message of 2015-07-29 15:25:33 +0100:
On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
I replied on both patches, but I'll repeat it here for a broader
audience:
Please set up
] [glance] Removing python-swiftclient
from requirements.txt
snip
I replied on both patches, but I'll repeat it here for a broader
audience:
Please set up an extras entry for each backend instead of just
removing the dependencies. That will signal to users that you know
what dependencies
On 7/29/15, 13:27, William M Edmonds edmon...@us.ibm.com wrote:
From: Doug Hellmann d...@doughellmann.com
To: openstack-dev openstack-dev@lists.openstack.org
Date: 07/28/2015 07:59 PM
Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
from requirements.txt
snip
I
So helpful! Thank you.
On Wed, Jul 29, 2015 at 7:48 AM, Doug Hellmann d...@doughellmann.com
wrote:
There is some documentation in the pbr manual
(http://docs.openstack.org/developer/pbr/#extra-requirements). The
feature is implemented throughout the packaging tool chain now.
Ah,
On 2015-07-28 19:25:04 -0700 (-0700), Clay Gerrard wrote:
[...]
I'd be more curious for the documentation if you have any idea where I
might look for it? Is this a feature of pkg_resources, distutils,
setuptools, pbr? What exactly does describing dependencies via this
extras key afford?
Excerpts from Clay Gerrard's message of 2015-07-28 19:25:04 -0700:
Doug,
I believe our glance friends are not the only project with some open
questions on dealing with the required dependency for optional plugin
use-case. You've made a recommendation to leverage some python tooling
Excerpts from Louis Taylor's message of 2015-07-29 15:25:33 +0100:
On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
I replied on both patches, but I'll repeat it here for a broader
audience:
Please set up an extras entry for each backend instead of just
removing the
On Tue, Jul 28, 2015 at 07:55:54PM -0400, Doug Hellmann wrote:
I replied on both patches, but I'll repeat it here for a broader
audience:
Please set up an extras entry for each backend instead of just
removing the dependencies. That will signal to users that you know
what dependencies
for
example our gate) glance itself should not have hard dependencies for 'em.
- Erno
From: William M Edmonds [mailto:edmon...@us.ibm.com]
Sent: Monday, July 27, 2015 10:42 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Removing python-swiftclient from
On 07/27/2015 11:42 PM, William M Edmonds wrote:
python-swiftclient is only needed by operators that are using the swift
backend, so it really doesn't belong in requirements.txt. Listing it in
requirements forces all operators to install it, even if they're not
going to use the swift backend.
From: Flavio Percoco fla...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 07/28/2015 07:36 AM
Subject: Re: [openstack-dev] [glance] Removing python-swiftclient
from requirements.txt
On 28/07/15 09:15 +, Kuvaja, Erno
://review.openstack.org/#/c/203200/
[3] https://review.openstack.org/#/c/203242/
- Erno
From: William M Edmonds [mailto:edmon...@us.ibm.com]
Sent: Monday, July 27, 2015 10:42 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Removing python
Doug,
I believe our glance friends are not the only project with some open
questions on dealing with the required dependency for optional plugin
use-case. You've made a recommendation to leverage some python tooling
functionality that I'm not familiar with. I was hoping I could probe you
to
On 28/07/15 10:29 +0200, Thomas Goirand wrote:
On 07/27/2015 11:42 PM, William M Edmonds wrote:
python-swiftclient is only needed by operators that are using the swift
backend, so it really doesn't belong in requirements.txt. Listing it in
requirements forces all operators to install it, even
- Erno
From: William M Edmonds [mailto:edmon...@us.ibm.com]
Sent: Monday, July 27, 2015 10:42 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Removing python-swiftclient from
requirements.txt
python-swiftclient is only needed by operators that are using the swift
python-swiftclient is only needed by operators that are using the swift
backend, so it really doesn't belong in requirements.txt. Listing it in
requirements forces all operators to install it, even if they're not going
to use the swift backend. When I proposed a change [1] to move this from
17 matches
Mail list logo
