Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Inline Code Backwards Compatibility

edited May 2016 in OpenSesame

Hi All,

I just have a general question about the new (>=3.0) versions of OpenSesame. I have over the last couple years programmed many different experiments with pure python code within OpenSesame. That said, they were all created in <3.0 and I am afraid that the new versions will require many changes to the code itself.

My questions is rather general– Is it worth going back and altering all the code to make the switch to >=3.0, or am I not missing out on anything substantial?

Best,
Nate

Comments

  • edited May 2016

    Hi Nate,

    There should be almost complete backwards compatibility, with the exception of the changes listed here:

    So if an experiment suddenly stops working under version 3.0, that would be a bug, and please let us know (including details). That being said, realistically, such bugs do exist--the changes to the underlying codebase are substantial, and backwards compatibility is tricky to ensure.

    Edit: Of course, you may nevertheless want to update the code to make use of the much cleaner api of 3.0. But it shouldn't be necessary.

    Cheers,
    Sebastiaan

  • edited 2:11AM

    Sebastiaan,

    Thank you for the info! My main concern was going back and removing all the exp.set(), self.get(), and self.sleep() functions along with changing the way that variables were logged throughout all the things I have coded until now. That said, I think the change is well worth it, so I am currently working on converting everything. Thanks for your help!

    Best,
    Nate

Sign In or Register to comment.