UnicodeDecodeError: ‘ascii’ codec can’t decode byte 0xd1 in position 1: ordinal not in range(128) (Why is this so hard??)
One of the toughest things to get right in a Python program is Unicode handling. If you’re reading this, you’re probably in the middle of discovering this the hard way.
The main reasons Unicode handling is difficult in Python is because the existing terminology is confusing, and because many cases which could be problematic are handled transparently. This prevents many people from ever having to learn what’s really going on, until suddenly they run into a brick wall when they want to handle data that contains characters outside the ASCII character set.
Parameter Extensions
- %~f1 Expand %1 to a Fully qualified path name - C:\utils\MyFile.txt
- %~d1 Expand %1 to a Drive letter only - C:
- %~p1 Expand %1 to a Path only e.g. \utils\ this includes a trailing \ which will be interpreted as an escape character by some commands.
- %~n1 Expand %1 to a file Name without file extension or path - MyFile or if only a path is present, with no trailing backslash, the last folder in that path.
- %~x1 Expand %1 to a file eXtension only - .txt
- %~s1 Change the meaning of f, n, s and x to reference the Short 8.3 name (if it exists.)
- %~1 Expand %1 removing any surrounding quotes (")
- %~a1 Display the file attributes of %1
- %~t1 Display the date/time of %1
- %~z1 Display the file size of %1
- %~$PATH:1 Search the PATH environment variable and expand %1 to the fully qualified name of the first match found.
Datum Pos No. Name Best time In lap Best speed Diff Gap Laps Comment
29.04.2021 105 423 Frank Matthieß 01:49.597 15 120.452 00:18.735 00:00.121 15 Getting warm with the bike
30.04.2021 129 423 Frank Matthieß 01:48.407 24 121.774 00:17.746 00:00.050 33 1:1 Coaching by Mario Steffen
01.05.2021 144 423 Frank Matthieß 01:46.630 24 123.804 00:15.474 00:00.013 25 Time to practice
Lap progression: 2.967 seconds
Mycroft is the world’s leading open source voice assistant. It is private by default and completely customizable.
Our software runs on many platforms—on desktop, our reference hardware, a Raspberry Pi, or your own custom hardware.
The Mycroft open source voice stack can be freely remixed, extended, and deployed anywhere. Mycroft may be used in anything from a science project to a global enterprise environment.
Mycroft is getting smarter every day. Our open source community includes thousands of contributors – improving the core technologies, creating new Voice Skills, translating the experience to new languages, and sharing their data to improve our machine learning models.
Join the diverse Mycroft Community made up of users, developers, and translators improving the experience for yourself and tens of thousands of people all over the world.
Once I was working in the software development company. It was a regular company: nothing really bad, but nothing fancy. It had the same problems as other similar companies:
Low-quality code
Unmet deadlines
Budget overflowsAnd disappointed clients as a final result.
Of course, everyone in management was eager to know, what (or “who”) was the reason. During our workday, it was quite normal to hear something like: “the project is failed because you wrote low-quality code, now the client is moving away from us”.
Did it help in any way? No. Was it pleasant to work there? No. So, once I woke up and decided that I do not want to work in this company anymore.
The ugliest part is that I was the founder of this company.
Fernverwaltung war noch nie so einfach
Intuitive, einfach zu bedienende Infrastrukturverwaltung, Fernzugriff, Skriptausführung, VPN-Ersatz und vieles mehr in einem einzigen, einfach zu bedienenden Tool
A remote desktop software, written in Rust. Works out of the box, no configuration required. Great alternative to TeamViewer and AnyDesk! You have full control of your data, with no concerns about security. You can use our rendezvous/relay server, or self-hosting, or write your own rendezvous/relay server. Download source code.
RTK2go® is a community NTRIP Caster created to allow you to publish your GNSS correction streams for others to use with their NTRIP Clients. It is built using the same Pro edition of the SNIP Caster you can find on the use-SNIP.com site. Why do we do this?, because many of the RTK2go users here end up operating a SNIP network of their own. You can also download and evaluate your own copy of SNIP® from here. It is one part of the overall simple NTRIP™ project created by SubCarrier Systems Corp. (SCSC).
Kea is open source, shared under MPL2.0 licensing. Kea is developed in the open on ISC’s GitLab; we welcome you to open issues and submit patches there. Kea runs on most Linux and Unix platforms, as well as MacOS. If you don’t want to build from our source distribution, we also provide a repository of pre-built packages for most popular operating systems.
ISC distributes and maintains TWO open source, standards-based DHCP server distributions: Kea DHCP and ISC DHCP. Kea includes all the most-requested features, is far newer, and is designed for a more modern network environment.
How is the Kea DHCP server different from the older ISC DHCP?
-
Modular Component Design, Extensible with Hooks Modules. The Kea distribution includes separate daemons for a DHCPv4 server, a DHCPv6 server, and a dynamic DNS (DDNS) module. Many optional features are enabled with dynamically-loaded “Hooks Modules,” which you need run only if you are using them. You can write your own hooks modules (in C++) or try some of the hooks we offer.
-
On-line Re-configuration with REST API Kea uses a JSON configuration file that can be modified remotely via set commands and reloaded without stopping and restarting the server, an operation that could take quite a while with ISC DHCP.
-
Designed to Integrate with Your Existing Systems. Kea allows you to separate the data from the execution environment, enabling new deployment options. Your network data - leases, host reservation definitions, and most configuration data - can be located separately from the DHCP server itself, using a Kea “backend.”
-
Web-based graphical dashboard Kea now has a graphical dashboard for monitoring multiple Kea servers. This system, called Stork, uses agents deployed on the Kea servers to relay information to a centralized management platform, providing the administrator with an easy-to-use quick view of system status and activity.
Kea supports two database backends; MySQL and PostgreSQL. Choose to store leases, host reservations, or shared configuration data in a separate database backend. Benefits of this include:
-
Integrate it more easily with your other systems - provisioning systems, IPAMS and so on - by storing critical data in a separate database.
-
Use the same hosts reservations backend for multiple DHCP servers.
-
Administer global options from a centralized configuration backend.
-
Manage large address pools in a database rather than a text file.
IDM 2011 Lauf Oscherleben
- Rundenzeit 1:27.18
- Geschwindigkeit am Bremspunkt Zeilgrade: 264km/h
- Print the certificate data to stdout:
openssl x509 -in <filename.pem> -text -noout
Check & print remote certificate
openssl s_client -connect <hostname>:<port> -showcerts
i3ipc-python is a library for controlling i3 window manager and sway. i3 users can use this library to create their own plugin scripts to customize their desktop or integrate i3 into other applications. With this library, you can query the state of the window manager, listen to events, and send commands to i3 to perform window manager actions such as focusing or closing windows.
The main entry point into the features of the library is the Connection class. This class manages a Unix socket connection to the ipc interface exposed by the window manager. By default, the Connection will attempt to connect to the running instance of i3 by using information present in the environment or the running X11 display.
I have been using the awesome window manager for 10 years. It is a tiling window manager, configurable and extendable with the Lua language. Using a general-purpose programming language to configure every aspect is a double-edged sword. Due to laziness and the apparent difficulty of adapting my configuration—about 3000 lines—to newer releases, I was stuck with the 3.4 version, whose last release is from 2013.
It was time for a rewrite. Instead, I have switched to the i3 window manager, lured by the possibility to migrate to Wayland and Sway later with minimal pain. Using an embedded interpreter for configuration is not as important to me as it was in the past: it brings both complexity and brittleness.
Network booting is cool. Once you have setup everything you can stop juggling iso images in your virtual machine configs. Instead you just kick a network boot and pick whatever you want install from the boot menu delivered by the boot server.
This article is not about the basics of setting up a boot server. The internet has tons of tutorials on how to install a tftp server and how to boot your favorite OS from tftp. This article will focus on configuring network boot for libvirt-managed virtual machines.
i3's interprocess communication (or ipc) is the interface i3wm uses to receive commands from client applications such as i3-msg. It also features a publish/subscribe mechanism for notifying interested parties of window manager events.
i3ipc-python is a Python library for controlling the window manager. This project is intended to be useful for general scripting, and for applications that interact with the window manager like status line generators, notification daemons, and window pagers.
If you have an idea for a script to extend i3wm, you can add your script to the examples folder.
For details on how to use the library, see the reference documentation.