Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Steven A. Falco]

On 10/26/19 10:46 AM, Carsten Schoenert wrote:
> Am 26.10.19 um 16:09 schrieb Seth Hillbrand:
>> I've added [1] so that we make sure to get to it before v6 is released.
>> What is the timeline for the new stable Debian/Fedora?  Do we need to
>> accelerate this for 5.1.6?
> 
> The next Debian stable release is planned for autumn 2021. So no rush needed.
> 

Fedora 31 is due out this coming Tuesday (2019-10-29).  It will still have 
python2 available, but the generic "python" command will be linked to python3.  
Scripts would have to be changed to explicitly call python2.

Fedora 32, in about 6 months, will remove python2 for most purposes.  There 
will be a python27 package available for legacy use, but from what I can tell, 
it would have to be installed manually by a user - automatic installation via 
dependencies will not be allowed.

Bottom line - figure 6 months for Fedora before python2 is history.

Steve

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Seth Hillbrand]

On 2019-10-26 10:06, Simon Richter wrote:

Hi Wayne,

On 26.10.19 19:00, Wayne Stambaugh wrote:

 None the less, there is currently no wxPhoenix/Python3 support for 
windows.


TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler
is great as an additional source of diagnostics, and some people might
like the smaller runtime, but in the end we want to be 100% free 
software.


   Simon


I also don't like the idea of introducing MSVC-only code.  But at the 
moment, the pthreads implementation of C++ async code is 1-2 orders of 
magnitude slower under windows than Linux.  We have a number of open 
bugs that directly point back to this.  Using MSVC translates the async 
calls to native threads.


If we have an option to improve the user experience while keep our code 
open and standards-compliant, I hope we'll consider it.


-Seth

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Wayne Stambaugh]

Hi Simon,

On 10/26/19 1:06 PM, Simon Richter wrote:
> Hi Wayne,
> 
> On 26.10.19 19:00, Wayne Stambaugh wrote:
> 
>>  None the less, there is currently no wxPhoenix/Python3 support for windows.
> 
> TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler
> is great as an additional source of diagnostics, and some people might
> like the smaller runtime, but in the end we want to be 100% free software.

I completely agree.  It's just frustrating to have to go back and fix
something that already worked.  Maybe I can find the time to fix it
myself or see if one of the msys2 developers can take a look at it.  I
think they fixed it last time.

Wayne

> 
>Simon
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Simon Richter]

Hi Wayne,

On 26.10.19 19:00, Wayne Stambaugh wrote:

>  None the less, there is currently no wxPhoenix/Python3 support for windows.

TBH, I wouldn't like to be dependent on MSVC on Windows -- the compiler
is great as an additional source of diagnostics, and some people might
like the smaller runtime, but in the end we want to be 100% free software.

   Simon



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Wayne Stambaugh]

From what I can tell, this is going to be an issue.  The wxPhoenix folks
don't seem too keen on supporting mingw builds any more.  The new
wxPhoenix build scripts forcibly change the build environment to msvc
even if you tell python distutils to use mingw.  The last time I
contacted the project they seemed to think that that was our problem
even though they broke the previous wxPython build behavior.  I haven't
tried it in a while but I have been following the project on github and
I have not seen any commits that addressed this issue.  Given the
response I got last time, my motivation is low to fix the issue myself.
 None the less, there is currently no wxPhoenix/Python3 support for windows.

On 10/26/19 12:41 PM, Nick Østergaard wrote:
> For windows, someone newds to show phoenix working in either msys2 or
> msvc. And if we will eventuallty transition to msvc we also need other
> dependencies easily available. I am still hoping for those dependencies
> to become available in vcpkg.
> 
> lør. 26. okt. 2019 17.13 skrev Ian McInerney  >:
> 
> We should also be thinking of when we want to officially drop the
> Python 2 support for KiCad. Since Python 2.7 will be end of life in
> just a few months, it might be worth starting the transition over to
> Python 3 (it looks like Windows and Mac builds ship with 2.7
> currently). 
> 
> -Ian
> 
> On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert
> mailto:c.schoen...@t-online.de>> wrote:
> 
> Hello Wayne,
> 
> Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:
> > I'm guessing that fixing the shebangs will not be enough
> because there
> > is python2 specific code in the script files.
> 
> I think so, I've haven't looked at the Python3 compatibility of the
> underlying code, just grep'd for potential shebang lines.
> Looking at the
> date within the copyright statement let me be quite sure the
> files wont
> be Python3 ready.
> 
> And this is for sure true for mostly all the existing files.
> 
> -- 
> Regards
> Carsten Schoenert
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Nick Østergaard]

