For each version below, this page lists that version’s most important changes, or any minor changes that I considered important to know about when upgrading.
Version 1.3 beta¶
Here are the main changes in 1.3 beta:
get_timeout_secondslets you set timeouts dynamically, and create timeouts that span multiple pages or rounds. See get_timeout_seconds.
get_players_for_grouplets you control how
group_by_arrival_timeassigns players to groups. See get_players_for_group()
- Bots: you can now simulate & test a page timeout. See Testing timeouts.
DEMO_PAGE_TITLEsetting added. See DEMO_PAGE_TITLE.
To install, run this (note the
--pre in the command;
this means “pre-release”):
pip install -U --pre otree-core otree resetdb
To upgrade to a newer beta release, run the same command above.
To revert back to the stable version of oTree-core:
pip uninstall otree-core pip install otree-core
Please send feedback to email@example.com.
Here are the changes in oTree-core 1.1:
Here are the main changes in 1.0:
- You can configure sessions in the admin interface
SESSION_CONFIGSparameters without changing the source code). See Configure sessions.
- Performance improvements
- The default for the
payofffield is now
None. (Make sure your code doesn’t rely on
The bot system has been overhauled, and there are some changes to the bot API. See the notes here.
Browser bots now work together with
Version 0.7 beta is available.
The main new feature is browser bots. There are also some changes to the admin UI (e.g. demo full-screen mode is now resizable).
Version 0.6 is available. You can install it as usual:
pip3 install -U otree-core otree resetdb
Here are some changes:
- The rooms feature is more fully developed and functional.
- Various improvements to the admin interface
- If you update a template you don’t have to reload the server
- Chinese now uses the proper
runprodservernow defaults to port 8000 (before was 5000)
oTree 0.5 is now released.
It has a different architecture based on WebSockets. It runs faster and supports more concurrent players.
It also has a “Server Check” feature in the admin interface that checks if your server is set up properly.
Redis needs to be installed on your server.
If using Heroku, you should install Heroku’s Redis add-on,
Then update your
requirements_base.txt so it contains the right version of
This will tell Heroku which version of oTree to install.
(The currently installed version of
otree-core is listed in the output of
In your project’s root directory, find the file
change its contents to the following, and if using Heroku, turn on both dynos:
web: otree webandworkers timeoutworker: otree timeoutworker