FWIW, I think that's the format that PyCharm auto inserts, so I'm guessing it conforms to some standard somewhere.  And if you are using pycharm, @VikParuchuri you could probably configure it.

On Sep 20, 2013, at 1:14 PM, brianhw <notifications@github.com> wrote:

> In lms/djangoapps/open_ended_grading/utils.py:
> 
> > +    ajax_url=None,
> > +    track_function=None,
> > +    get_module=None,
> > +    render_template=render_to_string,
> > +    replace_urls=None,
> > +    xmodule_field_data=DictFieldData({}),
> > +    )
> > +
> > +controller_qs = ControllerQueryService(settings.OPEN_ENDED_GRADING_INTERFACE, system)
> > +
> > +def generate_problem_url(problem_url_parts, base_course_url):
> > +    """
> > +    From a list of problem url parts generated by search.path_to_location and a base course url, generates a url to a problem
> > +    @param problem_url_parts: Output of search.path_to_location
> > +    @param base_course_url: Base url of a given course
> > +    @return: A path to the problem
> Not familiar with this docstring convention -- looks like Java. As far as I can tell, our docstring convention is merely: "Write in Sphinx-friendly prose style. Put backquotes around code names (variables, parameters, methods, etc)".
> 
> —
> Reply to this email directly or view it on GitHub.
>