For windows, someone newds to show phoenix working in either msys2 or msvc.
And if we will eventuallty transition to msvc we also need other
dependencies easily available. I am still hoping for those dependencies to
become available in vcpkg.

lør. 26. okt. 2019 17.13 skrev Ian McInerney :

> We should also be thinking of when we want to officially drop the Python 2
> support for KiCad. Since Python 2.7 will be end of life in just a few
> months, it might be worth starting the transition over to Python 3 (it
> looks like Windows and Mac builds ship with 2.7 currently).
>
> -Ian
>
> On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert 
> wrote:
>
>> Hello Wayne,
>>
>> Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:
>> > I'm guessing that fixing the shebangs will not be enough because there
>> > is python2 specific code in the script files.
>>
>> I think so, I've haven't looked at the Python3 compatibility of the
>> underlying code, just grep'd for potential shebang lines. Looking at the
>> date within the copyright statement let me be quite sure the files wont
>> be Python3 ready.
>>
>> And this is for sure true for mostly all the existing files.
>>
>> --
>> Regards
>> Carsten Schoenert
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Adam Wolf]

The Mac Kicad  Python 3 transition needed upstream work maybe a year ago.
I have revisiting it on my list.

Adam

On Sat, Oct 26, 2019, 10:13 AM Ian McInerney 
wrote:

> We should also be thinking of when we want to officially drop the Python 2
> support for KiCad. Since Python 2.7 will be end of life in just a few
> months, it might be worth starting the transition over to Python 3 (it
> looks like Windows and Mac builds ship with 2.7 currently).
>
> -Ian
>
> On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert 
> wrote:
>
>> Hello Wayne,
>>
>> Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:
>> > I'm guessing that fixing the shebangs will not be enough because there
>> > is python2 specific code in the script files.
>>
>> I think so, I've haven't looked at the Python3 compatibility of the
>> underlying code, just grep'd for potential shebang lines. Looking at the
>> date within the copyright statement let me be quite sure the files wont
>> be Python3 ready.
>>
>> And this is for sure true for mostly all the existing files.
>>
>> --
>> Regards
>> Carsten Schoenert
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Ian McInerney]

We should also be thinking of when we want to officially drop the Python 2
support for KiCad. Since Python 2.7 will be end of life in just a few
months, it might be worth starting the transition over to Python 3 (it
looks like Windows and Mac builds ship with 2.7 currently).

-Ian

On Sat, Oct 26, 2019 at 3:52 PM Carsten Schoenert 
wrote:

> Hello Wayne,
>
> Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:
> > I'm guessing that fixing the shebangs will not be enough because there
> > is python2 specific code in the script files.
>
> I think so, I've haven't looked at the Python3 compatibility of the
> underlying code, just grep'd for potential shebang lines. Looking at the
> date within the copyright statement let me be quite sure the files wont
> be Python3 ready.
>
> And this is for sure true for mostly all the existing files.
>
> --
> Regards
> Carsten Schoenert
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Carsten Schoenert]

Am 26.10.19 um 16:09 schrieb Seth Hillbrand:

I've added [1] so that we make sure to get to it before v6 is released.
What is the timeline for the new stable Debian/Fedora?  Do we need to
accelerate this for 5.1.6?


The next Debian stable release is planned for autumn 2021. So no rush 
needed.


--
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Seth Hillbrand]

On 2019-10-26 06:53, Wayne Stambaugh wrote:

I'm guessing that fixing the shebangs will not be enough because there
is python2 specific code in the script files.



I've added [1] so that we make sure to get to it before v6 is released.  
What is the timeline for the new stable Debian/Fedora?  Do we need to 
accelerate this for 5.1.6?


-Seth

[1] https://bugs.launchpad.net/kicad/+bug/1849961

Seth Hillbrand
KiCad Services Corporation
https://www.kipro-pcb.com
+1 530 302 5483 | +1 212 603 9372

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Carsten Schoenert]

Hello Wayne,

Am 26.10.19 um 15:53 schrieb Wayne Stambaugh:

I'm guessing that fixing the shebangs will not be enough because there
is python2 specific code in the script files.


I think so, I've haven't looked at the Python3 compatibility of the 
underlying code, just grep'd for potential shebang lines. Looking at the 
date within the copyright statement let me be quite sure the files wont 
be Python3 ready.


And this is for sure true for mostly all the existing files.

