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.

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

Log env info when the existence of pipenv cannot be determined #1962

Merged
merged 1 commit into from
Jun 14, 2018

Conversation

DonJayamanne
Copy link

Fixes #1338

This pull request:

  • Has a title summarizes what is changing
  • Includes a news entry file (remember to thank yourself!)
  • Has unit tests & code coverage is not adversely affected (within reason)
  • Works on all actively maintained versions of Python (e.g. Python 2.7 & the latest Python 3 release)
  • Works on Windows 10, macOS, and Linux (e.g. considered file system case-sensitivity)

Copy link

@d3r3kk d3r3kk left a comment

Choose a reason for hiding this comment

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

Should be just fine, but I made a comment re: Windows OS.

const platformService = this.serviceContainer.get<IPlatformService>(IPlatformService);
const currentProc = this.serviceContainer.get<ICurrentProcess>(ICurrentProcess);
const enviromentVariableValues = {
LC_ALL: currentProc.env.LC_ALL,
Copy link

Choose a reason for hiding this comment

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

Are these variables defined in the Windows environment? I'm used to seeing them in Linux (and presume that macOS shares these), but I don't remember seeing them in Windows...

Copy link
Author

Choose a reason for hiding this comment

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

Documented here http://click.pocoo.org/5/python3
Required by one of the dependencies of pipenv

@DonJayamanne DonJayamanne merged commit a93ce84 into microsoft:master Jun 14, 2018
@DonJayamanne DonJayamanne deleted the issue1338LogEnvInfo branch June 20, 2018 03:13
@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
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.

Log the user's environment when the attempt to execute pipenv returns ENOENT
2 participants