I have an updated version of this on my blog here: https://chrisamico.com/blog/2023-01-14/python-setup/.
This is my recommended Python setup, as of Fall 2022. The Python landscape can be a confusing mess of overlapping tools that sometimes don't work well together. This is an effort to standardize our approach and environments.
These are the current alternatives (with links when possible):
| name: Build Android | |
| on: [push, pull_request] | |
| jobs: | |
| build: | |
| name: Build APK | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Checkout source |
| { | |
| "final_space": true, | |
| "console_title": true, | |
| "console_title_style": "folder", | |
| "blocks": [ | |
| { | |
| "type": "prompt", | |
| "alignment": "left", | |
| "horizontal_offset": 0, | |
| "vertical_offset": 0, |
use livestream_saver to download from the first segment. Can also record membership-only streams by supplying it your cookies (uses yt-dlp to download)
use ytarchive which basically does the same thing, except a bit better.
use youtube_stream_capture. You can use cookies file to get member-only streams too. Be aware that this script currently fails to download chunks as soon as the stream has ended (this might be a bug).
or use live-dl which does monitoring of streams too. This is a wrapper around streamlink and yt-dlp.
| global: | |
| scrape_interval: 5s | |
| external_labels: | |
| monitor: 'node' | |
| scrape_configs: | |
| - job_name: 'prometheus' | |
| static_configs: | |
| - targets: ['192.168.68.240:9292'] ## IP Address of the localhost | |
| - job_name: 'node-exporter' | |
| static_configs: |
| { | |
| "banks": [ | |
| { | |
| "id": "0156", | |
| "name": "100%BANCO" | |
| },{ | |
| "id": "0156", | |
| "name": "100%BANCO" | |
| }, | |
| { |
| // Toggleable dark mode for those of us that care about that kind of thing. | |
| const toggleButton = '<button class="sidebar__toolbar-button rc-tooltip rc-tooltip--down js-button" aria-label="Toggle Dark Mode">D</button>'; | |
| function addDarkModeToggle() { | |
| const sidebarToolbar = $('.sidebar__toolbar'); | |
| // wait for the sidebar toolbar to be visible | |
| // this will also be false if the toolbar doesn't exist yet | |
| if(!sidebarToolbar.is(':visible')) { | |
| setTimeout(addDarkModeToggle, 250); |
| # Configuration for Alacritty, the GPU enhanced terminal emulator. | |
| # Any items in the `env` entry below will be added as | |
| # environment variables. Some entries may override variables | |
| # set by alacritty itself. | |
| #env: | |
| # TERM variable | |
| # | |
| # This value is used to set the `$TERM` environment variable for | |
| # each instance of Alacritty. If it is not present, alacritty will |
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
