I am starting to believe that software has a shelf life. Some of its fresh fruit and milk and some of it is canned beans that will survive for a long time. An answer to technical debt is throw out software
The Build HAT is not compatible with LEGO Mindstorms (EV3) because the plug system is different. The Build HAT/SPIKE™ Prime system uses LPF2 plugs whereas the Mindstorms system uses RJ12 plugs.
Duplo is Lego-compatible. A 2x4 Lego brick fits exactly onto 1x2 Duplo studs. A Duplo brick is 2x the height of a Lego brick, and a Duplo plate is 1x the height of a Lego brick.
It's fun to build large structures quickly with Duplo then detail them with Lego!
Oh cool, never knew about that one. I do have one more to add but it's mostly technics warmed over, which is 'Znap', clearly aimed at the same market as 'Knex', which Lego at some point saw as a competitor. Since then they've come their senses, the Znap line was ugly and highly impopular, leading to being discontinued after only a year.
What if I told you there is another plug type, that might still be sold with some old sets somewhere, and is still supported by a bunch of third party hubs (that for a long time were more advanced in many ways than Lego's own system ...)
Lego's stewardship of all this was a mess, and I'm super glad they open the system to officially blessed third parties.
Pynguin executes the module under test! As a consequence, depending on what code is in that module, running Pynguin can cause serious harm to your computer, for example, wipe your entire hard disk! We recommend running Pynguin in an isolated environment, for example, a Docker container, to minimise the risk of damaging your system.
This warning quoted from the README doesn't seem to suggest anything unexpected or unusual. Obviously running the tests would execute the module under test.
(Although I suppose if someone wanted to generate tests without ever executing them the warning would be relevant.)
Was anyone thinking it would "break" their computer just generating the tests? I would have though that only such a thing could happen later particularly if your python code was doing a bunch of file related stuff.
You’re confusing loading the module vs executing every method inside. I would not expect loading a module that has dangerous methods to do the destructive thing by default.
I admit to being surprised by that ... I assumed it generated tests (you know, like it says) that I could then inspect those tests and run. If you know how it works, then of course it is creating tests by running the code.