Printing to stdout console

[Irfa_Nisar]

Hello

Is there a way to print simply to stdout on the console. I am not sure why this simple functionality is not working. I also tried using the logger, but that didn’t print either to the log. I read some posts saying that this is associated with .psyexp but I don’t quite follow why that would be so.

thanks

OS : mac sierra
PsychoPy version (e.g. 1.84.x): 2020
Standard Standalone? (y/n) No , built from scratch

[Michael]

Hello, there were some issues with stdout recently, which should have been fixed in release 2020.2.5

Are you using that latest version?

No longer receiving a message on Experiment Runner at the end (when downloaded 2020.2)

Hello everyone. I have been reading here (thanks for the community!) and this is my first post. After running an experiment on builder (offline), there always was some kind of information (warning, errors etc.) in the Experiment Runner page that shows up. Now that I downloaded the latest version (Psychopy 2020.2), there never is any kind of information. I don’t see any error message even when the experiment stopped working. Always there is this line only: ####### Running: C:\Users\zadiguzel13\…

No error messages or logging output in Stdout

On my Mac (Version 10.14.6) I get the same thing with PsychoPy 2020.2.4. Nothing except the “Running: …” message is sent to the live logging/the supposed Stdout. I tried putting some print() statements inside of a functioning experiment, but the printed messages don’t show up in Stdout either. It’s the same thing on my other PC, regardless of whether I run PsychoPy in Ubuntu (20.04) or Windows (10). Even if I try opening up an experiment’s “.py” file using the Coder View, or if I run the experim…

[Arboc]

I can report that I still get the same issue with error messages not being sent to the Coder window’s stdout feed on 2020.2.5, unfortunately. This happens on Mac OS v10.14.6, whenever I’ve opened a .psyexp file by double-clicking it, causing PsychoPy to launch and open up the file. Just like with the previous version, the PsychoPy windows aren’t shown right away either - after double-clicking the file, I have to also click PsychoPy’s dock (the bar at the bottom of the screen on Mac OS) icon for it to start up properly. It doesn’t seem to matter for how long I wait, PsychoPy’s windows don’t show up if I don’t click the Dock icon.

(many other issues seem to have been fixed with the latest release though, thanks for that )

[Irfa_Nisar]

I am at 2020.2.3.

I have built my version from scratch instead of the provided standalone. Can i merge against a git release version?

[Michael]

@Arboc

I can report that I still get the same issue with error messages not being sent to the Coder window’s stdout feed on 2020.2.5, unfortunately.

I think stdout now goes to the Runner window rather than Coder?

[Michael]

@Irfa_Nisar

I have built my version from scratch instead of the provided standalone. Can i merge against a git release version?

You can checkout a specific tagged release, as per here:

How To Checkout Git Tags – devconnected

The latest tagged release is this one:

Release Bug-fix release 2020.2.5 · psychopy/psychopy

i.e. first do this:

git fetch --all --tags

then:

git checkout tags/2020.2.5

If you plan on making any changes to the PsychoPy source code, you might want to make a new branch as well.

[Arboc]

@Michael

I think stdout now goes to the Runner window rather than Coder?

Whoops, yes, Runner window is what I meant of course. All I get is the “Running experiment” message in Stdout, then nothing, when launching psychopy by double-clicking a .psyexp file. If I open PsychoPy “directlly”, then use its own file browser (“open file…” icon) to navigate to an experiment file and run, the stdout output is as expected.

[Irfa_Nisar]

Super, thanks!

[Irfa_Nisar]

git checkout tags/2020.2.5

error: pathspec ‘tags/2020.2.5’ did not match any file(s) known to git.

I am not sure this is checked into the repo yet.