print() doesn't output anything/sys.stdout is None

[Ayuto]

Some people have reported that the print function doesn't output anything. The reason for this is that sys.stdout is None.

I don't know why this happens, but this issue should be used to gather information about it.

Where did this issue occur so far?

• Windows 10 (TF2, CS:S, CS:GO)

What I have tested so far (without being able to reproduce the issue):

• Windows 7 (Blade, BM:S, CS:GO, CS:S, GMod, L4D2)
• Windows 10 (Freshly installed VM) (CS:S)
• Ubuntu 14.04.2 (Blade, BM:S, CS:GO, CS:S, GMod, L4D2)

Please post all relevant information here regarding this issue.

[Frag1337]

any updates on that?

Windows traceback doesnt work either

[Ayuto]

We have added a workaround that overrides sys.stdout when it's None, so that messages are printed through console_message.

If you are pertained by this issue, you should get a warning when starting your server with the appeal to post any relevant information regarding this issue.

And no, there are no news about this issue, because nobody has posted any information.

[KirillMysnik]

I have this issue on CS:GO and now (when installed) on CS:S dedicated servers. Only after I switched to Windows 10. Never had this on Windows 7.

Just feel obliged to share because of that warning :)

[Hackmastr]

I just updated, and I got this warning, so here's my info:

Windows 10,
CSS Dedicated server.
SP May, 02, current year.

[Frag1337]

I just want to edit my first comment which included Windows traceback doesnt work. Its fixed with the latest GameThread change.

[neoncik]

SP VERSION -> "sp_version" = "578" notify - Source.Python version
OS -> Windows Server 2016 Datacenter
GAME -> CS:GO

[xArchurious]

OS: Windows-10-10.0.15063
Version: 592
Game: csgo

[jordanbriere]

Seems like sys documentation has been updated to add the following note:

Under some conditions stdin, stdout and stderr as well as the original values stdin, stdout and stderr can be None. It is usually the case for Windows GUI apps that aren’t connected to a console and Python apps started with pythonw.

[jordanbriere]

Pushed a patch that fixed it on my side: 49a5d71

@KirillMysnik @Hackmastr @Frag1337 @neoncik @xArchurious: If you guys could try updating your server(s) affected by this issue to build 747 (or later), run the following code:

import sys

print('sys.stdin =', sys.stdin)
print('sys.stdout =', sys.stdout)
print('sys.stderr =', sys.stderr)

And confirm that the streams are no longer pointing to OutputRedirect but correctly set to TextIOWrapper instances:

sys.stdin = <_io.TextIOWrapper name='CONIN$' mode='rt' encoding='utf-8'>
sys.stdout = <_io.TextIOWrapper name='CONOUT$' mode='wt' encoding='utf-8'>
sys.stderr = <_io.TextIOWrapper name='CONERR$' mode='wt' encoding='cp1252'>

It would be appreciated, thanks!

[satoon101]

@invincibleqc - It looks good on my end, same output as you have.

[xArchurious]

@invincibleqc - Yup, I got exactly the same thing!

[Ayuto]

Awesome! Also works fine for me. I guess this can be closed.