-
- Remember pipx installs packages (usually applications) but provides environment isolation as well. https://github.com/pypa/pipx
- Got the following error:
ModuleNotFoundError: No module named 'virtualenv.seed.via_app_data'
- This is due to have two virtualenv installations. One on the system level (apt) and one on the python level (pip). I uninstalled both and force reinstalled with pip, their preferred mechanism.
- All you need to install venv is a python interpreter. So you can do it with pipx (isolated, many, whatever) – or you can do it with the global python (global pip).
- Installed poetry and migrated a few of my packages to it. Added to bash completions.
- Reperformed on mac, zsh configuration, poetry installer needed path addition, fought multiple system pythons so coerced with pyenv (just like nvm or nodeenv, manages multiple system versions) to 3.8.
- Winglevoss getting mad at Silbert (gemini vs genesis) for stalling: https://twitter.com/cameron/status/1609913051427524608. DCG owes genesis $1.675B, and genesis owes gemini. Basically claiming that genesis took user funds and used it for: buybacks, ventures, and NAV trades. Just took that AUM and was risky with, ghosted, then stalled. Tale as old as time.
- Updated sbsc banner. Sent note to league about points for the bills/bengals tragedy. Scored as push for now.
- If rescheduled, we’ll just retain the original picks. Easy.
- If ultimately cancelled, then we have 2 options: leave it as push or move the wager to a future event.
- If this happened week 18, we’d have no future events, so we’d have to do the former and leave it as a push (certainly fairer than 0 points, an explicit penalty in a 50/50 game).
- But since it happened in week 17, we can allow the bills/bengals pickers to leave the 4 in week 17 and submit 6 in week 18 while the rest of the league does the usual 5 in both.
- Tons of private work.
- The general sentiment of “don’t share the hamlin video” on twitter is nonsensical.
- Imagine we all live in a town.
- If my best friend died of gout and someone else published a case study about it, it would make me sick to read about it. Yep.
- So I won’t read about it.
- Maybe I avoid the town square for a little bit.
- Others can still write about it. With or without my permission.
- Others can still read about it. Some for curiosity. Some for research. Some for no reason. Some to literally collect detailed minutia about what happened so that they can have context clues and/or springboards to reduce its likelihood from happening to others in the future.
- Ok, but I’m seeing the book cover all the time and it hurts? I’m not seeking it but still getting blindsided? I’m stumbling upon it when searching for other books in the library? Understandable. That’s a filtering problem. Avoid the library if you see it frequently there. Stop talking to the blabbermouth John until your wound is better healed (or forever).
- Our records (memories, media, whatever) are the charter of what has happened. Literally what has happened. That’s it. Holding this charter is not going to change the events that have already transpired. You can’t change that.
- So I’d argue: it’s not just neutral and benign to get mad at others for sharing the video. It’s detrimental in the attempt to maximize the probability of understanding the tragedy and prevent it from happening again.
- Keep sharing the video. In corners where it’s least likely to be stumbled on, in order to respect the wanderers who would hurt in seeing it again. Classify it as best you can. And learn from it. Use it as motivation to cherish your loved ones. Use it to equip your daily life with gratitude. Use it to avoid contexts of similar risk. Use it to gain respect for those you witnessed in service of the incident and its victims. Use it.
