8000 Stack trace when following instructions on website · Issue #106 · avelino/liquidluck · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jun 4, 2021. It is now read-only.
This repository was archived by the owner on Jun 4, 2021. It is now read-only.
Stack trace when following instructions on website #106
Closed
@jml

Description

@jml

I just wanted to try out liquidluck, so I followed the instructions on the website, setting up a virtualenv, installing it, and so forth.

When I did, I got a stack trace:

Traceback (most recent call last):
  File "/private/tmp/liquidluck-crash/.env/bin/liquidluck", line 8, in <module>
    load_entry_point('liquidluck==3.8', 'console_scripts', 'liquidluck')()
  File "/private/tmp/liquidluck-crash/.env/lib/python2.7/site-packages/liquidluck/cli.py", line 153, in main
    generator.build(arg_settings, arg_output)
  File "/private/tmp/liquidluck-crash/.env/lib/python2.7/site-packages/liquidluck/generator.py", line 157, in build
    write_posts()
  File "/private/tmp/liquidluck-crash/.env/lib/python2.7/site-packages/liquidluck/generator.py", line 146, in write_posts
    writer.run()
  File "/private/tmp/liquidluck-crash/.env/lib/python2.7/site-packages/liquidluck/writers/base.py", line 44, in run
    raise e
TypeError: expected string or buffer

Possibly related to https://github.com/lepture/liquidluck/issues/100. The reporter there said that it was a Jinja2 bug that has since been fixed: pallets/jinja#236. However, that was fixed three months ago, and the last release of Jinja2 was three weeks ago.

Full log coming soon. There's a bunch of compiler warnings, but my guess is that they're not relevant.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0