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

Fails to find configured Python on Windows #474

Closed
1 task done
JamesMGreene opened this issue May 4, 2018 · 0 comments
Closed
1 task done

Fails to find configured Python on Windows #474

JamesMGreene opened this issue May 4, 2018 · 0 comments
Assignees
@JamesMGreene
Labels
bug

Comments

@JamesMGreene
Copy link
Member

JamesMGreene commented May 4, 2018 •
edited
Loading

This is a

  • Bug Report

If this is a bug report, What are the steps to reproduce?

If I configure the python option, nexe still fails to find the configured Python. It turns out this is an issue with the way the process.env object is being replicated in "compiler.ts" because, while part of the process.env object, the properties are treated caseless-ly (like when using the caseless module) but once they are copied over to this.env, they are no longer caseless. In my case, this.env.PATH is undefined because the property name after assignment was actually this.env.Path.

// relevant snippet only:
{
   "python": "C:/python27"
}




Please also provide:

  • Platform(OS/Version): Windows 10 Enterprise x64
  • Host Node Version: 8.11.1
  • Target Node Version: 4.8.3
  • Nexe version: 2.0.0-next.9
  • Python Version: 2.7.11
@JamesMGreene JamesMGreene self-assigned this May 4, 2018
@JamesMGreene JamesMGreene changed the title next/no-bundle branch: fails to find configured Python on Windows Fails to find configured Python on Windows May 4, 2018
This was referenced May 4, 2018
Closed
Merged
calebboyd pushed a commit that referenced this issue May 5, 2018
@JamesMGreene @calebboyd
fix: windows PATH setting for python configuration (#476)
34b983e 
fixes #474
calebboyd pushed a commit that referenced this issue May 5, 2018
@JamesMGreene @calebboyd
fix: windows PATH setting for pythong configuration (#476)
7629bda 
fixes #474
calebboyd pushed a commit that referenced this issue May 5, 2018
@JamesMGreene @calebboyd
fix: windows PATH setting for python configuration (#476)
e65ce4d 
fixes #474
@JamesMGreene JamesMGreene mentioned this issue May 8, 2018
Merged
calebboyd pushed a commit that referenced this issue May 8, 2018
@JamesMGreene @calebboyd
fix: case-sensitive windows PATH setting for python configuration (#481)
24c0b6b 
fixes #474
amends #476

related to nodejs/node#20605
uzdry pushed a commit to uzdry/nexe that referenced this issue Feb 28, 2020
@JamesMGreene @calebboyd
fix: windows PATH setting for python configuration (nexe#476)
8ec3029 
fixes nexe#474
uzdry pushed a commit to uzdry/nexe that referenced this issue Feb 28, 2020
@JamesMGreene @calebboyd
fix: case-sensitive windows PATH setting for python configuration (ne…
a08ebfa 
…xe#481)

fixes nexe#474
amends nexe#476

related to nodejs/node#20605
nevilm-lt pushed a commit to nevilm-lt/nexe-test that referenced this issue Feb 8, 2022
@JamesMGreene @nevilm-lt
fix: windows PATH setting for python configuration (nexe#476)
636886f 
fixes nexe#474
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JamesMGreene JamesMGreene

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JamesMGreene