[oslo] [tooz] Why does not tooz's tox env use upper-constraints?
The question is the subject. Why does not tooz's tox env use upper-constraints? I asked this on IRC once some time ago but did not receive an answer so trying out ML as a more reliable medium. -yoctozepto
On Fri, May 7, 2021, at 12:24 PM, Radosław Piliszek wrote:
The question is the subject. Why does not tooz's tox env use upper-constraints?
I asked this on IRC once some time ago but did not receive an answer so trying out ML as a more reliable medium.
https://review.opendev.org/c/openstack/tooz/+/413365 is the change that added the comment about the exclusion to tox.ini. Reading the comments there it seems one reason people were skipping upper-constraints was to find problems with dependencies early (rather than avoiding them with constraints and updating when everyone was happy to work with it). Not sure if Tony is still following this list but may have more info too.
-yoctozepto
On 5/7/21 10:53 PM, Clark Boylan wrote:
On Fri, May 7, 2021, at 12:24 PM, Radosław Piliszek wrote:
The question is the subject. Why does not tooz's tox env use upper-constraints?
I asked this on IRC once some time ago but did not receive an answer so trying out ML as a more reliable medium.
https://review.opendev.org/c/openstack/tooz/+/413365 is the change that added the comment about the exclusion to tox.ini. Reading the comments there it seems one reason people were skipping upper-constraints was to find problems with dependencies early (rather than avoiding them with constraints and updating when everyone was happy to work with it).
Not sure if Tony is still following this list but may have more info too.
-yoctozepto
Hi, Another more social reason, is that the people behind Tooz (that are now not involved in the project) loved to do things their own way, and loved experimentation, even if this meant not always being fully aligned with the best practices of the rest of the OpenStack project. I'm sure old-timers will know what I'm talking about! :) Anyways, it's probably time to realign... Cheers, Thomas Goirand (zigo) P.S: This post is in no way a critic of the involved people or what they did (I actually enjoyed a lot interacting with them), I'm just exposing a fact...
Hello, I don't know the reason behind this choice, however, you should notice that tooz became an independent project a few weeks ago [1]. Usually independent projects (at least those under the Oslo scope) are not using U.C (e.g pbr by example). So, by taking account of the independent model, I wonder if we need a UC at this point. Any opinions or thoughts? [1] https://opendev.org/openstack/releases/commit/a0f4ef7053e00418ac4800e4d8428d... Le ven. 7 mai 2021 à 23:54, Thomas Goirand <zigo@debian.org> a écrit :
On Fri, May 7, 2021, at 12:24 PM, Radosław Piliszek wrote:
The question is the subject. Why does not tooz's tox env use upper-constraints?
I asked this on IRC once some time ago but did not receive an answer so trying out ML as a more reliable medium.
https://review.opendev.org/c/openstack/tooz/+/413365 is the change that added the comment about the exclusion to tox.ini. Reading the comments
On 5/7/21 10:53 PM, Clark Boylan wrote: there it seems one reason people were skipping upper-constraints was to find problems with dependencies early (rather than avoiding them with constraints and updating when everyone was happy to work with it).
Not sure if Tony is still following this list but may have more info too.
-yoctozepto
Hi,
Another more social reason, is that the people behind Tooz (that are now not involved in the project) loved to do things their own way, and loved experimentation, even if this meant not always being fully aligned with the best practices of the rest of the OpenStack project. I'm sure old-timers will know what I'm talking about! :)
Anyways, it's probably time to realign...
Cheers,
Thomas Goirand (zigo)
P.S: This post is in no way a critic of the involved people or what they did (I actually enjoyed a lot interacting with them), I'm just exposing a fact...
-- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----
On Mon, May 10, 2021 at 11:15 AM Herve Beraud <hberaud@redhat.com> wrote:
Hello,
I don't know the reason behind this choice, however, you should notice that tooz became an independent project a few weeks ago [1].
Usually independent projects (at least those under the Oslo scope) are not using U.C (e.g pbr by example). So, by taking account of the independent model, I wonder if we need a UC at this point.
Any opinions or thoughts?
[1] https://opendev.org/openstack/releases/commit/a0f4ef7053e00418ac4800e4d8428d...
Oh, that is enough of a reason, thanks. :-) Also, thanks to others for providing the historical background. Cheers, -yoctozepto
participants (4)
-
Clark Boylan
-
Herve Beraud
-
Radosław Piliszek
-
Thomas Goirand