DOC+MAINT: optimize: lb and ub in the Bounds constructor are not optional

[WarrenWeckesser]

Also fix a really long line.

[mdhaber]

Do you want to add a test comparing the repr against the expected string?

[WarrenWeckesser]

The repr can change over time (e.g. it changed when lb and ub were passed through np.asarray before being saved as attributes), so I don't know if an exact match of the repr to a string is what we want. How about evaling the repr and checking that we get back what we put in? Something like

b = Bounds([1, 2], 100)
s = repr(b)
b2 = eval(s)
assert_array_equal(b.lb, b2.lb)
assert_array_equal(b.ub, b2.ub)
assert_array_equal(b.keep_feasible, b2.keep_feasible)

(and another with an explicit keep_feasible argument).

[mdhaber]

Sure. Sounds good.

[WarrenWeckesser]

That was easy... it turns out the tests are already there:

scipy/scipy/optimize/tests/test_constraints.py

Line 171 in ac23f85

def test_bounds_repr():

[mdhaber]

OK I'll merge when the last test finishes.

[mdhaber]

I don't know if the last test is going to finish.

[WarrenWeckesser]

I restarted the stalled job. They're all green now.