pythondavidhalter/jedi #1348Not a task: already works

Jedi's install_requires claims it works with old parso, but this doesn't appear to be true

envgap__davidhalter__jedi-1348

Original GitHub issue ↗Dated source checkout ↗Opened 2019-06-21

01 / FAILURE SIGNATURE

As reported upstream

E   ImportError: cannot import name 'SyncCompFor' from 'parso.python.tree' (/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/parso/python/tree.py)

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 454447d422c9d832db03dff118bafc21174ecb55
Manifest: requirements.txt
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

davidhalter/jedi #1348 · read the original issue

According to jedi's `install_requires`, all it needs is `parso >= 0.3.0`.



But judging from https://github.com/python-trio/trio/pull/1121, it looks like actually even parse 0.4.0 isn't good enough – we get:



```

>   from parso.python.tree import ExprStmt, SyncCompFor

E   ImportError: cannot import name 'SyncCompFor' from 'parso.python.tree' (/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/parso/python/tree.py)

```



So I guess the `install_requires` should be updated to say `parse >= 0.5.0`.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]