If you want to do web requests/ use API’s, use ‘requests’

graphs/reporting, I’ve used ‘bokeh’ before, it was nice.

I’ve never used PyDroid, so I’m not sure how you’d install things, but these are both available via pypi, python’s package repository.

haha no source, just a dumb joke.

Japan: Checkmate

:: Reveals 10X more laws regulating game consoles ::

I know, I know, it’s pronounced “Nyïmp”

Full name is GNUIMP anyway

In the U.S., you can build rockets all day long, they cannot be guided.

https://www.law.cornell.edu/uscode/text/18/2332g

You’d have to convince the feds it was never designed to be a weapon. Good luck with that.

Exactly! You actually CAN have 50 people finish something 50x faster, but it takes a shitload of planning, and that equals time and money no company I have ever worked for, or even known of, would allocate to something that isn’t generating immediate income.

Take the Hoover Dam for example: Dsigned over 3 ish years and built in 5, at a time when nothing that huge had ever been made before, at less than a billion in today money, and 2 years ahead of schedule. It’s 90 years old.

If you’re worried about the veracity of the claims, I can assure you they’re true.

Yes, you need to push back on those people. They’re the type that get high on code golf and end up writing unmaintainable one-liners measured in kilobytes for fun.

JavaScript: :wide eyed and smiling: Sure why not! You’re the boss!

Python: Sighing and downing half a bottle of Advil: Sure. Why not, you’re the boss.

The scripting language formerly known as Java.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

Unsolicited fact: Heinz picked the number 57 at random, it just sounded like good marketing at a time when things were general marketed as “tonic #4” and the like.

(well, maybe not fact, more like probable truth)

That’s why the cat is smug. It knows you know this.

Good for Ozempic for making something that works and (hopefully) doesn’t cook you alive like those meth diet pills used to in the 80’s.

Distributed Honor-system Clothes Peg Server

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

I see a dark room of shady, hoody-wearing, code-projected-on-their-faces, typing-on-two-keyboards-at-once 90’s movie style hackers. The tables are littered with empty energy drink cans and empty pill bottles.

A man walks in. Smoking a thin cigarette, covered in tattoos and dressed in the flashiest interpretation of “Yakuza Gangster” imaginable, he grunts with disgust and mutters something in Japanese as he throws the cigarette to the floor, grinding it into the carpet with his thousand dollar shoes.

Flipping on the lights with an angry flourish, he yells at the room to gather for standup.

It’s not uncommon to keep example bad data around for regression to run against, and I imagine that’s not the only example in a compression library, but I’d definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.