Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ans1crypto abort error on OSX Catalina zsh shell #386

Closed
TylerJamesMalloy opened this issue Jan 3, 2020 · 3 comments
Closed

ans1crypto abort error on OSX Catalina zsh shell #386

TylerJamesMalloy opened this issue Jan 3, 2020 · 3 comments

Comments

@TylerJamesMalloy
Copy link

Running pip install psiturk installs the asn1crypto==0.24.0, package which has an issue with OSX Catalina zsh shell and needs to be upgraded to asn1crypto 1.2.0. For compatibility with OSX the version should be updated to asn1crypto 1.2.0 and all compatibility issues fixed.

After installing psiturk with pip all pip functionality will be broken on the zsh shell and you will need to manually remove the package from your site-packages folder and reinstall it which gives the following error:

ERROR: psiturk 2.3.6 has requirement asn1crypto==0.24.0, but you'll have asn1crypto 1.2.0 which is incompatible.

The error and solution to the ans1crypto issue are detailed here:
Homebrew/homebrew-core#44996

This error made it so that I was unable to run the psiturk-setup-example which is now running, though I don't know if there are any other issues caused by switching to asn1crypto 1.2.0

@deargle
Copy link
Collaborator

deargle commented Jan 3, 2020

I just switched the python2 branch requiremenets.txt file to be generated using pipreqs instead of pip freeze. This removed stale package dependencies such as asn1crypto from the requirements file. Can you install from python2 branch to confirm that it works for you?

git clone [email protected]:NYUCCL/psiTurk.git
cd psiTurk
git checkout python2
pip install -e .

@TylerJamesMalloy
Copy link
Author

Currently working for me. asn1crypto is not installed when running pip install -e . on that branch, and the issue is no longer present.

@deargle
Copy link
Collaborator

deargle commented Jan 6, 2020

fixed in v2.3.7

@deargle deargle closed this as completed Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants