drop jython support in 3.0.0?

Question

drop jython support in 3.0.0?

cjw296 opened this issue 6 years ago · 14 comments

@rbtcollins / @mfoord / @voidspace - thoughts?

We have no CI for it, so it's likely to have bit-rotted...

Answer 1 · 2019-04-30T10:28:44.000Z

Without CI we can't guarantee it. As far as I recall it was no extra work, but unless someone will test/maintain it I'm happy to drop official support. (No idea how I ended up with two GitHub users.)

Answer 2 · 2019-04-30T10:36:57.000Z

Yeah, I can't find any official or support docker images for Jython, so...

Answer 3 · 2019-04-30T11:37:40.000Z

+1 for dropping it. I've never run mock's test suite on Jython before, so I guess it may have already been broken.

Answer 4 · 2019-04-30T12:49:14.000Z

There is no straightforward to run tests in Jython from Travis like pypy as far as I have searched around. The only example was astroid that downloaded and built it themselves. They also removed it from their CI later. Jython also doesn't support Python 3 yet so I am not sure if it's worth the effort given Python 2 EoL.

pylint-dev/astroid@3591182

Answer 5 · 2019-04-30T12:50:59.000Z

Well, I'm planning to move the backport to CircleCI for various reasons, so if we had a stable, publicly maintainer docker image, that would do it.

But, as you say, if they have no Py3, then I think we're safe to drop it.

Answer 6 · 2019-05-01T07:54:01.000Z

Okay, 'tis done, ed3bc8b.

Answer 7 · 2019-05-01T10:27:18.000Z

I don't think we should drop the Jython glue; it is platform checked to not affect other interpreters and has approx 0 maintenance overhead for us. The whole point of the backport is to make current mock features more widely available.

Answer 8 · 2019-05-01T10:34:44.000Z

Anyone who needs this can use 2.0.0 though, right?

I guess my point in saying that is that we're offering a backport that is maintained; I have no idea whether the current master of the backport will blow up when used with Jython or not, and it makes me uncomfortable keeping untested code around that's an indication it might be an expectation.

Answer 9 · 2019-05-01T10:56:35.000Z

Kindof defeats the purpose of doing the backport is all. We can equally say that folk can just use the mock in their Python interpreter's stdlib. We do the backport to allow projects that use mock to use newer features without having to mandate a very latest release of CPython; to a large degree we should be driven by our users, and in this case its worth remembering that we're a second order dependency: a project with developers or deployers using Jython may depend on mock working there, without it enabling us to CI it. We'll know its broken if they report bugs, but we can't tell the difference between 'not used' or 'working fine' with the feedback systems we have in place today.

…

-Rob

Answer 10 · 2019-05-01T11:00:22.000Z

Totally agree, and if we see evidence of Jython users or Jython users complaining that things no longer work, we can very easily revert the one commit above and bring it back :-)

Answer 11 · 2019-05-01T11:01:34.000Z

Sure, I'll leave it with you; my bias is to not remove it in the first place, because then there's no interrupt to run around and un-break, but if you're up for that, all good.

Answer 12 · 2019-05-01T11:20:14.000Z

Not sure if this is the issue to discuss this but is it agreed upon to remove it in upstream unittest.mock too? I feel upstream CPython has a larger userbase. Though there are no signs of Python 3 support for Jython or CI in CPython for Jython I think removal could at the least have a NEWS entry/whatsnew/porting section entry.

Answer 13 · 2019-05-01T11:21:07.000Z

Sorry forgot to paste the merged PR link : python/cpython#13033

Answer 14 · 2019-05-01T11:23:05.000Z

The upstream one gets copied into Jython when they update their stdlib, so if its still needed at all, they'll still need it there. I see value in keeping the delta low, so yeah, removing it upstream makes sense to me too.

…

-Rob

On Wed, 1 May 2019 at 23:20, Xtreak ***@***.***> wrote: Not sure if this is the issue to discuss this but is it agreed upon to remove it in upstream unittest.mock too? I feel upstream CPython has a larger userbase. Though there are no signs of Python 3 support for Jython or CI in CPython for Jython I think removal could at the least have a NEWS entry/whatsnew/porting section entry. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#453 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADZ7XRNQTNNTFQIEEJP7KDPTF4G5ANCNFSM4HJJ4BAA> .