Hi, I can't give you the advise for a concrete version anyway there are lot of arguments given by the other posters. BUT there is a way how you can circumvent the problem to some extend:
Are you intending to use Jenkins? I don't want to convince you here why to use Jenkins but maybe I don't need to and THEN you just install the ShiningPanda plugin and each time your project is build automatically because of a change all tests are running across multiple Python versions. This way you won't have too many problems to switch to another newer Python version. Keep the build "green". > > What is the general feel of /this/ community? I'm about to start a > > large scale Python project. Should it be done in 2 or 3? What are the > > benefits, aside from the 'it's the future' argument? -- https://mail.python.org/mailman/listinfo/python-list
