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
I've been building for Fedora using both KICAD_SCRIPTING_PYTHON3=ON and
KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON for quite a while now, FWIW.
I did a few basic tests of scripting and didn't see any problems.
Steve
On 10/26/19 1:03 PM, Simon Richter wrote:
> Hi,
>
> On 26.10.19 18:55, Simon
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,
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
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
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
Python 2 is deprecated upstream, and most distributions are switching
to Python 3 as default, and ship wxPython Phoenix as the wxWidgets
binding for Python 3.
---
CMakeLists.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index
Hi,
On 26.10.19 18:55, Simon Richter wrote:
> Python 2 is deprecated upstream, and most distributions are switching
> to Python 3 as default, and ship wxPython Phoenix as the wxWidgets
> binding for Python 3.
This is mainly to get the ball rolling -- before this can be applied on
master I'm
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
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
Hi Holger,
This depends on the platform. Some platforms may have not updated to
ngspice-31 (mostly legacy Linux distros) so this may not always be the
case. I thought the latest version of ngspice was 32-1. Do we not want
to use that in cases where we control the packaging?
Cheers,
Wayne
On
On 2019-10-25 17:57, Zficani Zficani wrote:
> Hi,
> I'm sorry for the delay but I finally got everything sorted out. I formatted
> the code and fixed a few bugs I found.
> Regarding `git format-patch`, I used it originally but my commits contain
> many TODOs and temporary code so I was told
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,
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.
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
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
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
ngspice-31 for this release?
All my tests have been o.k.
Holger
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help :
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
19 matches
Mail list logo
