I think everything works as intended as long as X_SYNTHETIC_NODES_ENABLED is not true. I'm still trying to figure out why, when synthetic nodes are turned on (for example something like: @zeroOrMoreThing = (...)*) the Python Congo parser reports the same beginning offset for the synthetic node as Java, but reports the ending offset as the first parsed token that follows, instead of the first token following (unparsed or parsed) as is the case with Java. This quirk causes the test-python to fail, so I can't check that in yet. So, I'll do another PR when that is solved.
I think everything works as intended as long as
X_SYNTHETIC_NODES_ENABLEDis nottrue. I'm still trying to figure out why, when synthetic nodes are turned on (for example something like:@zeroOrMoreThing = (...)*) the Python Congo parser reports the same beginning offset for the synthetic node as Java, but reports the ending offset as the first parsed token that follows, instead of the first token following (unparsed or parsed) as is the case with Java. This quirk causes the test-python to fail, so I can't check that in yet. So, I'll do another PR when that is solved.