Skip to content
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

Code reference pages return 404 error #114

Closed
IngoScholtes opened this issue Feb 22, 2024 · 4 comments
Closed

Code reference pages return 404 error #114

IngoScholtes opened this issue Feb 22, 2024 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@IngoScholtes
Copy link
Member

This holds for all classes in the core module, e.g. this on as well as for the io and nn modules.

@IngoScholtes IngoScholtes added the documentation Improvements or additions to documentation label Feb 22, 2024
@IngoScholtes IngoScholtes added this to the End of February Demo milestone Feb 22, 2024
@M-Lampert
Copy link
Contributor

Sorry, I am currently working on a fix for the version selector returning a 404 error. During that the documentation might have not been available for a few minutes. This might be because of this.

@IngoScholtes
Copy link
Member Author

No need to be sorry and thanks for your great work!

@M-Lampert
Copy link
Contributor

I finally found a solution for the problem that using version selector leads to a 404 error. Since the problem did not occur locally on http://localhost:8000/, I could only test it directly on pathpy.net. I checked the mentioned parts of the Documentation again and now everything works again as it should.

I think this example highlights very well why it is nice to have a versioned documentation. When we finally have a first stable release on pip and publish the corresponding stable documentation page, then no matter what problems might currently occur on the dev documentation, the stable documentation corresponding to each release will still be available.

@IngoScholtes
Copy link
Member Author

As soon as I have completed the refactoring of the PathData class (and as soon as we have expanded the test coverage a bit more), we can release a first stable version. After this refactoring is done, I do not expect substantial API changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants