Summary

The Gurobi interactive shell (gurobi.sh / gurobi.bat) is being deprecated. In the next major release these scripts will emit a deprecation warning, and in a future release they will be removed entirely from the Gurobi installers. I'm opening this issue to discuss if any changes are needed to avoid breaking pyomo for users of the file-based interface.

Description

There is some nice work already done so that the file-based interface would invoke the current python executable if it has gurobipy installed:

• Support gurobi lp interface through gurobipy module #2262
• Default Gurobi interface may not work depending on how Gurobi was installed #2132
• Fall back to direct interface if shell is not available #1776

There would still be a few changes to consider:

1. Update installation instructions to clarify that a gurobipy installation is needed and the full Gurobi package does not need to be installed
2. Consider changing the default behaviour to use a gurobipy installation in the current interpreter, or the direct interface
3. I suppose PyPy users rely more on the Gurobi shell since gurobipy doesn't support PyPy. Is another option needed there?

Just wanted to bring this up early in case it creates compatibility issues. I'm happy to work on any necessary changes.