nxdefiant

x = foo(y:=bar(), baz(), y) or z should work assuming foo bar and baz are functions being called?

if this is setting y to the effect of bar() + running baz after, then:

x = [bar(), baz()][0] or z

might work

and if you need y to be defined for later use:

x = [(y:=bar()), baz()][0] or z

but thats from memory, not sure if that will even run as written.

if I get to a real computer I'll try that with an actual if statement instead of a bastardized ternary.

"a = x if foo else y" is a perfectly cromulent statement!

The "Brick through a widow" bug has been an active exploit since the Model T.

That is probably true.

1. Planting trees has far greater benefits than just carbon capture.

2. At best they're deluded, at worst its green washing with a side effect of free trees.

Enabling the PIN mitigates this issue entirely. Can't drive it away if you don't know the PIN, even if you have the physical key, fob, or phone.

Anarchism: The theory or doctrine that all forms of government are oppressive and undesirable and should be abolished.

Anarchist: Decides to wash dishes, or not wash dishes, on their own. Literally nothing else is defined in this scenario.

iPython makes experimenting in an interactive manner so easy, I use it every day.

Ah, so the kids take the good candy home from work and package the rest for sale. Bastards.

libertarian Halloween is shit!

I see what you're saying. I wasn't aware that the USDA had updated the zones, so that was news to me at least. The appsite they built is neat. It does actually drive home that this is abnormal and will continue to accelerate in the future at least.

"These things changed, here's the details" is a pretty tame headline, what's the problem?