2026-01-21T06:46:13Z https://yabu.me James C :python: https://yabu.me/npub17kflek2ggdy9wxzwr09s4xafepwdvml7m5qqed3z93qtdmwjd80seasv7s https://cdn.fosstodon.org/accounts/avatars/109/523/292/949/311/053/original/0214d692bbdcc110.jpg https://cdn.fosstodon.org/accounts/avatars/109/523/292/949/311/053/original/0214d692bbdcc110.jpg https://yabu.me/nevent1qqsyw0jarqdmc99p42e26ay05yqlhxsqx6ktyc2wlgtyq40x8dwcpyqzyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a7hujhda In reply to <a href='/nevent1qqsyky6jcwwr4zpmkk0gpsjcu0nk4zf5jarlmk885e4q6srh9gveqvskv8xu9'>nevent1q…8xu9</a><br/>_________________________<br/><br/>lol! TBH it’s been a revelation. I’ve found machines that are cabled in can do 90Mbps but WiFi to WiFi is on 20Mbps for some routes. I thought the slowness was SSH overhead, but actually the pipe is just &#34;thin&#34;.<br/><br/>Am well jelly of your gigajiga bits though! 😍 2025-04-14T07:25:51Z https://yabu.me/nevent1qqsd3gmaqmuz4jhyp3cngl9cjjcp9qsr65nmys8futr6k0lms7zs6hszyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a7mr2kts Have been using iperf3 to measure max data transfer between homelab machines and have come to the expected decision that...<br/><br/>Wifi is poop 💩 <br/><br/>I&#39;m about to embark on wiring everything into a managed switch and for this I completely blame <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub19c6auv30z46ms6wxqe23kk209hmf3pkufu6q27peuuqv6j7weazss0ttya" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Wimpy</span> (<span class="italic">npub19c6…ttya</span>)</a></span> 😉 who &#34;made me&#34; do this in Episode 52: <a href="https://linuxmatters.sh/52/">https://linuxmatters.sh/52/</a> 2025-04-08T19:50:50Z https://yabu.me/nevent1qqs0h0jll9an6wapcs3lxadrn2f3t08x72n8n0mvn8a5qse6qfv8jfszyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a7wkhsck In reply to <a href='/nevent1qqstgnggdfkpm82teukfxuwd593evc80kmdqkyhlrr52ylzkd8aytsgj42jym'>nevent1q…2jym</a><br/>_________________________<br/><br/>Oh nice spot - that’s exactly the kind of thing I was thinking would benefit from being wrapped in a PyPI package that can call uv and parse its output.<br/><br/>If, instead, many Python devs of &#34;uv aware&#34; projects are doing `subprocess.run()` and then parse the result, that doesn’t seem very stable or efficient.<br/><br/>This kind of thing in that file you linked: <a href="https://github.com/modelcontextprotocol/create-python-server/blob/b07744de4f10e92cfd1a98b51f7aac8ee5805d69/src/create_mcp_server/__init__.py#L31">https://github.com/modelcontextprotocol/create-python-server/blob/b07744de4f10e92cfd1a98b51f7aac8ee5805d69/src/create_mcp_server/__init__.py#L31</a> 2024-12-03T12:59:19Z https://yabu.me/nevent1qqsx92u0qtf90m7v0q0fzy6r7mmjexrkmg8l5qyw3m5t08d08du2cfqzyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a76fxwf8 The issue of creating an interface for Python code to call uv is one of the most interesting features of this new tooling that I&#39;ve run into so far: <a href="https://github.com/astral-sh/uv/issues/3190">https://github.com/astral-sh/uv/issues/3190</a><br/><br/>#uv #Python 2024-12-02T23:22:08Z https://yabu.me/nevent1qqsvx9dwx5sdjr7glmjvf03dd28kprafsplm79fg4nuwc0ytc2q5vnczyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a7xptd3s In reply to <a href='/nevent1qqs8s520zd9purgv7pe3qvwxnlx3w0ayvcwdqyyutty22qerysrvjyqpmdkva'>nevent1q…dkva</a><br/>_________________________<br/><br/>We&#39;re still on GNU Make, but what I&#39;m loving about the uv workflow is that &#34;less technical&#34; users of our docs repository can:<br/><br/>* Have uv installed (homebrew, etc)<br/>* Clone the docs repo.<br/>* Make edits, changes, new branches etc.<br/>* Run `make lint` to get green before pushing for PR.<br/><br/>No more venv battles for them, no &#34;where did you get Python from?&#34;, is the &#34;venv&#34; active?<br/><br/>Under the hood the &#39;lint&#39; recipe is using `uv run ...` and it all _should_ Just Work ™️ 🙏 2024-09-12T14:44:39Z https://yabu.me/nevent1qqsd3y78x88v7rq942agna9kq6vcz4z243hdu7drjx6g4ak7kmqx5rczyr6e8lxefpp5s4ccfcdukz5m48y9e4n0lmwsqr9kygkypdhd6f5a7nfcts8 Am experimenting with uv on work projects - they are private Python projects inside Git repositories which multiple developers work on locally and BuildKite runs CI for.<br/><br/>Current confusion - there seem to be multiple places to set the version of Python to be used in the project:<br/><br/>- &#34;.python-version&#34; file<br/>- &#34;pyproject.toml&#34; file in the `requires-python` key.<br/>- In the `UV_PYTHON` environment variable.<br/><br/>Has anyone developed any convention or priority for these (or others) yet? 🤔 <br/><br/>#Python #uv 2024-09-12T12:23:35Z