--
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Wayne Stambaugh]

I'm guessing that fixing the shebangs will not be enough because there
is python2 specific code in the script files.

On 10/26/19 9:42 AM, Steven A. Falco wrote:
> This will become an issue for Fedora as well.  The command "python" used to 
> mean "python2", but as of Fedora 31 (due to be released this Tuesday, 
> 2019-10-29) the command "python" will mean "python3".
> 
>   Steve
> 
> On 10/25/19 4:35 PM, Carsten Schoenert wrote:
>> Hi,
>>
>> as probably known Debian is planning to get Python2 removed within the
>> next planned stable release.
>>
>> This requires no hard dependencies on Python2 of course in all related
>> packages.
>>
>> The master branch (and of course also the branch 5.1) has still some
>> Python scripts which do have a shebang that is hard wired to the python2
>> binaries.
>>
>>> $ for file in `find -type f -name "*.py"`; do if head -1 $file | grep -e 
>>> python2 -e /python; then echo found in $file; fi ;done
>>> #!/usr/bin/env python2.7
>>> found in ./pcbnew/python/examples/createFPC40.py
>>> #!/usr/bin/env python2
>>> found in ./scripts/ddr3_length_match.py
>>> #!/usr/bin/python
>>> found in ./scripts/test_plugin.py
>>> #!/usr/bin/python
>>> found in ./scripts/lib_convert.py
>>> #!/usr/bin/python
>>> found in ./scripts/test_kicad_plugin.py
>>
>> Any plans to convert these files to at least a shebang of
>> '#!/usr/bin/env python' and a compatibility so the scripts can also be
>> used within a Python3 interpreter?
>>
>> KiCad still has some other (indirect) dependencies on Python2 which will
>> also needed to get resolved, but that's another story.
>>
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python files still depending on Python2 only due used shebang

[Steven A. Falco]

This will become an issue for Fedora as well.  The command "python" used to 
mean "python2", but as of Fedora 31 (due to be released this Tuesday, 
2019-10-29) the command "python" will mean "python3".

Steve

On 10/25/19 4:35 PM, Carsten Schoenert wrote:
> Hi,
> 
> as probably known Debian is planning to get Python2 removed within the
> next planned stable release.
> 
> This requires no hard dependencies on Python2 of course in all related
> packages.
> 
> The master branch (and of course also the branch 5.1) has still some
> Python scripts which do have a shebang that is hard wired to the python2
> binaries.
> 
>> $ for file in `find -type f -name "*.py"`; do if head -1 $file | grep -e 
>> python2 -e /python; then echo found in $file; fi ;done
>> #!/usr/bin/env python2.7
>> found in ./pcbnew/python/examples/createFPC40.py
>> #!/usr/bin/env python2
>> found in ./scripts/ddr3_length_match.py
>> #!/usr/bin/python
>> found in ./scripts/test_plugin.py
>> #!/usr/bin/python
>> found in ./scripts/lib_convert.py
>> #!/usr/bin/python
>> found in ./scripts/test_kicad_plugin.py
> 
> Any plans to convert these files to at least a shebang of
> '#!/usr/bin/env python' and a compatibility so the scripts can also be
> used within a Python3 interpreter?
> 
> KiCad still has some other (indirect) dependencies on Python2 which will
> also needed to get resolved, but that's another story.
> 




signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Python files still depending on Python2 only due used shebang

[Carsten Schoenert]

Hi,

as probably known Debian is planning to get Python2 removed within the
next planned stable release.

This requires no hard dependencies on Python2 of course in all related
packages.

The master branch (and of course also the branch 5.1) has still some
Python scripts which do have a shebang that is hard wired to the python2
binaries.

> $ for file in `find -type f -name "*.py"`; do if head -1 $file | grep -e 
> python2 -e /python; then echo found in $file; fi ;done
> #!/usr/bin/env python2.7
> found in ./pcbnew/python/examples/createFPC40.py
> #!/usr/bin/env python2
> found in ./scripts/ddr3_length_match.py
> #!/usr/bin/python
> found in ./scripts/test_plugin.py
> #!/usr/bin/python
> found in ./scripts/lib_convert.py
> #!/usr/bin/python
> found in ./scripts/test_kicad_plugin.py

Any plans to convert these files to at least a shebang of
'#!/usr/bin/env python' and a compatibility so the scripts can also be
used within a Python3 interpreter?

KiCad still has some other (indirect) dependencies on Python2 which will
also needed to get resolved, but that's another story.

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp