minor bugfix for hit_extend

v2.3.9

try to tell travis to use python2-compat pytest-mock

v2.3.8

bump version

v2.3.7

bump version

Bugfix for versions still supporting python2

Backporting some bug fixes; also addressing the datastring formatting problem.

python3-compatible

2.3.2

set version number in changelog

boto3-compatible

On June 1st, 2019, mturk is deprecating its old api, which boto used. This release switches psiturk over to use boto3, which uses the new api. A testing suite is still in progress so there perhaps may be some bumps... stay tuned.

2.2.4

bump version but not calling it stable in readme yet

2.2.3

This minor bump adds a new column, 'mode'. This records whether the mode for a participant was debug, live, sandbox, etc. Having this handy helps filter out unwanted records during the analysis stage.

If you use psiturk 2.2.3 with a project with a db that was created with psiturk < 2.2.3, you will need to manually create the 'mode' column in your db. If you're still using sqlite and if your schema name is still participants.db and your table name is still turkdemo (those are the default), you can run this from the terminal:

sqlite3 participants.db
ALTER TABLE turkdemo ADD COLUMN mode VARCHAR(128);
<ctrl+d>

That same sql will work for mysql and psql, too.

2.2.2

• Adds a new error handling class, InvalidUsage, which can be used for API errors if you're building an API into custom.py etc.

2.2.1

This tag was created to make it easy for Heroku to install a compatible version of psiturk via pip.

New Features

• first-stage heroku integration (see #254, particularly this comment to get going).

Bug Fixes

• fix where debug -p link didn't work if only adserver_revproxy_host was set but not adserver_revproxy_port (thanks @braingineer)