Ensure $HOME is set before calling pandoc --version

[tkob]

This PR fixes the problem described in #103 .

In #103, I suggested using --data-dir option, but it is not usable since pandoc ignores --data-dir option if --version is specified.

This PR takes another aproach; creates an environment which is local to pandoc --version and supply $HOME if it is not set.

[bebraw]

Looks good to me.

@JanSchulz Any thoughts? Want to merge and publish?

[jankatins]

LGTM...

The problem I have right now is that I don't have my package builder running. I can cut a "normal" release without a problem, but not the wheels with embedded pandoc.

So:

• normal source release is possible
• conda packages (via conda-forge) are possible
• wheels with pandoc included are not

[bebraw]

Yeah, that's fine. I guess the embedded release can wait. Would it be possible to push that somewhere so it's easier to handle?

[jankatins]

I had them build with the conda packages for my pwn channel, but doesn't work anymore :-( I want to have a similar setup: three CI services which build the wheels and upload them. Still waiting for some twine changes and then I have to sit down and write the CI scripts. But the latter seems to take a bit of time... A bit more probably, as debugging is hard with CI scripts :-/

[jankatins]

Btw @tkob Does converting work? Or does that also need the same workaround?

[tkob]

I believe convert() etc. now work since pandoc (i.e. no --version) does not fail when HOME is not set:

$ unset HOME
$ echo hello | pandoc
<p>hello</p>
$ pandoc --version
pandoc: HOME: getAppUserDataDirectory: does not exist (no environment variable)

[jankatins]

@tkob Thanks!

Looks like this was missed upstream? Maybe file a bug there?

[jankatins]

@bebraw I've cut a new release (1.2.0) and uploaded the sdist and updated the conda packages.

[bebraw]

Nice. 👍