Closed leo-brewin closed 4 years ago
That weird closing bracket was definitely a bug in the pre-parser; interestingly this then prevented another bug from ever being triggered, and the property parser fortunately was nice enough to let this pass. Now all fixed on github/master.
The second one is safe to delete, but won't do any harm. At some point in the past it was necessary to inform python about Ex
objects which go out of scope immediately, but this is no longer necessary and the 2nd parameter is in fact ignored.
Thanks for the update. I'm inclined to rewrite parts of the tutorial to not suggest that people edit the output of cadabra2python. That will avoid these issues. Though I might still include a copy of the output in the tutorial just for the readers reference.
Sorry I messed up with the GitHub buttons :).
Running
cadabra2python
over the following codeproduces the following output
position=independent)
required?False
argument toEx
required?False
argument?