Honestly I wouldn't recommend trying to use Django on Jython (I'd be amazed if it all works), or really doing anything on either Jython or JRuby unless you're already familiar with all of the pieces. To understand and debug Jython properly you need a good understanding of both Python and Java. For a first JVM project, find something good and idiomatic in Java (I hear good things about Dropwizard) and use that.
So I'm guessing it should work fine and the comment above is probably too pessimistic about the situation.
JRuby, IIRC, hasn't been particularly faster than MRI since MRI 1.9-ish, though it still has the advantage of no GVL for multithreaded apps.
I just want to see how this works if django-jython wokrs at all.
There's also ZipPy, a Python 3 implementation based on Truffle/Graal. In some benchmarks, it far out-performs even PyPy, but it's very much incomplete so it's hard to make general conclusions as many (most?) larger benchmarks don't run.
JRuby has Charles Nutter. No disrespect to Frank, but Nutter has really been a champion for dynamic langauges on the JVM, out in front, pushing all the time (JEP-191).
Thanks for the detail.
Now, with that in mind, I heard a long time ago, and it might be utter BS that Jython is way behind JRuby in terms of community, and very fairly, not as performant or robust bc there are only so many eyes for shallow bugs. Is this true? I see geovizer and others are making use of it, but others using it to good effect and it is worth their while?
I am now studying Java academically, and played with Python for years. The idea of doing Django-REST-Framework on Jython instead of learning Rails-API for JRuby as trial by fire exercise, at least in my mind, is more appealing. So anyone know how realistic this is?