René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"SEGFAULT when certain modules are used in a project with Alpine 3.6/Python 3.6","articleBody":"We've recently upgraded several of our containers to Python 3.6.\r\n\r\nSome of the containers always segfault immediately after starting Django's `runserver` command.\r\n\r\nIn a couple of the containers upgrading our dependencies fixed the issue, but on some of the other containers that didn't have the issue upgrading the dependencies caused it to start happening.\r\n\r\nIn one example upgrading `requests` from 2.12.1 to 2.18.1 stopped the SEGFAULTs but adding the latest version of `boto3` caused them to start again.\r\n\r\nThe issue only happens when run under docker.\r\n\r\nI have a [simple example repo here](https://github.com/beaugunderson/crash-test) and would like to offer a bounty of $100 to whoever can either fix the issue or explain it in a way that allows me to fix it. ✨\r\n\r\nEdit: we've tested with `3-alpine` and `3-alpine3.6`; same result.\r\n\r\nAlso SEGFAULTs on `3.6.2rc2-alpine3.6`.\r\n\r\nMore clues: `requests` is also implicated in `boto3` which includes `botocore`--which includes a vendored `requests` 2.7.0.","author":{"url":"https://github.com/beaugunderson","@type":"Person","name":"beaugunderson"},"datePublished":"2017-07-12T17:14:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":29},"url":"https://github.com/211/python/issues/211"}