René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Python Crashes when using this Plugin in OSX High Sierra","articleBody":"**Summary:**\r\nAttempting to use this plugin on High Sierra is causing a python crash. Reproduced on both Python 2.7.14 and 3.6.2 (installed with brew). Unable to reproduce with other lookup plugins.\r\n\r\n**Reproduction:**\r\nA simple playbook with a debug step will do:\r\n```yaml\r\n- hosts: localhost\r\n  tasks:\r\n    - debug:\r\n        msg: \"{{ lookup('vault', 'secret/dev/test', 'hello') }}\"\r\n```\r\n\r\n**Symptoms:**\r\nIn the terminal which executes this playbook, the output looks like:\r\n```\r\nPLAY [localhost] ***************************************************************\r\n\r\nTASK [Gathering Facts] *********************************************************\r\nok: [localhost]\r\n\r\nTASK [debug] *******************************************************************\r\nobjc[34976]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.\r\nobjc[34976]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.\r\n```\r\n\r\n**Additional notes:**\r\nThis appears to be due to some low-level objective-C changes introduced in High Sierra. This article (http://sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html) has more details. It also provides a workaround: Setting the environment variable `OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES`. Setting this before running ansible provides successful results.\r\n\r\nI'll be honest, I have no clue what the \"correct\" fix is here, or even if it can be made in this plugin (as opposed to ansible or python itself). Mostly I'm documenting this here in case others come across this issue - I hope someone finds this useful. I'm content with using the environment variable for the time being.","author":{"url":"https://github.com/ajrgrubbs","@type":"Person","name":"ajrgrubbs"},"datePublished":"2017-09-28T16:50:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/60/ansible-vault/issues/60"}