Paul Moore

@jimalkhalili @threadreaderapp One thing I've always struggled with is the distinction between "quantum" and "classical" systems. Is the cat quantum or classical? Does opening the box somehow switch it from one to the other? Would I be a quantum system if I were really tiny?

@threadreaderapp unroll please.

Someone on Twitter asked me the other day if I could compose a tweet thread explaining the famous quantum measurement problem. Since I am off work for a few days I thought I’d take up the challenge. So, here goes: quantum measurement in 22 tweets… 1/22

@fredrikaverpil @film_girl Fosstodon.org doesn't seem to be taking sign-ups right now (either that or they just don't want me I guess :-))

Alright, what Mastodon instance are we all on? I’m on two right now and haven’t started to try to get into it because of the migration process but if I have to migrate anyway, I want to be on the best instance.

@brianokken @fredrikaverpil @willmcgugan @mkennedy I got a mastodon.social invite, so I'm now @pfmoore@mastodon.social. I guess I might end up with 2 accounts now... I'll fix that mess when it happens, though :-)

Turns out I've had a Mastodon account since 2018 and I even have a few followers. 🤷‍♂️ Follow me if you enjoy my brand of terminal shenanigans? @willmcgugan@matsodon.social Recommendations for who to follow would also be appreciated.

@DarrenJM73 @EleanorMorton Ah the smell of burning turnip...

Oh no it's the time of year when I get irrationally angry that America thinks it invented Halloween. I'm so sorry in advance.

@simonw I had to do it. Used oplop to generate a password, so I could recover it if I forgot. But I mostly remembered it. I used one password across multiple systems, though, so that arguably defeats the purpose...

Anyone been subject to a password rotation scheme where they've genuinely changed their password every X months over the course of multiple years, without using a password manager? What's that like?

@hynek The thing I struggle with is working out in my mind whether I want progress reporting or instrumentation (or if there's even a difference). Key=value is great for instrumentation, but looks weird in stdio progress messages. Something covering this would be great.

So I would love some feedback on what I’ve done with: - structlog.org/en/latest/gett… - structlog.org/en/latest/boun… Either here or ok the bug tracker.

Currently going thru structlog’s docs to bring it to 2022. It’s not like the docs r wrong but they have the wrong focus. It used to be abt “wrap anything!”; today ppl only care about “pretty console” or “stdlib”. 🧵

@willmcgugan Old fashioned or specialised. I think it's the printer's term for the symbol.

Testing Textual's keyboard example. Interesting to learn what unicode names codepoints. The official name of a slash is "solidus", which is a new one on me. I might translate that to "slash" because I don't think thats a common term. Is it??

@pradyunsg @gpshead I'd rather we got to the point where static (dependency) metadata was the norm and we could make running code for any purpose other than building a wheel from a sdist an opt-in behaviour, intended to support legacy code only...

@di_codes But will they contribute and collaborate, or will they make demands (of contributors, many of whom are not under their jurisdiction)?

@brianokken Second is incorrect but it's what I want to type. Optional needs a typing import and | None = None is too repetitive and so obscures the meaning. Sadly I often find type annotations obscure meaning rather than revealing it...

@juanluisback Switching my app to fly.io took just minutes...

@brettsky @pradyunsg In my case I have no consistent naming for anything other than .venv so no. Unless you plan on looking for pyvenv.cfg.

@pradyunsg @brettsky I assumed that too so I discounted nox/tox managed stuff. I do have other manually managed ones I use occasionally, so that's what I answered, but I'd be fine with assuming .venv was the "main" one. But isn't that what vs code does already?

@willmcgugan @brettsky I'd be more explicit with on_change_time or something like that.

@brettsky Watch methods are a bit of Textual magic. They are called when the corresponding reactive attribute is changed. Maybe “observe“ would be more apt, especially on this example

Now documenting Reactive attributes. This widget shows the number of seconds since it was started. If you knew nothing about Textual, what would you think of this code?

@zooba @willmcgugan I agree. Good type hints are often complex to catch nuances. As a result they suck as documentation. Write docs saying what types are allowed using words, not type hints.

@willmcgugan No in initial examples - if the type of something matters but isn't obvious from context, you need more explanation. No in docs - type hints are machine-readable docs, so write for humans when your audience is human. But I think I'm unpopular here 🙃

Type hints for example code in an introduction for a Python module. Yay or nay? And what about type hints for docs in general?

@willmcgugan Personally I hate videos for any sort of tutorial or explanatory content. Have them as supplementary if you must, but as links (clearly labelled as video) not inline. "Moving screenshots" are the only exception I can think of here.

Are videos in documentation a good idea or not? I can think of a bunch of pros and cons. If videos in docs aren't a good idea, how about links to external (YouTube) videos?

@dabeaz Agreed. I'd like a builtin with the sense of "untyped" rather than "any type". I know they are functionally the same, but conveying intent is important.