On Mon, Jun 13, 2016 at 1:18 AM, Erik Bray <erik.m.b...@gmail.com> wrote:
> On Sat, Jun 11, 2016 at 4:28 PM, William Stein <wst...@gmail.com> wrote: > > > > > > On Saturday, June 11, 2016, Volker Braun <vbraun.n...@gmail.com> wrote: > >> > >> Note that we can trivially support Python 2.6 just by vendoring > >> argparse.py. Make user's lives easier or save a few kilobytes of disk > space? > >> How is this not a total slam-dunk?-- > > > > > > Huge +1 > > +1 here too. You folks obviously decide what's best for sage, but as a minor comment on this point, from our experience on IPython: it's a fair bit harder to make the transition to a python 2/3 compatible codebase while supporting 2.6 than if you only support 2.7. Lots of things from 3 were backported to 2.7 to minimize the gap between the two, but that wasn't the case with 2.6. It may be the right tradeoff for Sage, obviously, but at least you should be aware that keeping 2.6 is in a sense a vote for not moving in the direction of 3.x. Cheers -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
