Python repr fix for RecursionError caused by circular references in lanelets with regulatory elements #372
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.
This MR contains some small fixes related to calling
repr
andstr
on python lanelet objects.repr
of a lanelet that contains regulatory elements with a reference back to the lanelet, you currently getThis is fixed by printing only
str
forLanelet
s inRuleParameter
instead ofrepr
, which breaks the loopstr
now returns a concise information whereasrepr
contains the full object description in more cases.For some reason this is not working as expected for
RuleParameterMap
, as can be seen by trying to runstd::cout << trafficLightRegelem->getParameters();
here. Hence, I had to add methods for therepr
of theRuleParameterMap
Example code: