Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can't do what you're looking to do, in the way you want to do it.</p> <p>From your description it seems like you could do something like this:</p> <pre><code>for tool in find_tools(): def __tool(*arg): validate_args(tool, args) return execute_tool(tool, args) __tool.__name__ = tool.name __tool.__doc__ = compile_docstring(tool) setattr(module, tool.name, __tool) </code></pre> <p>i.e. create the documentation string dynamically up-front when you create the function. Is the a reason why the docstring has to be dynamic from one call to <code>__doc__</code> to the next?</p> <p>Assuming there is, you'll have to wrap your function up in a class, using <code>__call__</code> to trigger the action.</p> <p>But even then you've got a problem. When help() is called to find the docstring, it is called on the class, not the instance, so this kind of thing:</p> <pre><code>class ToolWrapper(object): def __init__(self, tool): self.tool = tool self.__name__ = tool.name def _get_doc(self): return compile_docstring(self.tool) __doc__ = property(_get_doc) def __call__(self, *args): validate_args(args) return execute_tool(tool, args) </code></pre> <p>won't work, because properties are instance, not class attributes. You can make the doc property work by having it on a metaclass, rather than the class itself</p> <pre><code>for tool in find_tools(): # Build a custom meta-class to provide __doc__. class _ToolMetaclass(type): def _get_doc(self): return create_docstring(tool) __doc__ = property(_get_doc) # Build a callable class to wrap the tool. class _ToolWrapper(object): __metaclass__ = _ToolMetaclass def _get_doc(self): return create_docstring(tool) __doc__ = property(_get_doc) def __call__(self, *args): validate_args(tool, args) execute_tool(tool, args) # Add the tool to the module. setattr(module, tool.name, _ToolWrapper()) </code></pre> <p>Now you can do</p> <pre><code>help(my_tool_name) </code></pre> <p>and get the custom docstring, or</p> <pre><code>my_tool_name.__doc__ </code></pre> <p>for the same thing. The <code>__doc__</code> property is in the <code>_ToolWrapper</code> class is needed to trap the latter case.</p>
    singulars
    1. This table or related slice is empty.
    1. PODynamic function docstring
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USIan
    1. USIan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODynamic function docstring
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI can't comment on someone else's post yet (newbie, and all), but I want to say that overloading help() isn't a great solution, because you can't guarantee that anywhere help() will be called will use your version rather than the default version. Relying on that kind of monkey patching, in my experience, leads to difficult to debug problems at a later date when an unexpected use-case arrives (such as a new documentation tool, or a user with an 'enhanced' ipython, or a GUI help in an IDE, etc, etc).
      singulars
      1. PO
      1. USIan
    2. COExcellent, this did the trick. The first two code examples are just what I wrote before posting the question. I agree that overloading help is not a great idea.
      singulars
      1. PO
      1. USTom Aldcroft
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload