I have conflicting opinions on this one that lead me to believe we may need both.
The complaint I hear most about Gremlin Python is not that the step names are not "Pythonic" - in fact I don't think I have ever had a user say that to me me. What I do hear a lot is that people find it difficult (and error prone) that you cannot just copy and paste a query from the Gremlin Console into Python. I suppose there are two classes of users here. 1. Those who use Python to get a job done as it is simple and broadly supported. I would put myself in that category. I write a lot of Python but I would never call myself a "Pythonista" :-) 2. Those who are doing mainstream development in Python and trying to following all of the PEP8 best practices and other in-house coding standards. This class of user may indeed appreciate a more Python like syntax. I have no issue with supporting a more snake case style syntax etc. but I do not want to see the current syntax go away really either. I know that supporting two of something can be additional work but I do not think we could make a hard breaking change here anyway. Too much Gremlin Python is in production today. I think the bigger issue honestly, that I know is the subject of another thread, is that it is too hard to accurately migrate "Gremlin Console" syntax to Gremlin Python syntax. Tools that simplify that task I think are a much higher ask from users than having a more "Pythonic" syntax. I have had multiple users ask me about that conversion and I have lost count of how many users I have had to help convert "as" steps to "as_" steps etc. Cheers, Kelvin
