Fix min req

[Czaki]

Description

I do not like this solution, but the proper solution may take a long time so it may be treated as a temporal workaround...

Type of change

• Bug-fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

References

How has this been tested?

• example: the test suite for my feature covers cases x, y, and z
• example: all tests pass with my change
• example: I check if my changes works with both PySide and PyQt backends
  as there are small differences between the two Qt bindings.

Final checklist:

• My PR is the minimum possible work for the desired functionality
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• If I included new strings, I have used trans. to make them localizable.
  For more information see our translations guide.

[codecov]

Codecov Report

Merging #5560 (9ada0ba) into main (ada343a) will increase coverage by 1.51%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #5560      +/-   ##
==========================================
+ Coverage   87.87%   89.38%   +1.51%     
==========================================
  Files         608      608              
  Lines       51079    51099      +20     
==========================================
+ Hits        44885    45675     +790     
+ Misses       6194     5424     -770     

Impacted Files	Coverage Δ
napari/_qt/_tests/test_qt_viewer.py	94.61% <100.00%> (+0.01%)	⬆️
napari/utils/config.py	100.00% <0.00%> (ø)
napari/layers/utils/string_encoding.py	100.00% <0.00%> (ø)
napari/components/experimental/monitor/_api.py	0.00% <0.00%> (ø)
napari/utils/_tests/test_key_bindings.py	96.96% <0.00%> (+0.01%)	⬆️
napari/layers/utils/color_encoding.py	96.20% <0.00%> (+0.04%)	⬆️
napari/_tests/utils.py	97.80% <0.00%> (+0.04%)	⬆️
napari/layers/utils/style_encoding.py	96.22% <0.00%> (+0.07%)	⬆️
napari/layers/shapes/_tests/test_shapes_utils.py	97.22% <0.00%> (+0.07%)	⬆️
napari/_app_model/constants/_menus.py	95.45% <0.00%> (+0.21%)	⬆️
... and 52 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[psobolewskiPhD]

BTW, not this PR necessarily, but do we really need this as a napari requirement with the split repo?
I think we should make [docs] for the docs repo installation.

[Czaki]

BTW, not this PR necessarily, but do we really need this as a napari requirement with the split repo?
I think we should make [docs] for the docs repo installation.

No, we could use a constraints file for that. In the next 2-3 days, I may have time to do that.

[jni]

This is not a docs requirement. Rather, we use numpydocs to move some docstrings around. Run git grep numpydoc to find where it's used. It might be something we can eventually deprecate.

[brisvag]

What is it that you don't like exactly here?

[Czaki]

What is it that you don't like exactly here?

list of indirect napari dependencies that may change on the next dependency release (become obsolete for example).

[jni]

Thanks @Czaki!

As a note: @Czaki and I just had a call where he proposed a way to run the MINREQ tests as using a tox plugin — much more elegant! But this is a good fix in the meantime.