Environment solves with python3.7, breaking wavecal dependency progress bar

[ld-cd]

This syntax was introduced in 3.8, this should possibly be reported up stream or an older version of the package pinned:

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3552, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)

  File "<ipython-input-4-4075bd20be7a>", line 1, in <module>
    o.bad_pixel_mask

  File "/home/cudaa/Workspace/analysis/MKIDPipeline/mkidpipeline/photontable.py", line 368, in bad_pixel_mask
    from mkidpipeline.pipeline import PROBLEM_FLAGS  # This must be here to prevent a circular import!

  File "/home/cudaa/Workspace/analysis/MKIDPipeline/mkidpipeline/pipeline.py", line 17, in <module>
    mod = import_module(f"mkidpipeline.steps.{info.name}")

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)

  File "/home/cudaa/Workspace/analysis/MKIDPipeline/mkidpipeline/steps/flatcal.py", line 10, in <module>
    from mkidpipeline.steps import wavecal

  File "/home/cudaa/Workspace/analysis/MKIDPipeline/mkidpipeline/steps/wavecal.py", line 9, in <module>
    import progressbar as pb

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/site-packages/progressbar/__init__.py", line 5, in <module>
    from .bar import DataTransferBar

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/site-packages/progressbar/bar.py", line 13, in <module>
    from python_utils import types

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/site-packages/python_utils/__init__.py", line 1, in <module>
    from . import (

  File "/home/cudaa/.conda/envs/wheatley/pipeline/lib/python3.7/site-packages/python_utils/converters.py", line 89
    if match := regexp.search(input_):
              ^
SyntaxError: invalid syntax

[baileyji]

I think both Ronald and Nikki ran into this as well when setting up their environments. Maybe the pinning of the relevant package didn't get bushed to the env YAML file you used?

[ld-cd]

This is the yaml environment file on the develop branch, Andrew also hit this but I was asked not to look into it so I haven't found a solid fix