kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

On 04/30/2013 02:04 PM, Travis Ayres wrote:
> Also - python 2 or 3?

Great and important question.  We can do either, although some work is needed for 3.4 on
Windows, probably I would be in that critical path for python a-mingw-us.  I have already
commited to doing it.  I guess, 4 days work for me.

wxPython on 3.x moved away from Swig, we don't know if our swig work would still play nice.


I am neutral, having moved from pro ver. 3.x python to neutral over the last 4 years of
dreaming about it.  From my experience, there is a near psychotic fear among python
programmers of version 3.x, or there was at my last measurement of it.  I would be
delighted to be surprised on that evolution.


Travis, if you want to make a case, make it.  I will get out of the way and remain neutral.


Dick




> 
> On Apr 30, 2013 12:00 PM, "Dick Hollenbeck" <dick@xxxxxxxxxxx <mailto:dick@xxxxxxxxxxx>>
> wrote:
> 
>     On 04/29/2013 03:04 AM, Edwin van den Oetelaar wrote:
>     > Just found this paper.
>     > http://swwxguitesting.wefi.net/MPhilThesisChapterSwWxGuiTesting.pdf (about automated gui
>     > testing with wx)
>     > I personally think more gui code should move from C++ to python for easy development and
>     > interactive testing.
>     > Keep it going!!
>     > Greetings,
>     > Edwin van den Oetelaar
> 
> 
>     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.
> 
>     Both are possible, we need names to even talk, to even have a conversation.  There are
>     leadership opportunities here.
> 
>     For non-windows users, this can begin now.  For windows users, probably within days, based
>     on Brian's work.
> 
>     Converting old C++ to python is not on anyone's radar that I am aware of however.
> 
>     Dick
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help   : https://help.launchpad.net/ListHelp
>