Re: [openstack-dev] [all] Secrets of edit-constraints

[Akihiro Motoki]

Thanks Tony for the confirmation.

We have various variants of tox_install.sh. I just wondered we need to
fix it globally
or it depends on someone's development environment.

Anyway we can improve tox_install.sh for more general way :)

Thanks,
Akihiro

2017-08-16 18:14 GMT+09:00 Tony Breeds :
> On Mon, Aug 14, 2017 at 08:36:33AM +, Csatari, Gergely (Nokia - 
> HU/Budapest) wrote:
>> Hi,
>>
>> I have an interesting situation with the parametrization of edit-constraints 
>> in tools/tox_install.sh. This happens at the moment in neutron-lib, but as 
>> amotoki pointed out in [1] the same should happen in any projects (and 
>> actually was happening with me in Vitrage and Mistral).
>>
>> Here is what I experience:
>> With the current parameters of edit-constraints (edit-constraints $localfile 
>> -- $LIB_NAME "-e file://$PWD#egg=$LIB_NAME") the library itself (neutron-lib 
>> in this case) is added to upper-constraints.txt and the installation fails 
>> with "Could not satisfy constraints for 'neutron-lib': installation from 
>> path or url cannot be constrained to a version".
>> If I modify the parameters of edit-constraints in a way that it removes the 
>> library (neutron-lib in this case) instead of adding (edit-constraints 
>> $localfile $LIB_NAME --) it my build succeeds (as I'm playing with api-ref I 
>> use tox -r -e api-ref, but the same also happens with tox -r -e pep8).
>>
>> Is this happening with only me?
>
> No using edit-constraints to remove an item from the constrained set so
> you can use the current developement (git SHA) is the right things to
> do.
>
> Many of the project in the scenario you're describing do just that.
>
> Yours Tony.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Secrets of edit-constraints

[Tony Breeds]

On Mon, Aug 14, 2017 at 08:36:33AM +, Csatari, Gergely (Nokia - 
HU/Budapest) wrote:
> Hi,
> 
> I have an interesting situation with the parametrization of edit-constraints 
> in tools/tox_install.sh. This happens at the moment in neutron-lib, but as 
> amotoki pointed out in [1] the same should happen in any projects (and 
> actually was happening with me in Vitrage and Mistral).
> 
> Here is what I experience:
> With the current parameters of edit-constraints (edit-constraints $localfile 
> -- $LIB_NAME "-e file://$PWD#egg=$LIB_NAME") the library itself (neutron-lib 
> in this case) is added to upper-constraints.txt and the installation fails 
> with "Could not satisfy constraints for 'neutron-lib': installation from path 
> or url cannot be constrained to a version".
> If I modify the parameters of edit-constraints in a way that it removes the 
> library (neutron-lib in this case) instead of adding (edit-constraints 
> $localfile $LIB_NAME --) it my build succeeds (as I'm playing with api-ref I 
> use tox -r -e api-ref, but the same also happens with tox -r -e pep8).
> 
> Is this happening with only me?

No using edit-constraints to remove an item from the constrained set so
you can use the current developement (git SHA) is the right things to
do.

Many of the project in the scenario you're describing do just that.

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Secrets of edit-constraints

[Csatari, Gergely (Nokia - HU/Budapest)]

Hi,

I have an interesting situation with the parametrization of edit-constraints in 
tools/tox_install.sh. This happens at the moment in neutron-lib, but as amotoki 
pointed out in [1] the same should happen in any projects (and actually was 
happening with me in Vitrage and Mistral).

Here is what I experience:
With the current parameters of edit-constraints (edit-constraints $localfile -- 
$LIB_NAME "-e file://$PWD#egg=$LIB_NAME") the library itself (neutron-lib in 
this case) is added to upper-constraints.txt and the installation fails with 
"Could not satisfy constraints for 'neutron-lib': installation from path or url 
cannot be constrained to a version".
If I modify the parameters of edit-constraints in a way that it removes the 
library (neutron-lib in this case) instead of adding (edit-constraints 
$localfile $LIB_NAME --) it my build succeeds (as I'm playing with api-ref I 
use tox -r -e api-ref, but the same also happens with tox -r -e pep8).

Is this happening with only me?

Thanks,
Gerg0

[1]: https://review.openstack.org/#/c/492158/1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev