Python 3 support

By -
Good news, or-tools now supports python3.

How to get it (from sources only for the time being):
  ubuntu: install python3 python3-dev, python3-setuptools. Change UNIX_PYTHON_VERSION to 3.4 (in 14.04), recompile.
  Mac OS X: Install python (3.5.1?), change UNIX_PYTHON_VERSION to 3.5, tweak manually PYTHON_INC in makefiles/Makefile.unix to reflect the path (/Library/Framework/...) to the python3 install. recompile.
  Windows: Install python 3.5.1 (32 or 64 bit), set the correct path in Makefile.local. recompile.

Hopefully, everything should work. At least, make test_python works for me.

Comments:
  I removed dependencies on google-apputils, and python gflags. OR-Tools now uses argparse.
  Protobuf has been bumped to 3.0.0 beta 1
  Few python examples are ported. They will likely break on print and iterators.
  I will build pypi py3-ortools modules, soon I hope.
  Plenty of internal code was upgraded, especially in the swig layer.

I am sure there are plenty of bugs left, please send me everything that misbehaves.

Comments

Post a Comment

Popular posts from this blog

Linking glpk with or-tools on unix

By -
Following the change on SCIP, here is the new procedure to compile and link GLPK with or-tools This currently applies to unix only: First download the latest glpk archive (4.61 at the time of this post). Untar, cd into the glpk directory on linux:   ./configure --prefix=<install_path> --with-pic   make   make install on mac OS X:   ./configure --prefix=<install_path>   make CFLAGS='--mmacosx-version-min=10.8'   make install   then add:   UNIX_GLPK_DIR=<install_path> in or-tools/Makefile.local recompile or-tools:   make clean   make cc test it:   run bin/integer_programming and bin/linear_programming. Both must display glpk runs. I have no easy solution for glpk on windows currently, still investigating.
Read more

Changing the way we link with SCIP

By -
As of today, I pushed support for scip 4.0.0 on both unix and windows. In the process, I have changed the way to setup or-tools to include scip at compilation time. on Unix:   untar the scipoptsuite> archive somewhere   cd <path to scipoptsuite-4.0.0>   Mac OS X:  make GMP=false READLINE=false TPI=tny   Linux:  make GMP=false READLINE=false TPI=tny USRCFLAGS=-fPIC USRCXXFLAGS=-fPIC USRCPPFLAGS=-fPIC   in or-tools, edit Makefile.local   add:     UNIX_SCIP_DIR=<path to sciptopsuite-4.0.0>/scip-4.0.0   make clean   make cc   to test it, run:      bin/integer_programming   it should display the scip solver run. on windows:   download the compiled library:     http://scip.zib.de/download.php?fname=scip-4.0.0.win.x86_64.vc14.opt.spx2.lib.zip   download the headers:      http://scip.zib.de/download/release/scipoptheaders-4.0.0.tgz   uncompress, untar everything.   create a directory that will contains what is needed   md scip-4.0.0  
Read more

Heads up, upcoming incompatibility in the CP/Routing library

By -
Hello all, I will soon push a large incompatible change in the CP and Routing libraries. The change will replace parameters (CP solver parameters, routing model parameters, routing search parameters) from struct to protobuf. This will also hide the C++ command line flags (cp_trace_search, routing_first_solution, ...) and make them redundant for controlling the behavior of the libraries. They are currently kept in the C++ library, but will be dropped out eventually. With this move, all functionalities offered by the C++ command line flags will be available from all languages (provided you implement the command line parsing part). Let's see an example (tsp) Before (in C++):    // Setting first solution heuristic (cheapest addition).    FLAGS_routing_first_solution = "PathCheapestArc";    const Assignment* solution = routing.Solve() ; After (in C++, using the command line flags compatibility) :    RoutingSearchParameters parameters =  BuildSearchParametersFro
Read more