pandoc-pyplot

A Pandoc filter to include figures generated from Python code blocks https://github.com/LaurentRDC/pandoc-pyplot#readme

Version on this page:1.0.3.0
LTS Haskell 13.22:1.0.3.0
Stackage Nightly 2019-05-21:2.1.1.1
Latest on Hackage:2.1.1.1

See all snapshots pandoc-pyplot appears in

MIT licensed and maintained by Laurent P. René de Cotret

Module documentation for 1.0.3.0

pandoc-pyplot - A Pandoc filter to generate Matplotlib figures directly in documents

Hackage version Stackage version (LTS) Stackage version (nightly) Build status GitHub

pandoc-pyplot turns Python code present in your documents into embedded Matplotlib figures.

Usage

The filter recognizes code blocks with the .pyplot class present. It will run the script in the associated code block in a Python interpreter and capture the generated Matplotlib figure.

Here is a basic example using the scripting matplotlib.pyplot API:

    ```{.pyplot}
    import matplotlib.pyplot as plt

    plt.figure()
    plt.plot([0,1,2,3,4], [1,2,3,4,5])
    plt.title('This is an example figure')
    ```

Putting the above in input.md, we can then generate the plot and embed it:

pandoc --filter pandoc-pyplot input.md --output output.html

or

pandoc --filter pandoc-pyplot input.md --output output.pdf

or any other output format you want.

There are more examples in the source repository, in the \examples directory.

Features

No wasted work

pandoc-pyplot minimizes work, only generating figures if it absolutely must. Therefore, you can confidently run the filter on very large documents containing dozens of figures — like a book or a thesis — and only the figures which have recently changed will be re-generated.

Link to source code and high-resolution figure

In case of an output format that supports links (e.g. HTML), the embedded image generated by pandoc-pyplot will be a link to the source code which was used to generate the file. Therefore, other people can see what Python code was used to create your figures. A high resolution image will be made available in a caption link.

Captions

You can also specify a caption for your image. This is done using the optional caption parameter:

    ```{.pyplot caption="This is a simple figure"}
    import matplotlib.pyplot as plt

    plt.figure()
    plt.plot([0,1,2,3,4], [1,2,3,4,5])
    plt.title('This is an example figure')
    ```

Caption formatting is either plain text or Markdown. LaTeX-style math is also support in captions (using dollar signs $…$).

Including scripts

If you find yourself always repeating some steps, inclusion of scripts is possible using the include parameter. For example, if you want all plots to have the ggplot style, you can write a very short preamble style.py like so:

import matplotlib.pyplot as plt
plt.style.use('ggplot')

and include it in your document as follows:

    ```{.pyplot include=style.py}
    plt.figure()
    plt.plot([0,1,2,3,4], [1,2,3,4,5])
    plt.title('This is an example figure')
    ```

Which is equivalent to writing the following markdown:

    ```{.pyplot}
    import matplotlib.pyplot as plt
    plt.style.use('ggplot')

    plt.figure()
    plt.plot([0,1,2,3,4], [1,2,3,4,5])
    plt.title('This is an example figure')
    ```

This include parameter is perfect for longer documents with many plots. Simply define the style you want in a separate script! You can also import packages this way, or define functions you often use.

Compatibility with pandoc-crossref

pandoc-crossref is a pandoc filter that makes it effortless to cross-reference objects on documents.

You can use pandoc-crossref in conjunction with pandoc-pyplot for the ultimate figure-making pipeline. You can combine both in a figure like so:

    ```{#fig:myexample .pyplot caption="This is a caption"}
    # Insert figure script here
    ```

    As you can see in @fig:myexample, ...

If the above source is located in file myfile.md, you can render the figure and references by applying pandoc-pyplot first, and then pandoc-crossref. For example:

pandoc --filter pandoc-pyplot --filter pandoc-crossref -i myfile.md -o myfile.html

Configurable

New in version 2.1.0.0

To avoid repetition, pandoc-pyplot can be configured using simple YAML syntax. pandoc-pyplot will look for a .pandoc-pyplot.yml file in the current working directory:

# You can specify any or all of the following parameters
interpreter: python36
directory: mydirectory/
include: mystyle.py
format: jpeg
dpi: 150

These values override the default values, which are equivalent to:

# Defaults if no configuration is provided.
interpreter: python
directory: generated/
format: png
dpi: 80

Installation

Binaries

Windows binaries are available on GitHub. Place the executable in a location that is in your PATH to be able to call it.

Installers

Windows installers are made available thanks to Inno Setup. You can download them from the release page.

From Hackage/Stackage

pandoc-pyplot is available on Hackage. Using the cabal-install tool:

cabal update
cabal install pandoc-pyplot

Similarly, pandoc-pyplot is available on Stackage:

stack update
stack install pandoc-pyplot

From source

Building from source can be done using stack or cabal:

