Lukas Juhrich lukasjuhrich

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

"Build tools for others that you want to be built for you." - Kenneth Reitz
"Simplicity is alway better than functionality." - Pieter Hintjens

Using Other Window Managers with Plasma 5.21 and systemd Startup

KDE Plasma on X offers the option to use a differnt window manager than the default KWin. This way one can use many of the integrations KDE offers, but with for example the i3 window manager to have proper tiling support. This only works on X, not on Wayland.

With Plasma 5.21 it is now possible to "boot" KDE using systemd user services; that is, KDE Plasma provides a bunch of unit files that get started atfer you login in your graphical user session. Inidividual components, such as KWin, have individual unit files, and dependencies are specified using the usual systemd relationships between units. Among other things this allows for better ressource control using automatically created CGroups.

More details here: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/47

Sadly this breaks the way one could change the window manager, that was used until now. I noticed af

	from flask import Flask as DefaultFlask

	class Flask(DefaultFlask):
	def create_jinja_environment(self):
	self.jinja_options = dict(self.jinja_options)
	if 'JINJA_CACHE_SIZE' in self.config:
	self.jinja_options['cache_size'] = self.config['JINJA_CACHE_SIZE']
	return super(Flask, self).create_jinja_environment()