Vendor inspect.getcallargs for Jython 2.7 support

[anonymous]

inspect.getcallargs is not available in Jython 2.7. I'm shure this is something that should be fixed in Jython too, a workaround in Django would be easy to implement and has no drawbacks to the standard CPython implementation.

[Andreas Stocker]

Patch available here: ​https://github.com/django/django/pull/2983

[Tim Graham]

How do you run Django on Jython lately? ​This is latest status I could find: "As of January 2014, the latest release of django-jython supports Django 1.3 which is no longer supported (receiving fixes or security updates) by the Django Project. We therefore recommend that you do not try to run Django on Jython at this time." I authored that text, so we'd welcome a documentation update if there's a new way to do it.

[Andreas Stocker]

I've created a new branch in the django-jython Repository (​https://code.google.com/p/django-jython/source/browse/?name=1.7.X) where I try to port the database backends Django offers to a thin zxJDBC layer. Currently I'm the only person who works on django-jython, and I'm doing it very sporadicaly. So the projekt IS seeking contributors!

The latest revision on the default branch is working with Django 1.4 - at least the PostgreSQL and MS-SQL backends do. But we never made it to a release (as the other backends are untested and are quite certainly not working).

[Tim Graham]

Thanks for the update. Do you know if there is a Jython bug we can track? If we make this change, I'd want to remove it as soon as possible.

[loic84]

It's used in a few more places, so I don't think we want to go down the road of nested imports, since it's pure python we could vendor it however.

[Andreas Stocker]

I've opened a ticket on Jython's bugtracker: ​http://bugs.jython.org/issue2184

[Tim Graham]

Per the ticket above, it looks like this will be address in Jython and there's a temporary workaround for django-jython so I suggest we not do this.