Python 3
See original GitHub issueIt doesn’t seem to work in Python 3. What a shame…
(env) 02:39:47 (master) /tmp/statik/examples/blog$ statik
Project path configured as: /tmp/statik/examples/blog
Error caught: name 'unicode' is not defined
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Download Python
Download the latest Python 3 source. Read more. Alternative Implementations. This site hosts the "traditional" implementation of Python (nicknamed CPython). A ...
Read more >Python 3.0 Release
Python 3.0 (a.k.a. "Python 3000" or "Py3k") is a new version of the language that is incompatible with the 2.x line of releases....
Read more >Welcome to Python.org
The official home of the Python Programming Language. ... 3.10.9, 3.9.16, 3.8.16, 3.7.16, and 3.12.0 alpha 3 are now available; 2022-11-23 Where is...
Read more >3.11.1 Documentation
Python Setup and Usage how to use Python on different platforms. Python HOWTOs in-depth documents on specific topics. Installing Python Modules
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I simply tried to build the example blog with Python 3.6 (also tried 3.5), and it doesn’t work:
Because of the
name 'unicode' is not definedpart I thought it was because the code wasn’t prepared to run in Python 3, because in Python 3 there is nounicodetype, that only exists in Python 2.As a side note, I don’t like the
Error caught: name 'unicode' is not definedhandling at all. You shouldn’t hide Python tracebacks, that is an anti-pattern: now I’m not even able to debug where this error comes from…No worries. I realised I didn’t actually have a
requirements.txtin the repo for the blog example, so I just added it today. And apologies for the difficulty in debugging! Hope it’s easier from now on 😁