On Sun, Aug 23, 2015 at 11:22 AM, Simon Ward <si...@bleah.co.uk> wrote: > > > On 23 August 2015 00:06:44 BST, Chris Angelico <ros...@gmail.com> wrote: >>Precisely. Every time you support multiple versions of some >>dependency, you have to test your code on all of them, and in the >>common case (new features added in newer versions), you have to target >>the oldest and weakest version. > > Just don't add features to older versions. They're in maintenance or bugfix > mode.
That's not what I'm talking about... I'm talking about multiple versions of a dependency. If I write a Python script, and tell people "this requires CPython 3.6 running on Linux" because that's what I run... it's not going to be easy to use. Telling people that it requires Python 3.4 or newer cuts out a lot of people, requiring 3.3 or better is going to include a lot more. It's a tradeoff between usability and cleanliness of code. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
