This PR does a few things relating to script handling.
Consolidates all of our notes on what scripts are useful or not into the Sphinx documentation...still rough but at least in one place.
Sorts scripts into "scripts" that are likely to be more commonly used, "examples" that are less maintained but might be useful for reference/mission-specific, and some which are deleted. (Relevant to #5).
Takes all scripts which use optparse and ports them to argparse (Relevant to #60 -- it will be much easier to add support for other databases to the scripts if all scripts are using a common argument parsing code, and getting them using the same parsing mechanism is a first step.)
Some more clarity on the last part is probably in order. optparse was introduced in 2.3 or so and deprecated in 2.7, when argparse was introduced. That forced us to stay with optparse for as long as we wanted 2.6 support, even though we knew it was going away. So earlier scripts were written with optparse and often newer ones with argparse. Now that 2.6 is well in the rearview mirror, getting everything on argparse prepares us for the future.
There are a few scripts that directly parse sys.argv; they aren't changed for now.
Functionality shouldn't be changed; I did some chunk checks on every script (sometimes just primarily checking that the parsing worked) but we don't have deep testing on the scripts right now.
PR Checklist
[X] Pull request has descriptive title
[X] Pull request gives overview of changes
[X] New code has inline comments where necessary
[X] (N/A) Any new modules, functions or classes have docstrings consistent with dbprocessing style
[X] (N/A) Major new functionality has appropriate Sphinx documentation
[X] (N/A) Added an entry to release notes if fixing a major bug or providing a major new feature
[X] (N/A) New features and bug fixes should have unit tests
[X] Relevant issues are linked in the description (use Closes # if this PR closes the issue, or some other reference, such as See # if it is related in some other way)
This PR does a few things relating to script handling.
Some more clarity on the last part is probably in order. optparse was introduced in 2.3 or so and deprecated in 2.7, when argparse was introduced. That forced us to stay with optparse for as long as we wanted 2.6 support, even though we knew it was going away. So earlier scripts were written with optparse and often newer ones with argparse. Now that 2.6 is well in the rearview mirror, getting everything on argparse prepares us for the future.
There are a few scripts that directly parse sys.argv; they aren't changed for now.
Functionality shouldn't be changed; I did some chunk checks on every script (sometimes just primarily checking that the parsing worked) but we don't have deep testing on the scripts right now.
PR Checklist
Closes #if this PR closes the issue, or some other reference, such asSee #if it is related in some other way)