Improve how Jedi handles Numpy#281
Conversation
ccordoba12
left a comment
There was a problem hiding this comment.
Hey @gav451, thanks a lot for your contribution! Besides the two suggestions I left for you below, please also update our configuration file by running
python scripts/jsonschema2md.py pylsp/config/schema.json CONFIGURATION.md
4398552 to
08c14ea
Compare
|
Hey @ccordoba12, I have amended my pull request taking into account your remarks. |
|
Thanks @gav451! One last thing I forgot to mention before: could you remove the following constraint to see if our Numpy tests pass now? python-lsp-server/pyproject.toml Line 56 in 449d11a |
08c14ea to
a7cc7cb
Compare
|
Thanks @ccordoba12 for your guidance (next time I know I have to do all development steps). I checked that the Numpy test passed before amending and force-pushing. See the short test summary below: I had also to install |
No problem, thanks a lot for a great contribution!
Yeah, you need to install pylsp with to get all its dependencies for testing. |
ccordoba12
left a comment
There was a problem hiding this comment.
Looks good to me now, thanks @gav451!
The documentation of jedi.settings.auto_import_modules tells that jedi may handle numpy's module globals trickery better when importing numpy instead of parsing. The example script below prints the documentation strings of one of numpy's universal functions as well as the numpy version:
The pull request adds numpy to jedi's auto_import_modules and allows the user to modify the module list. The patch fixes:
Fixes #243.