<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hi - <br></div><div><br></div><div>Also bit by sudden changes in tox 4, and I think it's important that the tox maintainers know that they did not adequately warn for these changes. our jobs should not be "breaking" without us having adequate warnings from previous tox versions.<br></div><div><br></div><div>My issue at <a href="https://github.com/tox-dev/tox/issues/2676">https://github.com/tox-dev/tox/issues/2676</a> has been locked and the maintainer does not seem to think tox did anything incorrectly here. Pretty concerning for such a foundational project, so I would encourage new issues be raised at <a href="https://github.com/tox-dev/tox/issues/2676">https://github.com/tox-dev/tox/issues/</a> regarding individual backwards-incompatible changes that were made without warnings. <br></div><div><br></div><div>On Wed, Dec 7, 2022, at 2:19 PM, Jeremy Stanley wrote:<br></div><blockquote type="cite" id="qt" style=""><div>Tox 4.0.0, a major rewrite, just appeared on PyPI in the past couple<br></div><div>of hours, so jobs are breaking right and left. We're going to try<br></div><div>pinning to latest 3.x in zuul-jobs for the near term while we work<br></div><div>through some of the more obvious issues with it, but until then lots<br></div><div>of tox-based Zuul jobs are going to be broken. I'll follow up to<br></div><div>this thread once we think things should be stabilized and we can<br></div><div>start trying to pick through what's going to need fixing for the new<br></div><div>tox version.<br></div><div>-- <br></div><div>Jeremy Stanley<br></div><div><br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>signature.asc<br></li></ul></blockquote><div><br></div></body></html>