It persists because JavaScript had always been a toy language for the front end devs to make web sites "pretty" rather than useful. Generally all of that pretty broke the site, and it was always blamed on the back end.
Node may be turning the perception of JS, but it is a slow process. Node is still very young. It's community is still highly focused on building the tooling, while the community around a more mature language like Python has long since found its voice. Right now, Node is seen as a chaotic mess for web devs that are forced to do back end work because management thinks a code monkey is a code monkey and doesn't want to pay for the vastly more expensive systems devs. (To be fair, a little start up likely doesn't have enough of a customer base to require that level of performance tuning.)
Python devs are usually seen as academics, more experienced, and very mathematically inclined. But there was a time when Python was the kiddie language because it abstracts away so many details. Now it is the majority language for machine learning, which is a very hot trend.
Once the toolsets stabilize, Node developed a robust multi-threaded model on the server, and it actually solves an engineering problem better than any other language, you may start seeing more engineers picking JS as a tool. Till then, it will just be the hip startup toy used to interest young CS grads that the companies will have to rip out later to continue scaling.