FIX: Avoid use of bare except

[larsoner]

Follow-up to #9129. This PR:

1. Removes E722 from the list of ignores in tox.ini.
2. Replaces some instances of except: in tests with cleaner pytest.raises calls
3. Replaces as many except:s in our code with except Exception: that seemed reasonable. In a few places there was an except: ...; raise pattern to close some other object, to which I added # noqa: E722. This works for pydocstyle and flake8-style checkers, can't remember what SciPy uses for style checking so I'll wait to see what the CIs say about it.

[pv]

It raises

[larsoner]

Tests pass on my machine and CIs (except for an unrelated error). Do I need to run some special testing mode?

[ev-br]

For the failed example, can you replace >>> print(res.x) by >>> res.x, and copy-paste the output?

It's just that the doctest checker does not understand the way numpy arrays are printed. Not sure why the error surfaces with this PR though.

[pv]

Ok, please disregard, I apparently misremember...

[larsoner]

@ev-br I made a commit to try what you asked and this was the output:

File "doc/source/tutorial/optimize.rst", line 699, in /home/travis/build/scipy/scipy/tools/../doc/source/tutorial/optimize.rst
Failed example:
    res.x
Expected:
    np.array([0.41494418 0.17011164])
Got:
    array([0.41494475, 0.1701105 ])

I'm just going to put a # may vary in there for now

[ev-br]

https://github.com/scipy/scipy/compare/master...ev-br:doctest_tutorial?expand=1 should fix it, I think.

[larsoner]

I thought I tried a variant of this and it didn't work, but I'll open a PR to master for this. It's happening in other PRs, now, too, so I think mine was somehow just unfortunately timed to make it seem like it was due to my changes. So I'm going to revert the ones here and hopefully we can merge.

[mikofski]

@ev-br and @larsoner I think the failure is due to #9131 which changed one of the input arguments, so the expected output changes also, it should be: array([0.41494475, 0.1701105 ]) if you remove print()

[larsoner]

@mikofski can you push to #9138 or open a PR to fix it? I've reverted the changes here so we can address it separately.

[ilayn]

I've just placed a PR

[larsoner]

All green now that master is also green and I restarted the build.

Ready for review/merge from my end

[ilayn]

Looks good to me.

[rgommers]

LGTM too and all green, merging.