Updates dependencies for Python 3.10 support #557
+41
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Had been running into many issues with packages on newer versions of Python (3.10+). This commit updates most, if not all, the packages to their latest versions to allow for 3.10. It also removes 3.6 from the
python-app.yaml
, as GitHub actions no longer supports 3.6 (which recently reached EOL) on ubuntu-latest and thus fails Github workflows. Most of the newer package versions similarly no longer support 3.6.Additional small changes, mostly for fixing failing test cases:
psiturk/experiment_server_controller.py
: Thecheck_server_process_running
function was throwing exceptions in allpsiturk_shell
tests on my machine, as some processes returned inpsutil.process_iter
had already been terminated and thusproc.as_dict
would just throw. I wrapped in a try/catch block to remedy, which matches desired functionality.test_noaws.py
, the Github Action similarly fails to pass the last test of because pytest would disable socket use without explicitly specifying it using@pytest.mark.enable_socket
.experiment_server_controller.py
, I was only able to pass thepsiturk version
test by removingsys.exit()
from the server when not connected to AWS MTurk. I'm actually quite iffy on this change, because the psiturk CLI shouldn't depend on the server being run to function. I'd love input from someone who understands the functionality a bit better than me.Related PRs which this solves:
markupsafe==2.0.1