For the sake of expedience, I'm going to accept this and tweak it further. In the future, it's better to have a ticket and reference that ticket in the pull request and commits for better visibility to the changes and issues that it creates. I also suggest providing better commit messages. "Fix docs to work" is barely better than "changed things". The commit message should attempt to communicate the why and the how of the change at a high level. Something like "Added path in sphinx docs to allow setup.py to be imported when docs are built from docs directory."

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/setuptools.txt b/docs/setuptools.txt
index 86e23ff9..c3844cf2 100644
--- a/docs/setuptools.txt
+++ b/docs/setuptools.txt
@@ -479,7 +479,7 @@ script called ``baz``, you might do something like this::
                 'bar = other_module:some_func',
             ],
             'gui_scripts': [
-                'baz = my_package_gui.start_func',
+                'baz = my_package_gui:start_func',
             ]
         }
     )