At the summit last week there were some discussions about limitations of tox and how they affect our use of constraints. It looks like contributing to tox may be getting easier, so it's possible that some of the ideas floated at the summit (like adding separate install commands or a "prepare virtualenv" command setting) could be possible.
Doug --- Begin forwarded message from holger krekel --- From: holger krekel <hol...@merlinux.eu> To: Testing in Python <testing-in-pyt...@lists.idyll.org>, pytest-dev <pytest-...@python.org> Date: Fri, 04 Nov 2016 10:53:16 +0100 Subject: [TIP] new tox-dev mailing list on python Hey all, thanks to Mark Sapiro we now have a dedicated mailing list (tox-dev at python.org) and it's even using Mailman3 :) Please subscribe here: https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org We also recently moved tox development to github: https://github.com/tox-dev/tox I am more than happy to give people commit/push/merge rights, especially those who contributed already. I take the opportunity to thank Oliver Bestwalter for stepping up to sort through issueslately. Some of the activity around tox also was possible thanks to the 2016 python testing sprint which was crowdfunded. So thanks to those who contributed at the sprint and for the sprint. Next up is getting a nice logo for tox[1]. So don't hesitate to join tox-dev ML to influence what logo tox is going to have :) best, holger [1] I suggest we use a bit of the remaining crowd-funds to give some money to whoever comes up with a nice logo design. --- End forwarded message --- __________________________________________________________________________ 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