-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use RoutingModel routing status flags anymore #4553
Comments
Indeed, all RoutingModel enums have been removed in favor of the protobuf enums. This removed duplication. so the enum is available as routing_enums_pb2.RoutingSearchStatus.ROUTING_SUCCESS We will update the release notes |
FYI or-tools/ortools/constraint_solver/routing.h Lines 1440 to 1441 in b8e881f
or-tools/ortools/constraint_solver/routing_enums.proto Lines 149 to 171 in b8e881f
Still remain or-tools/ortools/constraint_solver/routing.h Lines 254 to 264 in b8e881f
|
What version of OR-Tools and what language are you using?
9.12.4544
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
Windows 11
What did you do?
Steps to reproduce the behavior:
With version 9.12.4544: Attempt to access ortools.constraint_solver.pywrapcp.RoutingModel.ROUTING_SUCCESS or any other flag
What did you expect to see
With version 9.11.4210: Getting the routing status
What did you see instead?
With version 9.12.4544: AttributeError: type object 'RoutingModel' has no attribute 'ROUTING_SUCCESS'
I was not able to identify the reason and nature of this change, what is the new expected process to access the routing status in the new version?
The text was updated successfully, but these errors were encountered: