Literate-style documentation generator.

Related tags

Documentation pycco
Overview
888888b.
888   Y88b
888    888
888   d88P  888  888   .d8888b  .d8888b  .d88b.
8888888P"   888  888  d88P"    d88P"    d88""88b
888         888  888  888      888      888  888
888         Y88b 888  Y88b.    Y88b.    Y88..88P
888          "Y88888   "Y8888P  "Y8888P  "Y88P"
                 888
            Y8b d88P
             "Y88P"

Pycco is a Python port of Docco: the original quick-and-dirty, hundred-line- long, literate-programming-style documentation generator. For more information, see:

https://pycco-docs.github.io/pycco/

Others:

CoffeeScript (Original) - http://jashkenas.github.com/docco/

Ruby - http://rtomayko.github.com/rocco/

Sh - http://rtomayko.github.com/shocco/

Build Status Coverage Status

Comments
  • Multi line comments (was

    Multi line comments (was "Format module docstrings")

    If a module has a docstring, e.g.

    """
    This is the docstring
    """
    
    print "module code starts here"
    

    the docstring isn't converted properly.

    opened by akaihola 20
  • Integration of pycco in build scripts /

    Integration of pycco in build scripts / "importable" pycco

    I'd like to import the pycco module in my own python build script, but currently there are a few show stoppers:

    • there is no "entry point" function for pycco doc generation that I could invoke from my script (e.g. pycco.generate_docs(path_to_scriptdir))
    • pycco assumes that you have cd'ed to your script directory before generating the docs, it can't handle absolute or relative paths... this isn't possible in build scripts
    • there should be an option to specify the output path of the docs.
    opened by fbuchinger 15
  • Option --skip-bad-files now skips all kind of bad files

    Option --skip-bad-files now skips all kind of bad files

    I had some problems running pycco in a directory containing some cached Pytest files (.pytest_cache/). I noticed that even if the --skip-bad-files option was used, Pycco would still fail to generate the documentation. Removing the cached files is an option of course, but in my opinion Pycco should treat those files as bad files.

    Given a .pytest_cache dire.tory (AFAIK it should be generate by Pytest when running the tests), the new behavior is the following,

    With the --skip-bad-files option

     ~/r/pycco git:(master) ✗ ➜ pycco --skip-bad-files  .pytest_cache/
    pycco [FAILURE]: .pytest_cache/v/cache/lastfailed, Can't figure out the language!
    pycco [FAILURE]: .pytest_cache/v/cache/nodeids, Can't figure out the language!
    

    Without the --skip-bad-files option

     ~/r/pycco git:(master) ✗ ➜ pycco .pytest_cache/
    Traceback (most recent call last):
      File "/home/vrde/repos/pycco/pycco/main.py", line 392, in get_language
        lang = lexers.guess_lexer(code).name.lower()
      File "/home/vrde/.local/share/virtualenvs/1e40936ec5d4128/lib/python3.6/site-packages/pygments/lexers/__init__.py", line 252, in guess_lexer
        raise ClassNotFound('no lexer matching the text found')
    pygments.util.ClassNotFound: no lexer matching the text found
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/home/vrde/.local/share/virtualenvs/1e40936ec5d4128/bin/pycco", line 11, in <module>
        load_entry_point('Pycco', 'console_scripts', 'pycco')()
      File "/home/vrde/repos/pycco/pycco/main.py", line 620, in main
        skip=opts.skip_bad_files)
      File "/home/vrde/repos/pycco/pycco/main.py", line 532, in process
        next_file()
      File "/home/vrde/repos/pycco/pycco/main.py", line 520, in next_file
        encoding=encoding))
      File "/home/vrde/repos/pycco/pycco/main.py", line 65, in generate_documentation
        return _generate_documentation(source, code, outdir, preserve_paths, language)
      File "/home/vrde/repos/pycco/pycco/main.py", line 72, in _generate_documentation
        language = get_language(file_path, code, language=language)
      File "/home/vrde/repos/pycco/pycco/main.py", line 402, in get_language
        raise ValueError("Can't figure out the language!")
    ValueError: Can't figure out the language!
    
    opened by vrde 11
  • Multiple code blocks require extra indentation

    Multiple code blocks require extra indentation

    When I parse this docstring

    """
    This is the first code sample
    
        alpha
    
    This is the second code sample
    
        gamma
    """
    

    ... I get the following format:

    This is the first code sample

    alpha

    This is the second code sample

    gamma

    But if I indent the second code block further, like this:

    """
    This is the first code sample
    
        alpha
    
    This is the second code sample
    
            gamma
    """
    

    ... I get the desired output:

    This is the first code sample

    alpha

    This is the second code sample

    gamma

    The problem vanishes if https://github.com/fitzgen/pycco/blob/master/pycco/main.py#L128 is changed from

    last_scope = current_scope if current_scope > last_scope else last_scope
    

    ... to ...

    last_scope = current_scope
    

    Is this a valid change? Or would it break something?

    Regards Anand

    opened by sanand0 7
  • Release a new version to the PyPI

    Release a new version to the PyPI

    I just installed pycco using pip and was wondering why the background was not staying behind the code when scrolling horizontally, which was fixed over a year ago. It turns out there hasn't been a new version for quite some time :) It'd be great if a new version could be released!

    :shipit:

    opened by x3ro 6
  • HTML <> are getting _incorrectly_ escaped

    HTML <> are getting _incorrectly_ escaped

    Steps

    1. Install pycco using pip install pycco (Dependencies such as pygments, pystache, etc are installed)
    2. cd /usr/local/lib/python2.6/dist-packages/pycco (As one example).
    3. Run pycco main.py (That is to say, run pycco against the pycco source)

    Expected results

    Page identical to http://fitzgen.github.com/pycco/ appears.

    Actual results

    I believe this page is getting generated correctly, EXCEPT that all the <> in the HTML are being escaped (presumably by pystache) into < and >, so the page is more-or-less the raw HTML instead of the rendered HTML. The pypi package of pystache was updated 3-25-12, so I'm guessing this is what has caused pycco to fail. I haven't looked into whether this is a bug on the pystache side as opposed to the pycco side.

    Notes

    My guess is that pycco is just not using the un-escaping versions of mustache tags {{&..}} and {{{..}}}, but what do I know? My extremely quick attempt at resolving the issue didn't fix it.

    opened by kespindler 4
  • Language extension is replaced everywhere in the generated filename

    Language extension is replaced everywhere in the generated filename

    Hi, whatever.jsonschema.js filename will generate an html file named whateveronschema.html. It looks like languages extensions are replaced everywhere in the filename. I had the version from pip. Regards.

    opened by t3h 4
  • Packaging clean up, reorganization, C delimiters, Python2.5 compatibility.

    Packaging clean up, reorganization, C delimiters, Python2.5 compatibility.

    Changelog

    • Add Python 2.5 compatibility
    • Add python2.5 compatible with_statement and format
    • Add Python 2.5 compatibility
    • Add python2.5 compatible with_statement and format
    • Removes commented unnecessary code
    • Adds charset and content type to css link
    • Makes generated docs preserve source fileextension
    • Minifies generated CSS using cssmin
    • Removes reference to the pycco/resources.py file
    • Removes pycco/resources.py
    • Moves resources into separate editable files
    • Updates console script to pycco/init.py
    • Renames the main.py script to init.py
    • Removes the pycco/init.py file
    • Adds ignore rules to exclude buildout directories
    • Adds zc.buildout configuration and bootstrap script
    • Moves the pycco_resources package into a module
    • Updates documentation for script entry-point
    • Replaces relative wildcard import with explicit
    • Adds MANIFEST.in to distribute additional files
    • Cleans up setup.py
    • Adds UTF-8 as encoding for Python source files
    • Cleans up AUTHORS, README, and LICENSE
    • Adds multiline comment delimiters for C and C++
    opened by gorakhargosh 4
  • h3 header?

    h3 header?

    How do I get an h3 header (f.e. the "Main Documentation Generation Functions" in http://fitzgen.github.com/pycco/)?

    I'm writing Javascript and whenever I do: // === Yadda === I get an em instead of an h3.

    opened by timmolendijk 4
  • Support multiline comment continuations

    Support multiline comment continuations

    This patch supports comments of the form:

    /*
     * some comment
     * continues for a while
     *
     */
    

    Specifically, it removes the "*" in the middle lines so they don't appear in the output as a markdown bulleted list.

    This addresses issue 30 (https://github.com/fitzgen/pycco/issues/30)

    opened by chsnow 3
  • Add Rudimentary HTML Support

    Add Rudimentary HTML Support

    This is a great project! I used it for a project documenting how to integrate Livefyre for our customers. It helped a lot!

    I wanted to use it on an HTML document, though. So I added rudimentary HTML support for multiline comments. I couldn't do it with the built in symbol-only definition in the langs dict, so I added two lines to generate_html to let me explicitly define divider_text and divider_html.

    You can see it in action here: http://demos.livefyre.com/ssosandbox/help/

    I will probably have a need soon to add support for not needing to have a newline between the <!-- and the actual comment, but I think that will be more invasive. Someone might be able to tweak a regex somewhere to do it easily. I didn't grok the whole program, but like I said, it's great!

    opened by gobengo 3
  • Switch to pathlib (py3 stdlib module)

    Switch to pathlib (py3 stdlib module)

    As Python2 is long overdue to be phased-out I switched the os.path module to use the recommended pathlib module instead - and through that fixing the watcher which did no longer work for me.

    The first commit just reformats everything with black (if thats an issue let me know then I could potentially "undo" that).

    opened by hv10 0
  • Imports blow up in pystache

    Imports blow up in pystache

    matth@lenovo MINGW64 ~/GitHub/no_algo_twitter (main)
    $ pycco src/*.py
    Traceback (most recent call last):
      File "C:\Users\matth\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 194, in _run_module_as_main
        return _run_code(code, main_globals, None,
      File "C:\Users\matth\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 87, in _run_code
        exec(code, run_globals)
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\Scripts\pycco.exe\__main__.py", line 4, in <module>
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\__init__.py", line 1, in <module>
        from .main import *  # noqa
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\main.py", line 60, in <module>
        from pycco.generate_index import generate_index
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco\generate_index.py", line 9, in <module>
        from pycco_resources import pycco_template
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pycco_resources\__init__.py", line 1, in <module>
        import pystache
      File "C:\Users\matth\.virtualenvs\no_algo_twitter-Vk_lV-hQ\lib\site-packages\pystache\__init__.py", line 2, in <module>
        from init import *
    ModuleNotFoundError: No module named 'init'
    
    matth@lenovo MINGW64 ~/GitHub/no_algo_twitter (main)
    $ python --version
    Python 3.8.7
    
    

    I think it is blowing up on some really old school import syntax. I don't remember seeing that sort of import that omits the package name since python 2.

    There is some motion to take over pystache ref: https://github.com/pypa/pypi-support/issues/1422 and we could see new releases of pystache, but in the meanwhile, pycco seems to be broken in a lot of venvs.

    opened by matthewdeanmartin 0
  • Docstring that ends with

    Docstring that ends with""" rather than \n""" completely breaks rendering

    Hi There,

    Thanks for this awesome tool. Running into an issue where these docstrings break rendering:

    def add(x, y):
      """This should be a simple docstring
      However, it turns everything following it into a comment."""
      return x + y
    

    Only this works:

    def add(x, y):
      """This should be a simple docstring
      However, it turns everything following it into a comment.
      """
      return x + y
    

    Given this particular formatting is not picked up on by pylint, I assume it is valid and this is a bug.

    bug 
    opened by Pet3ris 0
  • ClassNotFound('no lexer  . . .

    ClassNotFound('no lexer . . .

    Not sure what the root cause is here

    Traceback (most recent call last): File "/usr/local/bin/pycco", line 33, in <module> sys.exit(load_entry_point('Pycco==0.6.0', 'console_scripts', 'pycco')()) File "/usr/local/bin/pycco", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/local/Cellar/[email protected]/3.9.5/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/metadata.py", line 77, in load module = import_module(match.group('module')) File "/usr/local/Cellar/[email protected]/3.9.5/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 664, in _load_unlocked File "<frozen importlib._bootstrap>", line 627, in _load_backward_compatible File "<frozen zipimport>", line 259, in load_module File "/usr/local/lib/python3.9/site-packages/Pycco-0.6.0-py3.9.egg/pycco/__init__.py", line 1, in <module> # -*- coding: utf-8 -*- File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 664, in _load_unlocked File "<frozen importlib._bootstrap>", line 627, in _load_backward_compatible File "<frozen zipimport>", line 259, in load_module File "/usr/local/lib/python3.9/site-packages/Pycco-0.6.0-py3.9.egg/pycco/main.py", line 373, in <module> File "/usr/local/lib/python3.9/site-packages/Pycco-0.6.0-py3.9.egg/pycco/main.py", line 369, in compile_language File "/usr/local/lib/python3.9/site-packages/pygments/lexers/__init__.py", line 93, in get_lexer_by_name raise ClassNotFound('no lexer for alias %r found' % _alias) pygments.util.ClassNotFound: no lexer for alias 'stata' found

    opened by brucebookman 0
  • Bump pygments from 2.5.2 to 2.7.4

    Bump pygments from 2.5.2 to 2.7.4

    Bumps pygments from 2.5.2 to 2.7.4.

    Release notes

    Sourced from pygments's releases.

    2.7.4

    • Updated lexers:

      • Apache configurations: Improve handling of malformed tags (#1656)

      • CSS: Add support for variables (#1633, #1666)

      • Crystal (#1650, #1670)

      • Coq (#1648)

      • Fortran: Add missing keywords (#1635, #1665)

      • Ini (#1624)

      • JavaScript and variants (#1647 -- missing regex flags, #1651)

      • Markdown (#1623, #1617)

      • Shell

        • Lex trailing whitespace as part of the prompt (#1645)
        • Add missing in keyword (#1652)
      • SQL - Fix keywords (#1668)

      • Typescript: Fix incorrect punctuation handling (#1510, #1511)

    • Fix infinite loop in SML lexer (#1625)

    • Fix backtracking string regexes in JavaScript/TypeScript, Modula2 and many other lexers (#1637)

    • Limit recursion with nesting Ruby heredocs (#1638)

    • Fix a few inefficient regexes for guessing lexers

    • Fix the raw token lexer handling of Unicode (#1616)

    • Revert a private API change in the HTML formatter (#1655) -- please note that private APIs remain subject to change!

    • Fix several exponential/cubic-complexity regexes found by Ben Caller/Doyensec (#1675)

    • Fix incorrect MATLAB example (#1582)

    Thanks to Google's OSS-Fuzz project for finding many of these bugs.

    2.7.3

    ... (truncated)

    Changelog

    Sourced from pygments's changelog.

    Version 2.7.4

    (released January 12, 2021)

    • Updated lexers:

      • Apache configurations: Improve handling of malformed tags (#1656)

      • CSS: Add support for variables (#1633, #1666)

      • Crystal (#1650, #1670)

      • Coq (#1648)

      • Fortran: Add missing keywords (#1635, #1665)

      • Ini (#1624)

      • JavaScript and variants (#1647 -- missing regex flags, #1651)

      • Markdown (#1623, #1617)

      • Shell

        • Lex trailing whitespace as part of the prompt (#1645)
        • Add missing in keyword (#1652)
      • SQL - Fix keywords (#1668)

      • Typescript: Fix incorrect punctuation handling (#1510, #1511)

    • Fix infinite loop in SML lexer (#1625)

    • Fix backtracking string regexes in JavaScript/TypeScript, Modula2 and many other lexers (#1637)

    • Limit recursion with nesting Ruby heredocs (#1638)

    • Fix a few inefficient regexes for guessing lexers

    • Fix the raw token lexer handling of Unicode (#1616)

    • Revert a private API change in the HTML formatter (#1655) -- please note that private APIs remain subject to change!

    • Fix several exponential/cubic-complexity regexes found by Ben Caller/Doyensec (#1675)

    • Fix incorrect MATLAB example (#1582)

    Thanks to Google's OSS-Fuzz project for finding many of these bugs.

    Version 2.7.3

    (released December 6, 2020)

    ... (truncated)

    Commits
    • 4d555d0 Bump version to 2.7.4.
    • fc3b05d Update CHANGES.
    • ad21935 Revert "Added dracula theme style (#1636)"
    • e411506 Prepare for 2.7.4 release.
    • 275e34d doc: remove Perl 6 ref
    • 2e7e8c4 Fix several exponential/cubic complexity regexes found by Ben Caller/Doyensec
    • eb39c43 xquery: fix pop from empty stack
    • 2738778 fix coding style in test_analyzer_lexer
    • 02e0f09 Added 'ERROR STOP' to fortran.py keywords. (#1665)
    • c83fe48 support added for css variables (#1633)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 1
  • Pycco is unable to determine syntax for a Python3-formatted file without an appropriate extension

    Pycco is unable to determine syntax for a Python3-formatted file without an appropriate extension

    When running pycco file, it works well when the file is named foo.py, but does not work for foo despite having a shebang.

    Example Script

    Create this file as example. Note that if it is named example.py, everything works as expected.

    #!/usr/bin/env python3
    import os
    
    class CommandLineFlag(object):
        '''Holds information about a command-line argument'''
    

    Pycco Output

    $ pycco example
    Traceback (most recent call last):
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 397, in get_language
        raise ValueError()
    ValueError
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/Users/zachriggle/Library/Python/3.8/bin/pycco", line 10, in <module>
        sys.exit(main())
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 629, in main
        process(args.sources, outdir=outdir, preserve_paths=args.paths,
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 533, in process
        next_file()
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 518, in next_file
        f.write(generate_documentation(s, preserve_paths=preserve_paths,
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 80, in generate_documentation
        return _generate_documentation(source, code, outdir, preserve_paths, language)
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 87, in _generate_documentation
        language = get_language(file_path, code, language_name=language)
      File "/Users/zachriggle/Library/Python/3.8/lib/python/site-packages/pycco/main.py", line 402, in get_language
        raise ValueError("Can't figure out the language!")
    ValueError: Can't figure out the language!
    
    opened by zachriggle 1
Releases(0.6.0)
  • 0.6.0(Jul 25, 2018)

    This release includes some code modernization and greater test coverage, plus:

    • one new feature, courtesy of @vrde: --skip-bad-files, also now aliased to --ignore-errors, does what it says on the tin: Pycco will continue operation if it encounters a file it does not understand.
    • three Markdown enhancements are available: smartypants (which, contrary to the documentation, wasn't enabled before), fenced code blocks, and footnotes.
    Source code(tar.gz)
    Source code(zip)
  • 0.5.1(Jun 4, 2016)

    Changes:

    • Courtesy of @goosemo, Pycco will recurse into directories given as arguments and attempt to process all the contents.
    • Added -s argument to continue processing a list of files (or directory) if an unprocessable file is encountered.
    Source code(tar.gz)
    Source code(zip)
  • 0.4(Dec 28, 2015)

  • v0.3.1(Nov 20, 2015)

Owner
Pycco
A Python port of docco, originally by @fitzgen.
Pycco
A curated list of awesome tools for Sphinx Python Documentation Generator

Awesome Sphinx (Python Documentation Generator) A curated list of awesome extra libraries, software and resources for Sphinx (Python Documentation Gen

Hyunjun Kim 831 Dec 27, 2022
Documentation generator for C++ based on Doxygen and mosra/m.css.

mosra/m.css is a Doxygen-based documentation generator that significantly improves on Doxygen's default output by controlling some of Doxygen's more unruly options, supplying it's own slick HTML+CSS generation and adding a fantastic live search feature.

Mark Gillard 109 Dec 7, 2022
Swagger Documentation Generator for Django REST Framework: deprecated

Django REST Swagger: deprecated (2019-06-04) This project is no longer being maintained. Please consider drf-yasg as an alternative/successor. I haven

Marc Gibbons 2.6k Jan 3, 2023
Markdown documentation generator from Google docstrings

mkgendocs A Python package for automatically generating documentation pages in markdown for Python source files by parsing Google style docstring. The

Davide Nunes 44 Dec 18, 2022
Main repository for the Sphinx documentation builder

Sphinx Sphinx is a tool that makes it easy to create intelligent and beautiful documentation for Python projects (or other documents consisting of mul

null 5.1k Jan 2, 2023
API Documentation for Python Projects

API Documentation for Python Projects. Example pdoc -o ./html pdoc generates this website: pdoc.dev/docs. Installation pip install pdoc pdoc is compat

mitmproxy 1.4k Jan 7, 2023
Main repository for the Sphinx documentation builder

Sphinx Sphinx is a tool that makes it easy to create intelligent and beautiful documentation for Python projects (or other documents consisting of mul

null 5.1k Jan 4, 2023
Project documentation with Markdown.

MkDocs Project documentation with Markdown. View the MkDocs documentation. Project release notes. Visit the MkDocs wiki for community resources, inclu

MkDocs 15.6k Jan 2, 2023
Watch a Sphinx directory and rebuild the documentation when a change is detected. Also includes a livereload enabled web server.

sphinx-autobuild Rebuild Sphinx documentation on changes, with live-reload in the browser. Installation sphinx-autobuild is available on PyPI. It can

Executable Books 440 Jan 6, 2023
Your Project with Great Documentation.

Read Latest Documentation - Browse GitHub Code Repository The only thing worse than documentation never written, is documentation written but never di

Timothy Edmund Crosley 809 Dec 28, 2022
:blue_book: Automatic documentation from sources, for MkDocs.

mkdocstrings Automatic documentation from sources, for MkDocs. Features Python handler features Requirements Installation Quick usage Features Languag

Timothée Mazzucotelli 1.1k Dec 31, 2022
Run `black` on python code blocks in documentation files

blacken-docs Run black on python code blocks in documentation files. install pip install blacken-docs usage blacken-docs provides a single executable

Anthony Sottile 460 Dec 23, 2022
:blue_book: Automatic documentation from sources, for MkDocs.

mkdocstrings Automatic documentation from sources, for MkDocs. Features - Python handler - Requirements - Installation - Quick usage Features Language

null 1.1k Jan 4, 2023
Seamlessly integrate pydantic models in your Sphinx documentation.

Seamlessly integrate pydantic models in your Sphinx documentation.

Franz Wöllert 71 Dec 26, 2022
NetBox plugin for BGP related objects documentation

Netbox BGP Plugin Netbox plugin for BGP related objects documentation. Compatibility This plugin in compatible with NetBox 2.10 and later. Installatio

Nikolay Yuzefovich 133 Dec 27, 2022
Automated Integration Testing and Live Documentation for your API

Automated Integration Testing and Live Documentation for your API

ScanAPI 1.3k Dec 30, 2022
Documentation of the QR code found on new Austrian ID cards.

Austrian ID Card QR Code This document aims to be a complete documentation of the format used in the QR area on the back of new Austrian ID cards (Per

Gabriel Huber 9 Dec 12, 2022
Test utility for validating OpenAPI documentation

DRF OpenAPI Tester This is a test utility to validate DRF Test Responses against OpenAPI 2 and 3 schema. It has built-in support for: OpenAPI 2/3 yaml

snok 106 Jan 5, 2023
Dev Centric Tools for Mkdocs Based Documentation

docutools MkDocs Documentation Tools For Developers This repo is providing a set of plugins for mkdocs material compatible documentation. It is meant

Axiros GmbH 14 Sep 10, 2022