Peter Otten >Those who regularly need different configurations probably use virtualenv, >or virtual machines when the differences are not limited to Python.
Use tox for this. https://testrun.org/tox/latest/ However for development purposes it often helps to have a --force the_one_that_I_want option (for command lines) or a global variable, or a config file for modules. How badly you want this depends on your own personal development style, and how happy you are popping in and out of virtualenvs. Many people prefer to write their whole new thing for one library (say elementtree) and then test it/port it against the other 2, one at a time, making a complete set of patches for one adaptation at a time. Other people prefer to write their code so that, feature by feature they first get it to work with one library, and then with another, and then with the third, and then they write the next new bit of code, so that they never have to do a real port. Life is messy enough that you often do a bit of this and a bit of the other thing, even if you would prefer to not need to, especially if hungry customers are demanding exactly what they need (and we don't care about the other ways it will eventually work for other people). Laura _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
