Den 2017-10-29 skrev Chris Warrick <kwpol...@gmail.com>: > On 28 October 2017 at 22:41, Martin Schöön <martin.sch...@gmail.com> wrote: <snip> >> >> Could mixing pip installs with Debian distro installs of Python >> packages lead to conflicts or other problems? > > Yes, it does, you should avoid that at all cost. The best way to do it > is by using virtualenv. > OK. Python virtualenv is new to me. > > Now, onto fixing Nikola issues: > > As discussed on IRC, Nikola recommends (and will soon require) Python > 3. And you’ll be better off with a virtualenv: install `virtualenv` > from apt and follow the Getting started guide for Nikola: > https://getnikola.com/getting-started.html > I have installed Python 3 virtualenv and Nikola according to those instructions. I now have a working Nikola but I sure don't know what I am doing :-) How do I get back into that nikola python environment next time?
I guess I need to do some reading. > If you still get unicode issues when compiling posts, make sure > they’re saved as UTF-8, and that your locale is configured properly: > https://chriswarrick.com/blog/2017/06/18/unix-locales-vs-unicode/ > The problem with locale went away when I changed DEFAULT_LANG from en to sv in conf.py. pip list still throws exceptions at me but I have a plan. My secondary computer has a very similar Debian installation. There are no Python issues on that machine so I will do some comparative research. Most gratefully, /Martin -- https://mail.python.org/mailman/listinfo/python-list