Pete R Jemian

I still believe supporting on the two most recent versions is an aggressive stance for this toolchain. Lots of repositories to update to that standard.

The point raised by @padraic-shafer is new, we must consider the beam line staff as participating developers in this process. By the time new versions become available in the full...

For example, the bluesky user wants to learn what plans are available (such as [`apstools.utils.listplans()`](https://bcda-aps.github.io/apstools/latest/examples/ho_list_control_objects.html#listplans()-function)). This decorator could be used to make that discovery process much easier and [better informed](https://github.com/BCDA-APS/apstools/blob/83206b9fab067f9a80bd4f9fa732b9c0c51d12fa/apstools/utils/list_plans.py#L25-L29)....

`bluesky/utils/__init__.py` is approaching 2,000 lines with dozens of classes and functions at the module level. Does anyone else believe it is time to refactor this file into its component modules?...

Already it is easier to find things. (per #1723)

Here's the minimum [1.3.6](https://github.com/conda-forge/mongoquery-feedstock/pull/8) version needed, waiting on approvals. @tacaswell , @CJ-Wright, @ericdill, @licode - Any of you care to review this 2+ year-old PR?

Passing review not required, just merge by authorized GH user.

How can I release apstools on conda-forge with a non-cf requirement?