Adding suggestion from Jaime and napari version Note

[psobolewskiPhD]

Description

I've added the suggestion from Jaime
napari#51 (comment)
And the Note about the version.
I fixed the GitHub action to use the proper version. I'm not sure if the other actions also need changing.

YOu can check the build docs in my fork PR:
psobolewskiPhD#3

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

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.

[Czaki]

I think that it could be done better. We cannot substitute in the code block, but we could substitute the whole code block.

[psobolewskiPhD]

There was a small bug after merging the fix from Czaki where the regular substitution didn't work. I've fixed it. Here's the built docs now:


Can access here:
https://github.com/psobolewskiPhD/napari-docs/actions/runs/3610147414

[Czaki]

Maybe also specify the python version as a variable in conf.py to have same python version everywhere in docs?

[psobolewskiPhD]

Maybe also specify the python version as a variable in conf.py to have same python version everywhere in docs?

Good idea. I won't be able to get to it till at least Tuesday—traveling the next two days.
Also, maybe it's a bit of scope creep—which admittedly even this PR to the original PR is somewhat—and should be it's own PR?

[Czaki]

but in the scope of this PR may be introduced this variable and use, and followup could be to reintroduce it in another place.