Jedi with PyPy about jedi HOT 5 CLOSED

You can also add pypy to .travis.yml if you want. Travis supports it (although I don't know which version).

from jedi.

Yeah, I removed it once: 7c3a1c2

I plan to add it again if the travis uses a newer version (with the itertools.tee fix).

from jedi.

Could PyPy be tested again?

from jedi.

I have only recently removed pypy from the tested versions. It was tested for a long time, but allowed to fail. The problem is basically that it generated a lot of errors: https://travis-ci.org/davidhalter/jedi/jobs/277965015.

I have no idea why, but it was definitely not just working. Part of the errors are things that IPython does slightly different (like not having certain dunder methods on certain objects) and other things are probably PyPy bugs. The problem is that too many tests are failing and I would spend way too much time in the PyPy tracker. If someone wants to do that, they can feel free.

On a related note, I realized that PyPy was not really faster than CPython. Rather the contrary was the case: Python was probably like 10-20% faster. This might have changed, but I think that Jedi probably takes too many code paths to really speed it up.

I'm also not quite sure why not even parsing is faster (with parso), but maybe dealing with the stack (list.append, list.pop) is not that much faster.

from jedi.

@davidhalter thanks for the info!

from jedi.