Differences

This shows you the differences between two versions of the page.

--- python_install [2017/12/30 16:52] – [Troubleshooting] g00r00
+++ python_install [2018/01/01 14:49] – [Troubleshooting] g00r00
@@ Line 5: / Line 5: @@
 Mystic requires that Python 2.7 is installed on your system if you wish to execute Python scripts.  The presence of Python is detected automatically by Mystic, and is initialized as needed.  It is not in any way a dependency and Mystic will continue to operate normally without it should you decide you do not wish to use it.
-Most Linux desktop distributions and Apple's macOS will come with Python 2.7 installed by default, and in many cases no installation will be required in order to use Python.  In Windows, Python needs to be installed by downloading it from the Website: [[http://www.python.org|www.python.org]]
+Most Linux desktop distributions and Apple's macOS will come with Python 2.7 installed by default, and in many cases no installation will be required in order to use Python.  If not, it can typically be installed by a package manager in Unix (explained below).  In Windows, Python needs to be installed by downloading it from the Website: [[http://www.python.org|www.python.org]]
 **Note:** If you are using the 32-bit version of Mystic (even if it is in a 64-bit operating system), then you need the 32-bit version of Python installed.  If you are using the 64-bit version of Mystic then you need to have the 64-bit version of Python installed.  This is a very common mistake, particularly on the Windows platform where SysOps will download the wrong bit-version of Python.
-==== Library Validation ====
+==== Library Validation / Installation ====
 When initializing Python, Mystic will be attempting to locate the following library depending on operating system:
@@ Line 28: / Line 28: @@
 The result will tell you where Python 2.7 is installed.  If Python 2.7 is installed under a different library name, then you will need to create a symbolic link to that filename using "libpython2.7.so.1.0" so Mystic can find it.
+If you cannot locate libpython2 then it may be that you do not have Python 2 installed or that you have a partial installation of Python 2.  You will likely need to install Python 2.7 and then possibly create a symbolic link as described above.  This can typically be installed by a package manager, as shown below on a Raspbian installation:
+  sudo apt-get update
+  sudo apt-get install libpython2.7
 ==== Environment Variables ====
@@ Line 83: / Line 89: @@
 The most common issue in Unix based platforms is that a link is not created to the Python library.  Mystic expects to find "libpython2.7.so.1.0" on Linux and "libpython2.7.dylib" in macOS, so if your Python library is stored under a different name then you need to make a symbolic link.
+Like the Windows version, another issue some people have ran into is that their bit level of Python does not match that of Mystic.  This can cause crashes when a script is attempting to execute.  The issue seems more prominent in macOS where the owner may not be aware of their OS bit-level, or their OS has a mix and match of 32-bit and 64-bit softrware.  This seems like common on the average Linux installation.