-
Notifications
You must be signed in to change notification settings - Fork 77
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
MNT: stop install wrong pyca package through pip, and enabled psp test which uses pyca's psp library #1136
base: master
Are you sure you want to change the base?
Conversation
1674763
to
bc3550b
Compare
"works on my machine", need to figure why failing automation also not sure how much issue it is to revert epicscorelibs in order to have pyca... |
89d0b67
to
44e03c3
Compare
this patch is blocked for now, |
Do I need to make some updates to |
The correct package is on github: https://github.com/slaclab/pyca and on coda: https://anaconda.org/conda-forge/pyca. Need to switch to using correct package, which will fix 'psp' plugin related tests. (psp is part of pyca) Installing correct library and enabling test fixes issue where a user downloads pydm and runs the tests with pytest cmd directly (instead of run_tests.py), only to see 'no module named psp' failure. This failure seems to suggest to user to 'pip install psp', which is the wrong package and confusing.
44e03c3
to
c194578
Compare
btw @tangkong very recently fixed the pyca builds. It should install via pip from github or from the recently updated conda forge build. |
This test can be enabled now that we are using correct pyca package from
conda.
Installing correct library and enabling test fixes issue where a user
downloads pydm and runs the tests with pytest cmd directly (instead of
run_tests.py), only to see 'no module named psp' failure. This failure seems to suggest
to user to 'pip install psp', which is entirely the wrong package and
just leads to further confusion.