git clone https://github.com/LaurentRDC/pandoc-pyplot
cd pandoc-pylot
stack install # Alternatively, `cabal install`

Running the filter

Requirements

This filter only works with the Matplotlib plotting library. Therefore, you a Python interpreter and at least Matplotlib installed. The name of the Python interpreter to use can be specified in a .pandoc-pyplot.yml file; by default, pandoc-pyplot will use the "python" name.

You can use the filter with Pandoc as follows:

pandoc --filter pandoc-pyplot input.md --output output.html

In which case, the output is HTML. Another example with PDF output:

pandoc --filter pandoc-pyplot input.md --output output.pdf

Python exceptions will be printed to screen in case of a problem.

pandoc-pyplot has a limited command-line interface. Take a look at the help available using the -h or --help argument:

pandoc-pyplot --help

Usage as a Haskell library

To include the functionality of pandoc-pyplot in a Haskell package, you can use the makePlot :: Block -> IO Block function (for single blocks) or plotTransform :: Pandoc -> IO Pandoc function (for entire documents).

Usage with Hakyll

This filter was originally designed to be used with Hakyll. In case you want to use the filter with your own Hakyll setup, you can use a transform function that works on entire documents:

import Text.Pandoc.Filter.Pyplot (plotTransform)

import Hakyll

-- Unsafe compiler is required because of the interaction
-- in IO (i.e. running an external Python script).
makePlotPandocCompiler :: Compiler (Item String)
makePlotPandocCompiler =
  pandocCompilerWithTransformM
    defaultHakyllReaderOptions
    defaultHakyllWriterOptions
    (unsafeCompiler . plotTransform)

The plotTransformWithConfig is also available for a more configurable set-up.

Warning

Do not run this filter on unknown documents. There is nothing in pandoc-pyplot that can stop a Python script from performing evil actions.

Changes

Change log

pandoc-pyplot uses Semantic Versioning

Release 2.1.1.1

  • Fixed a critical bug where pandoc-pyplot would interpret input from pandoc as a malformed command-line flag.

Release 2.1.1.0

  • Added a command-line option to open the HTML manual in the default web browser.
  • Added documentation regarding compatibility with pandoc-crossref. This was always supported but not explicitly documented.

Release 2.1.0.1

  • Fixed outdated documentation (referencing “target” parameter)
  • Fixed types required to build Configuration values that were not exported (SaveFormat, PythonScript)

Release 2.1.0.0

  • Added support for config files “.pandoc-pyplot.yml”, which specify different default values. This is mirrored in the new Configuration type and new functions, makePlotWithConfig and plotTransformWithConfig.
  • Added the ability to specify a different Python interpreter to use.
  • Added support for GIF and TIF files.
  • Added the “-f”/”–formats” command to show supported output figure formats.
  • Added support for GHC 8.2
  • Moved internal modules to Text.Pandoc.Filter.Pyplot.Internal module.

Release 2.0.1.0

  • Support for Markdown formatting in figure captions, including LaTeX math.

Release 2.0.0.0

Many breaking changes in this release:

  • pandoc-pyplot will now determine the filename based on hashing the figure content. Therefore, figures will only be re-generated if necessary.
  • Removed the ability to control the filename and format directly using the plot_target=... attribute.
  • Added the ability to control the directory in which figures will be saved using the directory=... attribute.
  • Added the possibility to control the figures dots-per-inch (i.e. pixel density) with the dpi=... attribute.
  • Added the ability to control the figure format with the format=... attribute. Possible values are currently "png", "svg", "pdf", "jpg"/"jpeg" and "eps".
  • The confusing plot_alt=... attribute has been renamed to caption=... for obvious reasons.
  • The plot_include=... attribute has been renamed to include=....
  • Added the generation of a higher resolution figure for every figure pandoc-pyplot understands.

Release 1.1.0.0

  • Added the ability to include Python files before code using the plot_include=script.py attribute.
  • Added a test suite.

Release 1.0.3.0

  • Fixed an issue where pandoc-pyplot would not build with base < 4.9 (#1)

Release 1.0.2.0

  • Added support for captions using the plot_alt=... attribute. For example:

      ```{plot_target=test.png plot_alt="This is a caption"}
      import matplotlib.pyplot as plt
      plt.figure()
      plt.plot([1,2,3,4,5],[1,2,3,4,5])
    
    
    

Release 1.0.1.0

  • Added plotTransform :: Pandoc -> IO Pandoc function to transform entire documents. This makes it easier to integrate pandoc-pyplot into Hakyll-based sites!

Release 1.0.0.1

  • Updated README with fixes and warnings
  • Added top-level package documentation compatible with Haddock
  • Added Unsafe language extension, as this filter will run arbitrary Python scripts.

Release 1.0.0.0

Initial release.

See documentation on Hackage

comments powered byDisqus