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

Ensure pyzmq and redis also installed with pip2 for Python 2 #15

Merged

Conversation

jbarlow-mcafee
Copy link
Contributor

Previously, pyzmq and redis were pip installed using the default pip,
which was for Python 3. This resulted in the pyzmq and redis packages
not being found when the MISP server spawned the mispzmq script using
the default python, which is version 2. With this commit, pyzmq and
redis would be installed for both Python 2 (via pip2) and Python 3
(via pip3), which should allow the packages to be available to scripts
which use it from different Python versions.

Previously, pyzmq and redis were pip installed using the default pip,
which was for Python 3. This resulted in the pyzmq and redis packages
not being found when the MISP server spawned the mispzmq script using
the default python, which is version 2. With this commit, pyzmq and
redis would be installed for both Python 2 (via pip2) and Python 3
(via pip3), which should allow the packages to be available to scripts
which use it from different Python versions.
@ventz
Copy link
Collaborator

ventz commented Apr 10, 2018

@jbarlow-mcafee Have you checked that there are no collisions between the two?

If so - I have no problem in merging this.

@jbarlow-mcafee
Copy link
Contributor Author

@ventz I did try this out with a custom build of the Dockerfile and saw that the mispzmq script was working fine with MISP ZeroMQ after the change. I don't believe it should be a problem to have these packages installed for both Python 2 and 3 at the same time. Even though it did not appear that pyzmq and redis needed to be installed under Python 3 in order for the mispzmq script to work, I figured it would probably be best to continue to have them installed for Python 3 for any custom modules running under Python 3 that might need to use them. Does that sound reasonable to you? Thanks!

@ventz
Copy link
Collaborator

ventz commented Apr 10, 2018

@jbarlow-mcafee Ok - and yes it does.

Thanks - merging.

@ventz ventz merged commit e2300e0 into harvard-itsecurity:master Apr 10, 2018
ventz added a commit that referenced this pull request Apr 10, 2018
…e - thanks to @jbarlow-mcafee for discovering and proposing fixes
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

Successfully merging this pull request may close these issues.

2 participants