On 04/30/2013 07:06 PM, Travis Ayres wrote: > We could entirely avoid the python 2/3 question by implementing and sticking > with C++, and > if we arent going to get satisfactory speed it would forever doom the tool to > toy status
click, delete. > > On Apr 30, 2013 12:50 PM, "Lorenzo Marcantonio" <[email protected] > <mailto:[email protected]>> wrote: > > On Tue, Apr 30, 2013 at 02:00:16PM -0500, Dick Hollenbeck wrote: > > I agree with you, to the extent that having some new code in wxPthon is > likely to > > accelerate the evolution of KiCad to near epic speed. Simply > categorizing, organizing, > > and gathering, will be an extreme challenge. Even some terminology > must be agreed > upon so > > that we can talk about it. Types of scripts: python on C++, or python > under C++ UI, > etc. > > Slow stuff under C++ :D > > Really, I'm not satisfied with python speed *expecially* for wxPython > > Also the C++ bindings are all but robust, at the moment. > > -- > Lorenzo Marcantonio > Logos Srl > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
