Opened 5 years ago
Closed 5 years ago
#60195 closed defect (fixed)
py-spyder: Not picking up dependency on py-parso 0.6.2
Reported by: | mf2k (Frank Schima) | Owned by: | reneeotten (Renee Otten) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | py-spyder |
Description (last modified by mf2k (Frank Schima))
When I launch the new spyder 4.1.0, I see the following message pop up in a dialog box.
You have missing dependencies! # Mandatory: parso =0.5.2 : 0.6.2 (NOK)
But it is indeed installed.
$ port installed | grep parso py37-parso @0.6.2_0 (active) $ port installed | grep spyder py37-spyder @4.1.0_0 (active) py37-spyder-kernels @1.9.0_0 (active) spyder_select @0.1_0 (active)
Change History (4)
comment:1 Changed 5 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:2 Changed 5 years ago by reneeotten (Renee Otten)
comment:3 Changed 5 years ago by reneeotten (Renee Otten)
okay, that the parso
versioning restriction is there because versions above don't work anymore with jedi
v0.14.1. Since we already patch the jedi
requirement we can do the same for parso
. Of course, this means that completions for NumPy
and Pandas
will likely not not be fully functional. I'll commit this change shortly.
comment:4 Changed 5 years ago by reneeotten (Renee Otten)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
ah, I did test
py27-spyder
and that all worked correctly and assumed, as it appears incorrectly, that it would work with all others as well. Butpy27-parso
is pinned to version 0.5.2, whereas for the PY3 it is at version 0.6.2. Apparently,py-spyder
does not like this newer version - I'll take a look and see if we can get around this.