migrate to >=py311 enum.StrEnum usage

[bjlittle]

🚀 Pull Request

Description

After adopting Scientific Python SPEC-0 and dropping support of py310, we're now free to adopt enum.StrEnum and enum.auto and thus purge some tech debt.

---

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.28%. Comparing base (9ca4121) to head (4bf1317).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1144      +/-   ##
==========================================
- Coverage   91.29%   91.28%   -0.01%     
==========================================
  Files          58       58              
  Lines        2941     2939       -2     
==========================================
- Hits         2685     2683       -2     
  Misses        256      256              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[trexfeathers]

Are you sure about auto()? With explicit strings we still get the built-in validation and documentation of Enum, while allowing users to type strings in their own code, which I imagine would be easier.

[bjlittle]

@trexfeathers Users can still type strings as before, so there's no difference in user experience or behaviour.

When auto() is used for a StrEnum it's giving us the lower case string value of the enumeration name for free ... the only difference is in the rendered documentation where the value of an enumeration isn't shown i.e., this ...

vs this ...

TBH on reflection I prefer the former, so if you wanted to push a PR dropping the use of auto for the explicit lower case literal, that would be welcomed 😉

[trexfeathers]

Ohhhh now I can't decide 😖

it's giving us the lower case string value of the enumeration name for free

That's good!

the rendered documentation where the value of an enumeration isn't shown

That's bad!

TBH on reflection I prefer the former

Let me know if you're just being nice. If you really want it I will write it!

[bjlittle]

@trexfeathers Let's go with reverting the use to auto and replace with lower-case literals. This should improve the documentation, if you're still game for that?

[trexfeathers]

#1152