Theodore Georgomanolis theodore86

cave! `–` becomes often a single hyphen. Please be aware. (You see - it is actually a double hyphen :P).

Replaces: pyenv	Purpose	Command
	Install a specific Python version	uv python install <version>
	List available Python versions	uv python list
	Use a specific Python version in a project	uv python use <version>
	Automatically install the required Python version	uv run –python <version> script.py
	Pin the Python version for a project	uv python pin

Inspired By: grafana/loki#333

docker-compose.yml

version: "3"

networks:
  loki:

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.

Turns out, however, you can define fixtures in individual files like this:

tests/fixtures/add.py

import pytest

@pytest.fixture

	import os
	import sys
	import time
	import signal
	from multiprocessing import Pool

	def int_handler(signum, frame):
	print('(%s) int_handler' % os.getpid())
	raise KeyboardInterrupt()