#BREW INSTALL MONGODB SPECIFIC VERSION HOW TO#
If you want to monkey with prior versions of Python installed via homebrew, this answer should help: How to install older formula using Brew? However, using virtualenv removes the need for much of these sorts of gymnastics. You can reset your homebrew python by removing it ( brew uninstall python), or by changing the symlink ( ln -s -f /usr/bin/python /usr/local/bin/python).
It's possible that you installed the latest python 2.7.x via brew which puts /usr/local/bin/python as a symlink in your $PATH, or you perhaps have a python alias pointing somewhere you don't want. For example, /usr/bin/python -V gives me 2.7.10 even though python -V gives me 2.7.13 (via brew). If you enter the command: which python, do you get /usr/bin/python (system) or /usr/local/bin/python (brew installed user-land python). However, assuming your use case really does require using a specific Python version - getting to an actual solution now - be sure sure you really upgraded system python to begin with. is true for a manually built or using brew (brew install mosquitto) to install.
#BREW INSTALL MONGODB SPECIFIC VERSION CODE#
Code written for 2.7.x should all be compatible. This is the plugin version 5 interface, which covers authentication. If you needed 2.6, that would be a different story since that's a change in minor version. MongoDB Shell to connect, configure, query, and work with your MongoDB database.
All pythons with the same minor revision number (2.7) should always be compatible. Secondly, I am unclear why you need 2.7.10 instead of 2.7.13. You need to assume that system utilities require a specific version of system python, and your user land code may then be locked to that python version forever, which is not wise (unless you're writing system utilities, in which case just use /bin/python, but then you wouldn't be asking this question.). First, it's generally considered bad practice to rely on system python for user land code if you can avoid it.
0 kommentar(er)
