You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this experimentally: is it assumed that access to the results are only valid as long as the parser object lives / is in scope?
I noticed that when I have a function that instantiates the parser and returns the result of the parse output I will regularly get segfaults. This isn't very Python and might need a bigger warning and/or some utilities to assist managing the lifecycle ...
The text was updated successfully, but these errors were encountered:
I could make the Result object a bit smarter by proxying the underlying attributes to the result ... but for understanding the issue, this should suffice.
I found this experimentally: is it assumed that access to the results are only valid as long as the parser object lives / is in scope?
I noticed that when I have a function that instantiates the parser and returns the result of the
parse
output I will regularly get segfaults. This isn't very Python and might need a bigger warning and/or some utilities to assist managing the lifecycle ...The text was updated successfully, but these errors were encountered: