This repository has been archived by the owner on Sep 14, 2022. It is now read-only.
Fixed a bug causing epydoc to fail #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you please comment on where you saw this issue happening or what commands when you ran into this? |
|
I believe this was causing a python error anytime a rosdoc.yaml had a builder set to epydoc. However, since things seem to have switched to rosdoc_lite it hasn't been showing up anymore. |
|
Closing as this does not appear to be an issue any more. And I think we're entirely switched to rosdoc_lite. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The parameters for roslib.launcher._generate_python_path were changed a while ago, and generate_epydoc() wasn't changed to reflect that.