Closed rjhubbard88 closed 5 years ago
Perfect, I installed from pip so that explains it. Thanks Dave.
nw. I'm going to reopen this until I update pip.
I'm still leaving this open since the api retirement date is tomorrow (June 1st), but v2.3.0 is published on pip now, and is compatible with the new api.
Seems like the AMI does not have these changes?
I don't support the AMI.
On Tue, Aug 6, 2019, 11:04 AM Yang-Yang Feng notifications@github.com wrote:
Seems like the AMI does not have these changes?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NYUCCL/psiTurk/issues/348?email_source=notifications&email_token=AAI6Y7MQA2ALQ4NSTQNN2GDQDGVIRA5CNFSM4HKF4CZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3VZ44I#issuecomment-518758001, or mute the thread https://github.com/notifications/unsubscribe-auth/AAI6Y7KX2R2Y424U2POECA3QDGVIRANCNFSM4HKF4CZA .
Hi there, I've installed Psiturk 2.2.4 on my Linux Mint machine and attempted to run it (I have an AWS account and credentials, as well as Psiturk, and have changed the global configuration file). I get the following error:
I see a blog post from Mturk about this issue: https://blog.mturk.com/older-versions-of-the-mturk-requester-api-to-be-deprecated-beginning-june-1st-2019-9fcc9791fa18
It's not quite June 1st, but maybe they rolled this out already and Psiturk won't work without Boto3? Unless of course I'm just making a mistake somewhere.
Thanks in advance.