Validate input AST for user facing functions about astor HOT 4 OPEN

Thanks for the report. I think that would be a good feature, but the tricky part is that we need to keep in mind different Python versions when doing validation. For example, wrapping int with ast.Num might be the correct solution for Python 3.x and 3.x+1. However, Python 3.x+2 might need ast.Number or ast.Guido in the future.

from astor.

In general, I'm not a big fan of slowing down the general case for exceptions.

I would support your proposal turned inside out; e.g. we wrap the top functions with try/except Exception , and if an exception occurs, we transfer control to a function that tries to do a better job of explaining to the caller what went wrong (e.g. re-raise a different exception).

from astor.

@pmaupin Interesting point of view! Makes sense to me and does seem like a better approach.

from astor.

Also, I don't have any time right now, but if someone is looking at this, we should probably merge my current PRs (or not) first...

from astor.