Skip to content

make sure we use our resource to get interpreter details #11474

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.

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

Conversation

IanMatthewHuff
Copy link
Member

For #11469

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
  • Title summarizes what is changing.
  • Has a news entry file (remember to thank yourself!).
  • Appropriate comments and documentation strings in the code.
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated.
  • Test plan is updated as appropriate.
  • package-lock.json has been regenerated by running npm install (if dependencies have changed).
  • The wiki is updated with any design decisions/details.

@@ -76,7 +76,7 @@ export class PythonExecutionFactory implements IPythonExecutionFactory {
const interpreterService = this.serviceContainer.get<IInterpreterService>(IInterpreterService);
const logger = this.serviceContainer.get<IProcessLogger>(IProcessLogger);

const interpreter = await interpreterService.getInterpreterDetails(pythonPath);
const interpreter = await interpreterService.getInterpreterDetails(pythonPath, options.resource);
Copy link
Member Author

@IanMatthewHuff IanMatthewHuff Apr 28, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per discussion on teams I think this is the change we need. This should cover cases where the full pythonPath is specified in the spec, and if it's just "python" it will use the resource to calculate the interpreter.

Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🕐

Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@codecov-io
Copy link

codecov-io commented Apr 28, 2020

Codecov Report

Merging #11474 into master will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #11474      +/-   ##
==========================================
- Coverage   60.61%   60.60%   -0.02%     
==========================================
  Files         612      612              
  Lines       33472    33472              
  Branches     4719     4719              
==========================================
- Hits        20290    20285       -5     
- Misses      12731    12735       +4     
- Partials      451      452       +1     
Impacted Files Coverage Δ
...client/datascience/kernel-launcher/kernelFinder.ts 61.26% <ø> (ø)
...rc/client/common/process/pythonExecutionFactory.ts 87.25% <100.00%> (+0.98%) ⬆️
src/datascience-ui/react-common/arePathsSame.ts 75.00% <0.00%> (-12.50%) ⬇️
src/client/common/utils/platform.ts 64.70% <0.00%> (-11.77%) ⬇️
src/client/linters/pydocstyle.ts 86.66% <0.00%> (-2.23%) ⬇️
src/client/datascience/debugLocationTracker.ts 76.56% <0.00%> (-1.57%) ⬇️
src/client/common/process/proc.ts 14.49% <0.00%> (-0.73%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6218433...8e57daf. Read the comment docs.

@IanMatthewHuff IanMatthewHuff merged commit 29e9695 into microsoft:master Apr 28, 2020
@IanMatthewHuff IanMatthewHuff deleted the dev/ianhu/useInterpreterForLaunch branch April 28, 2020 20:44
@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants