[WIP] Better identify dependencies for latex/pdf report functionalities #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces a new
PDF_SUPPORT
global boolean flag in thereport
module which identifies ifmatplotlib
,pylatex
andlatexmk
are present. This leaves bothmatplotlib
andpylatex
as optional dependencies to be installed via the PDFextras_require
option. We can also ship "elegant-lite" windows installers without both these requirements.This is related to issue #42.
I'm thinking we could rewrite the plain text report in either markdown or rST, so that at least some formatting is preserved. Any ideas?