Sure. The m.addConstr() call returns a constraint object that you can just store in your
own list, like
cons[s,d,t] = m.addConstr((z[s,d,t] == z_m[s,d,t]), 'day_RepairOne')
Then, you can call
for (s,d,t) in Y:
m.remove(cons[s,d,t])
But since Gurobi 7.5 there is actually a much nicer way to do this:
consset = m.addConstrs((z[s,d,t] == z_m[s,d,t] for (s,d,t) in Y if d != d0 and d !=
d1), name='day_RepairOne')
adds all of your constraint with a single Python statement. It returns a dictionary of
Constr objects. This you can plug directly into the remove method:
m.remove(consset)
to get rid of all these constraints. See
http://www.gurobi.com/documentation/7.5/refman/py_model_addconstrs.html and
http://www.gurobi.com/documentation/7.5/refman/py_model_remove.html
Regards,
Tobias