Is Python 3.5 supported for example ?

On Windows 7 64-bit system, with MinGW and Python 3.5.2, and Python 3 in path, I try to run the example at http://cocotb.readthedocs.io/en/latest/quickstart.html, but when doing make in MSys terminal, it gives:

$ make
  File "<string>", line 1
    from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
                                                   ^
SyntaxError: invalid syntax
  File "<string>", line 1
    import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
                                              ^
SyntaxError: invalid syntax
  File "<string>", line 1
    from distutils import sysconfig; print sysconfig.get_config_var("DESTSHARED"
)
                                                   ^
SyntaxError: invalid syntax
  File "<string>", line 1
    import distutils.sysconfig; print distutils.sysconfig.get_python_inc()
                                              ^
SyntaxError: invalid syntax
/home/mz/cocotb/makefiles/simulators/Makefile.icarus:49: *** "Unable to locate command >iverilog<".  Stop.

Looks like the scripts does not support Python 3 with print being a function.

Is Python 3.5 supported for example, and what should I then do to use Python 3 ?

Thanks.

[javValverde]

@jeremyherbert I guess appVeyor could be used for continuous integration in Windows.

[jeremyherbert]

Hi @MortenZdk

I certainly use cocotb with python 3.5 on Linux and OS X. The problem here is that the Windows/msys makefile is a bit wonky. You can have a look at the Linux one to see how it should be working.

I can immediately see that these lines can be fixed by something like this:

LOCAL_PYTHON_VERSION?=$(shell $(PYTHON_BIN) -c 'from __future__ import print_function; import distutils.sysconfig; print(distutils.sysconfig.get_python_version())') PYTHON_DYNLIBDIR:=$(shell $(PYTHON_BIN) -c 'from __future__ import print_function; from distutils import sysconfig; print(sysconfig.get_config_var("DESTSHARED"))')

Unfortunately I can’t test this for you because I am not near my computer (I blame any typing errors on my tablet), and I also don’t use Windows for this kind of work 😉 but keep reporting back if you find issues; there is no simple way to do regression testing for Windows using free services like there is for Linux.