:P
On 29 June 2014 16:56, Christopher Crouzet <christopher.crou...@gmail.com> wrote: > In the lack of answer, I guess we shouldn't count too much on the future > of the API 2.0 :) > > > > On 25 June 2014 11:33, Sebastien Sterling <sebastien.sterl...@gmail.com> > wrote: > >> A brave initiative Christopher, and thank you for laying it out plain for >> the less techsavvy, >> >> >> "why are you using the maya python API 1.0 instead of 2.0 ?" >> >> Why is Python API 2.0 not finished yet Luc Eric ? >> >> >> On 24 June 2014 17:31, Christopher Crouzet <christopher.crou...@gmail.com >> > wrote: >> >>> When I initially patched the Maya Python API, it was with Maya 2010 and >>> there was no API 2.0 back then. As of today, I didn't really think about my >>> choice, I simply wanted to share the technique. >>> >>> That said, and remembering the state of the API 2.0, it could indeed >>> have been the subject of the article/library but then I'm not sure if >>> patching a yet unfinished API would be the wisest choice since it will have >>> its gaps officially filled in over the releases, right? >>> >>> >>> >>> On 24 June 2014 12:12, Luc-Eric Rousseau <luceri...@gmail.com> wrote: >>> >>>> why are you using the maya python API 1.0 instead of 2.0 ? >>>> >>> >>> >>> >>> -- >>> Christopher Crouzet >>> *http://christophercrouzet.com* <http://christophercrouzet.com> >>> >>> >> > > > -- > Christopher Crouzet > *http://christophercrouzet.com* <http://christophercrouzet.com> > >
