-
Notifications
You must be signed in to change notification settings - Fork 391
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
Dead links at PyPI #1287
Comments
Oh yes you're right! It seems that I am asking to much from my @choldgraf or @mahendrapaipuri do you know if I can pre-process the |
hmmm, I'm not sure. You could define a template README.md (e.g. |
@mwouts I think you can include the absolute links instead of relative paths in README so that they work everywhere. Instead of something like:
using something like
What do you think? |
Well, I need the relative links, as we do use this file in the documentation. I think I am looking for a build hook, maybe something like #1298 could work? |
Ah, ok, I see. You are using the README in the sphinx docs as well. In that case, may be a simple option would be to copy the README (with absolute links) file into docs folder before compiling sphinx. You can add it as a target into Sphinx Makefile. Something like:
And make the above target as dependent to build target for Sphinx docs. |
Most of the links at the jupytext Project description page on PyPI lead to "Page Not Found".
Examples:
The text was updated successfully, but these errors were encountered: