7 ms·

Hey There! I'm trying to solve the issue of IntelliSense.. I'm building/improving Jupyter Notebooks inside VSCode: https://github.com/pavanagrawal123/VSNotebook

Hey There! I'm trying to solve the issue of IntelliSense.. I'm building/improving Jupyter Notebooks inside VSCode: https://github.com/pavanagrawal123/VSNotebooks https://github.com/pavanagrawal123/VSNotebooks . It's a fork from another extension somebody already built, but all activity is dead, so I'm starting up dev on an active fork. I'd love to hear any feedback y'all have! :) Also planning to add some nice debug features, plus hopefully integration into the inbuilt VSCode debugger!

yodon 8y ago
How do you see the idea of a vs code notebook comparing to or being different from the goals of the hydrogen editor?
- kylebarron 8y ago
  To me, my favorite part of the design of Hydrogen is that it's entirely language agnostic, and can be used with _any_ Jupyter kernel.
  - pavanagrawal123 8y ago
    I'm planning on adding better language support in a couple of weeks! Don't want to limited to Python and R
    - awake 8y ago
      One thing you may want to be aware of is that the python language server used for vscode runs pylint which performs static analysis on the code. However, Jupyter Notebook uses autocomplete by actually introspecting the variables as they are defined. This creates large differences when doing things such as selecting a column in a pandas dataframe. In jupyter if you press tab on the column name, it can autocomplete and also assumes you are getting a series, which leads to autocomplete on things like .min, .max, etc... In pylint you don't get any of this autocomplete since pylint cannot statically determine the column names so you lose the intellisense.
      - pavanagrawal123 8y ago
        yep! this is something I will be focussing on in VSNotebooks. I noticed this as a huge drawback to the current implementation, so I will be fixing it :)
- pavanagrawal123 8y ago
  I think the biggest thing for me personally is that I like VScode a lot more than Atom. Also, I'm going to be focussing more on better debugging, which AFAIK, is not heavily emphasized in hydrogen.
- pavanagrawal123 8y ago
  Better debugging is something I want to focus on in VSNotebooks. Personally, I like VSCode more than Atom, so this was one of the reasons I started working on this extension!
projectramo 8y ago
Thanks for working on this. We’re converging on the Bret Victor IDE
yodon 8y ago
Microsoft just announced an initiative like this (unfunded, community-based, likely at risk of becoming abandonware), perhaps you could combine your efforts with theirs? (The issue in their code that I'm personally most impacted by in lack of support for conda[0]) [0]https://github.com/lorenzo2897/vscode-ipe/issues/162 https://github.com/lorenzo2897/vscode-ipe/issues/162
- yodon 8y ago
  HN thread for that announcement: https://news.ycombinator.com/item?id=18346198 https://news.ycombinator.com/item?id=18346198
- pavanagrawal123 8y ago
  Fixed this in my fork :) I want to combine, but Neuron has stated they will not be accepting any PRs until December.
  - banyanrong 8y ago
    The Neuron extension is no longer in active development, because we are taking the functionalities further by building them directly into the Microsoft VS Code Python extension. We're still finishing up to get ready for the first official release, but if anyone is interested in giving it a try, the code is here: https://github.com/Microsoft/vscode-python https://github.com/Microsoft/vscode-python. Let us know what you think :)

yodon 8y ago

How do you see the idea of a vs code notebook comparing to or being different from the goals of the hydrogen editor?

kylebarron 8y ago
To me, my favorite part of the design of Hydrogen is that it's entirely language agnostic, and can be used with _any_ Jupyter kernel.
- pavanagrawal123 8y ago
  I'm planning on adding better language support in a couple of weeks! Don't want to limited to Python and R
  - awake 8y ago
    One thing you may want to be aware of is that the python language server used for vscode runs pylint which performs static analysis on the code. However, Jupyter Notebook uses autocomplete by actually introspecting the variables as they are defined. This creates large differences when doing things such as selecting a column in a pandas dataframe. In jupyter if you press tab on the column name, it can autocomplete and also assumes you are getting a series, which leads to autocomplete on things like .min, .max, etc... In pylint you don't get any of this autocomplete since pylint cannot statically determine the column names so you lose the intellisense.
    - pavanagrawal123 8y ago
      yep! this is something I will be focussing on in VSNotebooks. I noticed this as a huge drawback to the current implementation, so I will be fixing it :)
pavanagrawal123 8y ago
I think the biggest thing for me personally is that I like VScode a lot more than Atom. Also, I'm going to be focussing more on better debugging, which AFAIK, is not heavily emphasized in hydrogen.
pavanagrawal123 8y ago
Better debugging is something I want to focus on in VSNotebooks. Personally, I like VSCode more than Atom, so this was one of the reasons I started working on this extension!

projectramo 8y ago

Thanks for working on this. We’re converging on the Bret Victor IDE

yodon 8y ago

Microsoft just announced an initiative like this (unfunded, community-based, likely at risk of becoming abandonware), perhaps you could combine your efforts with theirs? (The issue in their code that I'm personally most impacted by in lack of support for conda[0]) [0]https://github.com/lorenzo2897/vscode-ipe/issues/162 https://github.com/lorenzo2897/vscode-ipe/issues/162

yodon 8y ago
HN thread for that announcement: https://news.ycombinator.com/item?id=18346198 https://news.ycombinator.com/item?id=18346198
pavanagrawal123 8y ago
Fixed this in my fork :) I want to combine, but Neuron has stated they will not be accepting any PRs until December.
- banyanrong 8y ago
  The Neuron extension is no longer in active development, because we are taking the functionalities further by building them directly into the Microsoft VS Code Python extension. We're still finishing up to get ready for the first official release, but if anyone is interested in giving it a try, the code is here: https://github.com/Microsoft/vscode-python https://github.com/Microsoft/vscode-python. Let us know what you think :)