Paul Moore

[Paul Moore @pf_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?

[Paul Moore @pf_moore]

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

[Paul Moore @pf_moore]

@brianokken @fredrikaverpil @willmcgugan @mkennedy I got a https://t.co/n2D3uXbAbu invite, so I'm now @[email protected]. I guess I might end up with 2 accounts now... I'll fix that mess when it happens, though :-)

[Paul Moore @pf_moore]

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

[Paul Moore @pf_moore]

@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...

[Paul Moore @pf_moore]

@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.

[Paul Moore @pf_moore]

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

[Paul Moore @pf_moore]

@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...

[Paul Moore @pf_moore]

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

[Paul Moore @pf_moore]

@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...

[Paul Moore @pf_moore]

@juanluisback Switching my app to https://t.co/AHfEJpnDke took just minutes...

[Paul Moore @pf_moore]

@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.

[Paul Moore @pf_moore]

@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?

[Paul Moore @pf_moore]

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

[Paul Moore @pf_moore]

@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.

[Paul Moore @pf_moore]

@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.

[Paul Moore @pf_moore]

@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.