-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mkdocs2pandoc gives no output #3
Comments
Thanks for catching this! Looks like this appeared in 0.2.2, with the Python 3 compatibility code being the likely culprit. I shouldn't have tested it with just the
|
Works like a charm. Thanks for your valuable work! |
I'm glad the workaround works for you, but I'll leave this open nonetheless if you don't mind, since I'd rather fix this for all use cases including the one that didn't work for you :-) |
The Python 3 patch broke writing to standard output. This fixes the problem by moving the call to pconv.convert() back to its proper place, and by accounting for the different approaches to encoded output on sys.stdout in Python 2 and Python 3 when opening the `out` filehandle for the first time. Bug report: #3
Fixed in abe0f26. This is the basis for the new release 0.2.3. |
mkdocs2pandoc gives no output an no error message.
Would be great, if you could add some logging, possibly a '-v' switch
No output...
The text was updated successfully, but these errors were encountered: