On Fri, Jan 25, 2019 at 02:14:52PM +0100, Johannes Berg wrote: > > Now I recognize parallel-vm.py does not work both python2 and 3. > > FWIW, I'm not sure I see a need to keep this python2 compatible. This is > a development thing, and there we should not have a problem to just > require python3. > > I see that it's not *that* much more work to keep it working on python2, > however, if the default remains python2 then people are only going to > break python3 support in the future again. > > And trying to keep it working on python2 will have exactly the same > problem - if python3 is the default then python2 will be broken quickly > ... so I'd say we should just switch, but Jouni should decide I guess :) Agreed. If it makes this any easier to manage, I would have no problems with moving all this from python2 to python3 (only) if everything continues to work after these changes. While I do not really like the way python language is updated without backwards compatibility, I obviously have python3 installed and can learn the new language requirements once needed ;-). The key requirement here really is that the test setup should be easy to use for anyone and if distros start strongly preferring python3 and potentially dropping python2 altogether, it is clear that things need to change here. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
