constraint_solver: Fix python 3.13 build
This commit is contained in:
@@ -1,18 +1,18 @@
|
||||
# Overview
|
||||
|
||||
You can find here, the documentation for the two following Or-Tools components.
|
||||
You can find here the documentation for the two following OR-Tools components.
|
||||
|
||||
* [CP Solver](CP.md)
|
||||
* [CP Solver](CP.md)
|
||||
|
||||
Constraint programming (CP), is the name given to identifying feasible
|
||||
solutions out of a very large set of candidates, where the problem can be
|
||||
modeled in terms of arbitrary constraints.
|
||||
Constraint programming (CP) is the name given to identifying feasible
|
||||
solutions out of a very large set of candidates, where the problem can be
|
||||
modeled in terms of arbitrary constraints.
|
||||
|
||||
**note:** We **strongly recommend** using the [CP-SAT solver](../../sat)
|
||||
rather than the original CP solver.
|
||||
**note:** We **strongly recommend** using the [CP-SAT solver](../../sat)
|
||||
rather than the original CP solver.
|
||||
|
||||
* [Routing Solver](ROUTING.md)
|
||||
* [Routing Solver](ROUTING.md)
|
||||
|
||||
A specialized library for identifying best vehicle routes given constraints.
|
||||
A specialized library for identifying best vehicle routes given constraints.
|
||||
|
||||
This library extensiond is implemented on top of the CP Solver library.
|
||||
This library extension is implemented on top of the CP Solver library.
|
||||
|
||||
@@ -140,7 +140,7 @@ static void PyFunctionSolverToVoid(PyObject* pyfunc,
|
||||
PyObject* const pysolver =
|
||||
SWIG_NewPointerObj(s, SWIGTYPE_p_operations_research__Solver,
|
||||
SWIG_POINTER_EXCEPTION);
|
||||
PyObject* const pyresult = PyEval_CallFunction(pyfunc, "(O)", pysolver);
|
||||
PyObject* const pyresult = PyObject_CallFunction(pyfunc, "(O)", pysolver);
|
||||
if (!pyresult) {
|
||||
PyErr_SetString(PyExc_RuntimeError,
|
||||
"std::function<void(Solver*)> invocation failed.");
|
||||
|
||||
Reference in New Issue
Block a user