I’d once again recommend running Jamf Migrator against your Jamf Pro instance to download any scripts and Extension Attributes to check. ![]() But to generalise, you’ll want to check all your scripts and packages for occurrences of python -c, /usr/bin/python or /usr/bin/env python.īelow is some more specific guidance: Jamf Pro Well, depends on what systems you’re using. It really depends on how the Python 2 was being invoked, but directly you’ll likely see something like: /usr/bin/python: bad interpreter: No such file or directoryĪnds maybe: /usr/bin/python: command not found So, now what? This is the same as calling #!/usr/bin/env python, and as such as the same caveats. So, these will fail as they will likely not be able find a file or if they do find a file, it could be Python 3. When things are calling #!/usr/bin/env python, they are telling the OS to traverse the directories shown in $PATH for a file named “python” and to then use that. These changes are in part why Python 2 is still being used, despite Python 3 having been released on December 3, 2008. ![]() ![]() ![]() Python 3 includes several changes which mean that backwards compatibility with Python 2 isn’t possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |