Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEA] Missing IntelliSense capability in VSCode #489

Closed
alexkrz opened this issue Jan 26, 2023 · 1 comment · Fixed by #575
Closed

[FEA] Missing IntelliSense capability in VSCode #489

alexkrz opened this issue Jan 26, 2023 · 1 comment · Fixed by #575
Labels
feature request New feature or request
Milestone
v23.04.00

Comments

@alexkrz
Copy link

alexkrz commented Jan 26, 2023 •
edited
Loading

Is your feature request related to a problem? Please describe.
After installing cucim, unfortunately I cannot get IntelliSense features like auto-complete in Visual Studio Code. According to microsoft/pylance-release#242 this is due to the fact that the Pylance extension does not support IntelliSense for compiled libraries.

Describe the solution you'd like
As described in microsoft/pylance-release#242 it would be necessary to provide a type stub ("pyi") file for the library interface.
I would very much appreciate if such a type stub file could be provided.

Describe alternatives you've considered
Interestingly, IntelliSense features are working for me in PyCharm. Haven't figured out the reason why PyCharm can auto-generate the type stubs and VSCode can't..
@alexkrz alexkrz added the feature request New feature or request label Jan 26, 2023
@grlee77
Copy link
Contributor

grlee77 commented Feb 7, 2023

Thanks, @alexkrz. The use of .pyi files was introduced in recent months to scikit-image and should appear in the 0.20 release.

Let me update to use .pyi files here as well (port changes from scikit-image/scikit-image#6577). I will target this for the 2023.04.00 milestone.

@grlee77 grlee77 added this to the v23.04.00 milestone Feb 7, 2023
@grlee77 grlee77 mentioned this issue Jun 19, 2023
Merged
@rapids-bot rapids-bot bot closed this as completed in #575 Jul 26, 2023
rapids-bot bot pushed a commit that referenced this issue Jul 26, 2023
@grlee77
switch from bundled lazy loading code to the public lazy_loader packa…
f8e9b38 
…ge (#575)

This PR switch from using the internally bundled `_shared/lazy.py` to the public [lazy_loader](https://github.com/scientific-python/lazy_loader) package. 

Also switches to use `.pyi` [stub files](https://mypy.readthedocs.io/en/stable/stubs.html) in cases where submodules or attributes were being dynamically loaded.

closes #489  (probably, but have not yet verified from VS Code)

Authors:
  - Gregory Lee (https://github.com/grlee77)
  - https://github.com/jakirkham

Approvers:
  - Gigon Bae (https://github.com/gigony)
  - https://github.com/jakirkham
  - Ray Douglass (https://github.com/raydouglass)

URL: #575
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request
Projects
None yet
Milestone
v23.04.00
Development

Successfully merging a pull request may close this issue.

switch from bundled lazy loading code to the public lazy_loader package grlee77/cucim
2 participants
@grlee77 @alexkrz