DOC: link out to troubleshooting guide in install #27226
Conversation
doc/devel/development_setup.rst
Outdated
| @@ -173,6 +173,10 @@ When working on a branch that does not have Meson enabled, meaning it does not | |||
| have :ghpull:`26621` in its history (log), you will have to reinstall from source | |||
| each time you change any compiled extension code. | |||
|
|
|||
| If the installation is not working, please consult the :ref:`troubleshooting guide <troubleshooting-faq>` | |||
| for a potential solution before filing a bug report or reaching out to us. | |||
There was a problem hiding this comment.
| for a potential solution before filing a bug report or reaching out to us. | |
| for a potential solution. |
It reads a bit less defensive this way.
There was a problem hiding this comment.
I meant it in the opposite - if it's not in the guide you should reach out. Let me rewrite that .
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
…3.8.x Backport PR #27226 on branch v3.8.x (DOC: link out to troubleshooting guide in install)
PR summary
Per #27168 (comment), figured it wouldn't hurt to signpost "hey, we have a troubleshooting section over there (that links to our other troubleshooting section)" Went slightly more general than that comment suggested just because there's more than just Windows mentioned in the troubleshooting guide.