I would like to jump in and agree with Roland on this. As someone who has a book and a major training series in the works, having a firm idea of what the version number will be is very important. For most users it will not make a difference in the end, but for those of us that are producing training materials it can have a huge impact on marketing.
Jonathan Williamson http://www.montagestudio.org On Fri, Apr 9, 2010 at 11:17 AM, Martin Poirier <the...@yahoo.com> wrote: > That would be Python 3.1, Blender 2.5x can't build with Python 3.0 (the > CPython API changed). > > Martin > > --- On Fri, 4/9/10, Mike Pan <mike.c....@gmail.com> wrote: > > > From: Mike Pan <mike.c....@gmail.com> > > Subject: Re: [Bf-committers] version naming > > To: "bf-blender developers" <bf-committers@blender.org> > > Received: Friday, April 9, 2010, 9:23 AM > > Blender 3 would also coincide with > > the new Python version that it's using... > > Just saying... > > > > -mike > > _______________________________________________ > > Bf-committers mailing list > > Bf-committers@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers > > > > > __________________________________________________________________ > Get a sneak peak at messages with a handy reading pane with All new Yahoo! > Mail: http://ca.promos.yahoo.com/newmail/overview2/ > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers