Rename datascience to datascience_modules#10525
Conversation
DonJayamanne
left a comment
There was a problem hiding this comment.
Some parts of the python code need to be changed as well,
Might want to do a search for datascience.daemon.
|
I think that our chance of collision is now way lower. But my vote here would be that we have something either Microsoft or vscode specific in the name. "datascience_modules" still doesn't seem outside of the realm of possibility for someone to want to have their own module of. I think something like "vscode_datascience" or "vscode_datascience_modules" or "vscode_python_extension" is safer, but I'm not sure if that's just too much caution. |
|
I agree with @IanMatthewHuff |
IanMatthewHuff
left a comment
There was a problem hiding this comment.
More specific name from "datascience_modules"
|
Kudos, SonarCloud Quality Gate passed!
|
Codecov Report
@@ Coverage Diff @@
## master #10525 +/- ##
==========================================
- Coverage 60.81% 60.79% -0.02%
==========================================
Files 578 578
Lines 31288 31288
Branches 4451 4451
==========================================
- Hits 19029 19023 -6
- Misses 11295 11299 +4
- Partials 964 966 +2
Continue to review full report at Codecov.
|
* Rename datascience to datascience_modules * Change name to something even harder to get wrong
* master: Fix flakey file system tests (#10541) Tweaks for gather (#10532) Fix #10437: Update launch.json handling to support "listen" and "connect" (#10517) Add conda support to nightly flake test (#10523) Rename datascience to datascience_modules (#10525) Clean up the extension activation code. (#10455) Allow escape and ctrl+U to clear the interactive window (#10513) Fix builtins so they don't interfere with our execution (#10511) Jupyter autocompletion will only show up on empty lines, (#10420) notify on missing kernel and interpreter with kernel (#10508)
Seems there's a popular module called 'datascience' already.
This should fix this bug here:
microsoft/vscode#92511