Re: [Kicad-developers] Python 3 now required

2021-06-18 Thread crash
Could this work? conda create --name py2 python=2.7 -Original Message- From: Kicad-developers On Behalf Of Marco Ciampa Sent: Tuesday, June 15, 2021 6:32 AM To: kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] Python 3 now required On Tue, Jun 15, 2021 at 12:22:42AM

Re: [Kicad-developers] Python 3 now required

2021-06-16 Thread Jon Evans
The option KICAD_SCRIPTING_PYTHON3 doesn't even exist anymore. I recommend that people who are having issues get rid of your CMake cache and start fresh, you have a lot of left over variables that may be confusing things. When we remove a variable from our CMake configuration, many times it does

Re: [Kicad-developers] Python 3 now required

2021-06-16 Thread Nick Østergaard
You don't need to specify the type, but cmake will accept it as well and that is how it is written by cmake in the CMakeCache.txt. On Wed, 16 Jun 2021 at 20:51, Kevin Cozens wrote: > On 2021-06-15 6:32 a.m., Marco Ciampa wrote: > > On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote:

Re: [Kicad-developers] Python 3 now required

2021-06-16 Thread Kevin Cozens
On 2021-06-15 6:32 a.m., Marco Ciampa wrote: On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote: [snip] That's where cmake UIs come handy. Try ccmake or cmake-gui (they are [snip] Exactly, Kevin is right but using the cmake-gui command it was very easy to figure out how to

Re: [Kicad-developers] Python 3 now required

2021-06-15 Thread Marco Ciampa
On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote: > On Mon, Jun 14, 2021 at 11:59 PM Kevin Cozens wrote: > > Not that simple. I tried passing -DPYTHON_EXECUTABLE=python3 and it still > > only finds 2.7. I tried it without the -D part. I have also tried it with > > and without a full

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Wayne Stambaugh
On 6/14/21 4:59 PM, Kevin Cozens wrote: On 2021-06-14 4:34 p.m., Marco Ciampa wrote: On Mon, Jun 14, 2021 at 03:43:54PM -0400, Jon Evans wrote: You should be able to override what is found by CMake by defining the PYTHON_EXECUTABLE variable in your cmake command line Gosh, shame on me, it

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Eeli Kaikkonen
On Mon, Jun 14, 2021 at 11:59 PM Kevin Cozens wrote: > Not that simple. I tried passing -DPYTHON_EXECUTABLE=python3 and it still > only finds 2.7. I tried it without the -D part. I have also tried it with > and without a full path to python3. I even tried putting PYTHON_EXECUTABLE > before

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Jon Evans
I made this change[1] to try to fix the Ubuntu python3 situation Does this not work for you if you start from a clean directory (get rid of CMake cache)? [1] https://gitlab.com/kicad/code/kicad/-/commit/b345d979543d3f42add7e563e9881448b15d01bf On Mon, Jun 14, 2021 at 5:00 PM Kevin Cozens

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Kevin Cozens
On 2021-06-14 4:34 p.m., Marco Ciampa wrote: On Mon, Jun 14, 2021 at 03:43:54PM -0400, Jon Evans wrote: You should be able to override what is found by CMake by defining the PYTHON_EXECUTABLE variable in your cmake command line Gosh, shame on me, it was so simple! Not that simple. I tried

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Marco Ciampa
On Mon, Jun 14, 2021 at 03:43:54PM -0400, Jon Evans wrote: > You should be able to override what is found by CMake by defining the > PYTHON_EXECUTABLE variable in your cmake command line Gosh, shame on me, it was so simple! It worked thanks! -- Saluton, Marco Ciampa

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Jon Evans
You should be able to override what is found by CMake by defining the PYTHON_EXECUTABLE variable in your cmake command line -Jon On Mon, Jun 14, 2021 at 3:41 PM Marco Ciampa wrote: > > On Fri, Jun 04, 2021 at 02:50:37PM -0400, Kevin Cozens wrote: > > On 2021-06-04 1:34 p.m., Seth Hillbrand

Re: [Kicad-developers] Python 3 now required

2021-06-14 Thread Marco Ciampa
On Fri, Jun 04, 2021 at 02:50:37PM -0400, Kevin Cozens wrote: > On 2021-06-04 1:34 p.m., Seth Hillbrand wrote: > > KiCad now officially only supports Python 3. > [snip] > > The current minimum Python version is 3.7 (due to a module test call we > > use) but we are looking at potentially supporting

Re: [Kicad-developers] Python 3 now required

2021-06-04 Thread Kevin Cozens
On 2021-06-04 1:34 p.m., Seth Hillbrand wrote: KiCad now officially only supports Python 3. [snip] The current minimum Python version is 3.7 (due to a module test call we use) but we are looking at potentially supporting Python 3.6 if we can handle dynamic reloads. I have 2.7 and 3.6

Re: [Kicad-developers] Python 3 now required

2021-06-04 Thread Christoph Moench-Tegeder
## Steven A. Falco (stevenfa...@gmail.com): > I have a related qestion regarding "shebangs" in python code. In a > few files we have #!/usr/bin/env python3, which is great, because it > fully specifies which interpreter to use. There's no real guarantee that "python3" exists (nor "python" as

Re: [Kicad-developers] Python 3 now required

2021-06-04 Thread Steven A. Falco
I have a related qestion regarding "shebangs" in python code. In a few files we have #!/usr/bin/env python3, which is great, because it fully specifies which interpreter to use. For example tools/create_dark_theme.py has this. In other files, the python version is not specified, and we just

Re: [Kicad-developers] Python 3 now required

2021-06-04 Thread Eeli Kaikkonen
Great work, thanks! It's also a big relief that plugin developers don't need to try to support 2 and 3. On Fri, Jun 4, 2021 at 8:36 PM Seth Hillbrand wrote: > > The current minimum Python version is 3.7 (due to a module test call we > use) but we are looking at potentially supporting Python 3.6

[Kicad-developers] Python 3 now required

2021-06-04 Thread Seth Hillbrand
Hi Folks- KiCad now officially only supports Python 3. Note that this comes a full year and 6 months after Python 2 was deprecated (https://pythonclock.org/) and most, if not all, of our supporting packages have pledged to stop supporting Python 2 (https://python3statement.org/) We are now