I agree that Brython is an interesting idea - I am intrigued by it. I would love to see a real browser-based Python implementation.
And to be clear, I’m not saying that Django shouldn’t “support” it - if a case for it can be made - and that is what I’m not seeing.
My question really revolves around why Django (or more specifically and accurately, the people who volunteer their time to work on Django and improve it) should divert their efforts from Django, whether to Brython specifically, or any of the other alternatives that have been or may be developed.
I’m not sure why you think that there are a number of Django developers who are “supporting” JavaScript to the same degree that you would like to see them supporting Brython.
(Or, to be more precise, most people volunteer to work on Django because it makes something they use, better. Very few Django contributors that I know also contribute to any of the JavaScript frameworks. Their “support” of those frameworks is limited to being a user of them - and it’s not like there are hundreds of active contributors to Django to begin with.)
None of those technologies are affected by, nor directly affect, Django. It’s a separate environment with different needs, uses, and goals.
(I do have other opinions regarding the long-term viability of such projects, but that’s really a different topic with a purely personal perspective. I will repeat what I said at the top. I would love to see a real Python implementation in the browser - I’m no fan of the JavaScript language.)
Ken