Half fair, half outdated.
Pascal is the fairer half of the claim. Niklaus Wirth designed it explicitly to teach structured programming, and that's mostly what it's remembered for today. But it wasn't always confined to classrooms — Turbo Pascal and later Delphi (Object Pascal) powered real commercial software from the 1980s through the 2000s, including early Skype and a lot of Windows business applications. So the "limited use in production" framing is accurate now, but it undersells Pascal's actual production history.
For Python I would disagree. That description fit Python's reputation around the early 2000s, when it was seen mainly as a scripting or glue language. It doesn't fit today. Python now runs core backend services at companies like Instagram, Spotify, and Dropbox, and it's the backbone of essentially the entire machine learning and AI industry, PyTorch, TensorFlow, and the broader LLM ecosystem are all built on it, in production, not just research. It's also deeply embedded in finance, scientific computing, and infrastructure tooling.
So your point might show your age 
it’s more an historical snapshot than a general rule: it captures how people talked about these languages twenty years ago, but Python's teaching-friendliness clearly hasn't stopped it from becoming a default production language across huge parts of the industry.
To the original question, most has been said: Python simply can't compete with C and C++ for embedded and Arduino work. Python's interpreter and garbage collector need memory and processing overhead that many microcontrollers don't have to spare, a chip with 2KB of RAM can't fit a Python runtime at all, and even where it fits (like MicroPython on beefier boards), the interpreter's unpredictable pause times for garbage collection make it unsuitable for hard real-time tasks like precisely timed motor control or signal processing, where C and C++ let you know exactly how many clock cycles an operation will take.
It reminds me about Java. Embedded Java had its own shot at this world in the 1990s and 2000s , that's literally what Java was originally designed for, before it pivoted to the web, but it never took hold for similar reasons. The JVM itself needed more memory and flash storage than cheap microcontrollers offered, its garbage collector introduced the same unpredictable pauses that hurt Python, and stripped-down variants like Java ME never matched the tiny footprint and direct hardware access that C offered natively. By the time embedded systems got powerful enough to comfortably run a JVM, C and C++ already owned the ecosystem, tooling, and decades of trusted, battle-tested code, leaving Java only niche footholds rather than real displacement.