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.

I stole one of those huge rolls from college once. It dispenses just fine on the floor.

Get medical advice from a doctor, not a green text by a person who scissored their balls off in a hospital bathroom.

This ad is literally the perfect opposite of their famous Think different ad:

We have an actual gigantic, unfeeling machine, literally crushing an effigy of the sum total of human creativity, only to proudly declare that everyone now needs to do all those things in the same, apple-approved way.

And the real irony is that’s the actual message they’re trying to get across.

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.

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.