On Sat, Feb 15, 2014 at 2:09 PM, Gary Oberbrunner <ga...@oberbrunner.com> wrote: > > > > On Sat, Feb 15, 2014 at 5:36 AM, Dirk Bächle <tshor...@gmx.de> wrote: >> >> Hi Russel, >> >> >> On 15.02.2014 08:40, Russel Winder wrote: >>> >>> On Thu, 2014-02-13 at 16:20 -0500, Gary Oberbrunner wrote: >>>> >>>> Thanks to Manuel Naranjo, our application is now in. Please go to >>>> http://www.scons.org/wiki/GSoC2014Ideas (which is just a clone of the >>>> 2013 >>>> ideas page so far) and add/edit/cleanup. >>> >>> I had a quick look at the 2 → 3 one and started making changes, but >>> cancelled when I realized the final goal seems to be to create a pre >>> 2to3 script so that the combination of the two create a SCons codebase >>> transform. >>> >>> I don't agree with this, I think we should be looking to create a single >>> codebase that runs with Python 2 or Python 3. >>> >>> Once I realized this I backed out of my changes to leave things as they >>> were. >>> >>> >> please just continue editing the page and set the proper goals for this >> task. I wrote this text for GSoC 2013, back when our py3 branch didn't >> exist. So it's not really up-to-date anymore... > > > Agreed -- the task should be single 2&3 codebase, as we've discussed on the > mailing list.
I just want to warn that supporting Python 2/3 is a can of worms and if we lose control over them, we may lose more than gain. In https://pypi.python.org/pypi/hexdump from 7 released versions, at least 2 were released because of non-trivial Python 3 issues, and hexdump is just 10kB with tests. -- anatoly t. _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
