autodoc | PostgreSQL Autodoc - dumps a Postgres schema | SQL Database library

Python imports work only on a file system, not from a URL. You may install a package from a URL into your file system and preferably a virtual environment, then Python will be able to import the package from there.

As for me you should use relative import - with dot

Do you know what kind of program it is? Windows? ASP.NET? MVC?

The errors are shown, but let's go through them:

In your conf.py, put sys.path.insert(0, ".."). The ../ relative path navigates to the parent directory. Since conf.py is located in docs/, the parent directory of docs/ is the root of your project. This way, sphinx will be able to access your project files and it will be able to import your modules.

The :no-index: is an option used under Sphinx and autodoc directives.

From Sphinx domains and directives:

Basic Markup

If you want to typeset an object description, without even making it available for cross-referencing, you can give the directive option flag :noindex: (which implies :noindexentry:)

From the autodoc extension:

Options and advanced usage - Directives

All autodoc directives support the noindex flag option that has the same effect as for standard py:function etc. directives: no index entries are generated for the documented object (and all autodocumented members)

What this means is that when you declare a .. directive:: with the usual syntax, the :noindex: option goes underneath the directive (mind the indentation):

UPDATE: With Robot Framework this has changed and became easier to do.

Release note: Running and result models have been changed.

• TestSuite, TestCase and Keyword objects used to have keywords attribute containing keywords used in them. This name is misleading now when they also have FOR and IF objects. With TestCase and Keyword the attribute was renamed to body and with TestSuite it was removed altogether. The keywords attribute still exists but it is read-only and deprecated.
• The new body does not have create() method for creating keywords, like the old keywords had, but instead it has separate create_keyword(), create_for() and create_if() methods. This means that old usages like test.keywords.create() need to be changed to test.body.create_keyword().

For examples check out this other answer: How to write FOR loop and IF statement programmatically with Robot Framework 4.0?.

The if statement should be a Run Keyword If keyword with the arguments you need. It is a keyword like any other so you should list everything else in its args list.

• The condition.
• The keyword name for the True branch.
• Separately any args to the keyword for the True branch if there is any. Listed separately.

• The ELSE IF keyword if needed.
• The ELSE IF condition.
• The keyword name for the ELSE IF branch.
• Separately any args to the keyword for the ELSE IF branch if there is any. Listed separately.

• The ELSE keyword.
• The keyword name for the ELSE branch.
• Separately any args to the keyword for the ELSE branch if there is any. Listed separately.

The problem with parsing comments as part of your syntax is that they can crop up absolutely anywhere. If they aren't ignored, then you have to insert them throughout your parser.

What you might do is use two passes, one for the syntax elements and one for the comments, and capture the locations of each using locatedExpr or parse actions, or use scanString (which returns the start and end of each matched location). Then match up the locations of the comments and the important syntax elements.

The extensions configuration contains both numpydoc and sphinx.ext.napoleon.

I don't know the exact cause of your problem, but these extensions are quite similar and you should use only one of them.

And there should be a blank line before "PyTuner tunertools".

Lets say you have 1 module with 2 functions and 3 docstrings, e.g:

acat.build.actions.py