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

Fix OSError: [WinError 193] on Windows debuggers #11034

Merged
merged 3 commits into from
Dec 10, 2017
Merged

Fix OSError: [WinError 193] on Windows debuggers #11034

merged 3 commits into from
Dec 10, 2017

Conversation

tringler
Copy link
Contributor

@tringler tringler commented Dec 8, 2017

Description:

If you are trying to debug the home-assistant code on Windows i.e. with PyCharm it will fail with this error:

Traceback (most recent call last):
  File "C:/Users/___User___/Downloads/home-assistant-dev/homeassistant/__main__.py", line 374, in <module>
    sys.exit(main())
  File "C:/Users/___User___/Downloads/home-assistant-dev/homeassistant/__main__.py", line 366, in main
    exit_code = setup_and_run_hass(config_dir, args)
  File "C:/Users/___User___/Downloads/home-assistant-dev/homeassistant/__main__.py", line 252, in setup_and_run_hass
    subprocess.check_call(nt_args)
  File "C:\Program Files\Python36\lib\subprocess.py", line 286, in check_call
    retcode = call(*popenargs, **kwargs)
  File "C:\Program Files\Python36\lib\subprocess.py", line 267, in call
    with Popen(*popenargs, **kwargs) as p:
  File "C:\Program Files\Python36\lib\subprocess.py", line 707, in __init__
    restore_signals, start_new_session)
  File "C:\Program Files\Python36\lib\subprocess.py", line 992, in _execute_child
    startupinfo)
OSError: [WinError 193] %1 ist keine zulässige Win32-Anwendung (not a valid win32-application)

Related issue (if applicable): fixes #

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>

This small change fixes that behaviour.

Example entry for configuration.yaml (if applicable):

Checklist:

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
  • New files were added to .coveragerc.

If the code does not interact with devices:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • Tests have been added to verify that the new code works.

@tringler tringler requested a review from a team as a code owner December 8, 2017 20:27
@homeassistant
Copy link
Contributor

Hi @tringler,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@emlove
Copy link
Contributor

emlove commented Dec 8, 2017

@balloob balloob merged commit 4e91e6d into home-assistant:dev Dec 10, 2017
akatrevorjay added a commit to akatrevorjay/home-assistant that referenced this pull request Dec 11, 2017
…into dev

* 'dev' of https://github.com/home-assistant/home-assistant:
  This change fixes the error `OSError: [WinError 193]` on Windows debuggers (i.e. PyCharm) (home-assistant#11034)
  Make notify.html5 depend on config (home-assistant#11052)
  Add support for Logitech UE Smart Radios. (home-assistant#10077)
@fabaff fabaff mentioned this pull request Dec 16, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants