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

Running steamctl on Windows errors due to SIGPIPE not existing #3

Closed
DMzda opened this issue Aug 15, 2019 · 1 comment · Fixed by #4
Closed

Running steamctl on Windows errors due to SIGPIPE not existing #3

DMzda opened this issue Aug 15, 2019 · 1 comment · Fixed by #4
Labels
bug Something isn't working

Comments

@DMzda
Copy link
Contributor

DMzda commented Aug 15, 2019

Using python 3.7.3 64bit on Windows 10.

The full error:

> steamctl
Traceback (most recent call last):
  File "c:\users\mazin\appdata\local\programs\python\python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\mazin\appdata\local\programs\python\python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\mazin\AppData\Local\Programs\Python\Python37\Scripts\steamctl.exe\__main__.py", line 5, in <module>
  File "c:\users\mazin\appdata\local\programs\python\python37\lib\site-packages\steamctl\__main__.py", line 4, in <module>
    from signal import signal, SIGPIPE, SIG_DFL
ImportError: cannot import name 'SIGPIPE' from 'signal' (c:\users\mazin\appdata\local\programs\python\python37\lib\signal.py)

From the docs:

On Windows, signal() can only be called with SIGABRT, SIGFPE, SIGILL, SIGINT, SIGSEGV, SIGTERM, or SIGBREAK. A ValueError will be raised in any other case.

so I assume those are the only signals that exist on Windows.

@rossengeorgiev rossengeorgiev added the bug Something isn't working label Aug 15, 2019
@rossengeorgiev
Copy link
Collaborator

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants