Right now withStrategies() is not supported by Gremlin-Python. Why? Because strategies are created via Java and thus you can't do stuff like:
Now, we have strategies that we have made "native" to GraphTraversalSource by way of withXXX. For example: withSideEffect(), withSack(), withRemote(), withPath(), etc.
In order to generally support any strategy created by a user for use from a language variant, we should support lambda based strategies. E.g.:
Like any other lambda, it is executed server side using the respective ScriptEngine.
Next, withoutStrategies() should support String... so you can do:
..instead of having to pass in the Class object.