Julian Hall

Great, it's easy for me to add a method to the C++ API to take a model in this form, and then create the Python binding that you'll need. It's...

> Actually example 3 here: https://ergo-code.github.io/HiGHS/dev/interfaces/python/example-py/ shows `addCols` and `addRows` might be exactly what we want? I don't see any documentation of the integral variable support in the python interface...

The value in the interface [I plan to add to HiGHS](https://github.com/ERGO-Code/HiGHS/issues/1955) is that the expense of passing the model via calls to `addCols` and `addRows` in Python is avoided. Less...

Great! I'll leave the creation of a EQ-UB CSR LP/MIP interface to HiGHS for now, but do let me know if there's a meaningful overhead of passing models row-by-row to...

> Consider this change: > > ```python > highspy.IisStrategy.kIisStrategyFromLpColPriority > highspy.HighsIisStrategy.kFromLpColPriority) > ``` > > Here the `IisStrategy` bit is duplicated (for no real discernable reason AFAIK), while `IisStrategy` without...

>> Why can SciPy not exploit the fact that highspy is now in PyPI, and avoid any SciPy-specific build requirements? > This is likely not going to work, mostly because...

>> Note that we are considering removing the HiGHS meson build altogether, as it appears to be more trouble than it was ever worth. > I'm not sure I agree...

> > Why can SciPy not exploit the fact that `highspy` is now in PyPI, and avoid any SciPy-specific build requirements? > > This really is not an option, and...

> @mdhaber surely you didn't mean a hard dependency? Perhaps this was a misunderstanding, or you had something else in mind? No, @mdhaber didn't mean a hard dependency, but there...

> > These are all compiler warnings. In this PR anything outside `highs_bindings` and the `meson.build` is purely for the warnings. > > Why not split these off as separate...