-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added info for conda installation problems #51
Conversation
Further down, at line 143 |
If you state the current version one has to update the doc every time. Or can we add a prompt with the current version tag? |
Yeah, I posted about that above, but it's resolved now: #51 (comment) |
@ch-n You want to take a stab at versioning the version number, per @melissawm :
|
Yes will take a look. |
Co-authored-by: Peter Sobolewski <76622105+psobolewskiPhD@users.noreply.github.com>
Co-authored-by: Peter Sobolewski <76622105+psobolewskiPhD@users.noreply.github.com>
Guess I just don't find it but the best solution I could come up is to us the link to the latest version. This is stable and dynamic but will not display the correct version tag. @melissawm @psobolewskiPhD |
Hmm, I tried the myst_substitution provided by @melissawm |
this version problem is a well-known problem of |
Does that mean it's just messed up in PR builds, or does it mean it will be messed up if released? |
Indeed - code blocks are supposed to not be interpreted by the parser so that makes sense. |
That would leave us with the link to the latest version I guess. |
@ch-n I made a PR to your fork with some suggestions. You can see the built docs in my fork PR: |
I have added in Chris-N-K#1 (review) the solution to provide napari version |
Co-authored-by: Grzegorz Bokota <bokota+github@gmail.com>
Adding suggestion from Jaime and napari version Note
All merged now, guess it should be ready for a final review. |
@Chris-N-K @Czaki I made a PR adding python_version to the substitutions: I also fixed the listing of supported python versions from 3.7 ... to 3.8 ... because we don't support 3.7 anymore. For me this is not a blocker, so I leave it up to @Czaki and @jaimergp for the final approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one nit. Can be merged afterwards!
Co-authored-by: Jaime Rodríguez-Guerra <jaimergp@users.noreply.github.com>
Merged it and fixed a conflict with main. |
This is unrelated but I noticed that the font (face and size) is different in the numbered list. Is that intentional or a CSS bug? |
I resolved the conflict if we want the python version set programmatically as suggested by @Czaki Chris-N-K#2 |
I believe this is the current napari-sphinx-theme formatting/design choice. cc @codemonkey800 ? |
@Czaki @Chris-N-K Did y'all have any input on the python version substitution: |
I think the current solution is absolutely reasonable. There might be a slight lag when a new version is unrolled and the docs repo might not have the newest version for a short amount of time, but that should be no real problem. Merry Christmas ;) |
This is awesome, thanks folks! Merging now 🎉 |
…ubstitution (#99) # Description See napari/napari#5509 (comment) The docs live on napari.org don't match PR action downloaded docs when doing napari version substitution (#51) This PR updates the deploy action with `fetch-depth: 0` that was added to the PR `build_docs` action. This should make the version metadata be correct (see pypa/setuptools-scm#480) ## Type of change <!-- Please delete options that are not relevant. --> - [x] Fixes or improves existing content - [ ] Adds new content page(s) - [ ] Fixes or improves workflow, documentation build or deployment # References Adresses issue noted here napari/napari#5509 (comment) ## Final checklist: - [x] My PR is the minimum possible work for the desired functionality
…stitutions (#5557) # Description This PR an an analog to napari/docs#99 The built docs built by this repo PR action have improper napari version substitution (see napari/docs#51) This PR fixes that based on the README of https://github.com/actions/checkout It updates the deploy action with `fetch-depth: 0`. You can see that this was added to the napari/docs PR build_docs action and works correctly. This makes the version metadata be correct (see pypa/setuptools-scm#480) ## Type of change - [x] Bug-fix (non-breaking change which fixes an issue) # References Motivated by napari/docs#51 Analog to napari/docs#99
Description
As in napari/napari#5345 at the
napari
main repository discussed I added a small info box for the case that theconda
installation does not work propperly.In this case
mamba
is a good alternative.Type of change
References
@psobolewskiPhD recommended
mamba
How has this been tested?
Final checklist:
trans.
to make them localizable.For more information see our translations guide.
@jaimergp