Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Running into a segfault issue bumping cffi - <https://github.com/pantsbuild/pants/pull/7484#issuecomment-479679456>

Repro’d on a mac (Air, macOS 10.14.4, pyenv python 2.7.14) - pulled this in case it’s helpful, could use a hand looking into this if anyone has a moment <https://gist.github.com/codealchemy/4de401a2c1c46adb9f0e1ab03e618e9f>

I’m going to walk back the cffi version to see which one breaks things

Tests with cffi 1.12 were green locally, pushing that to check CI.

Change in 1.12.1 no longer compiles with `Py_LIMITED_API`, per <https://github.com/pantsbuild/pants/blob/master/src/python/pants/releases/packages.py#L95-L101> we set that up in the native engine so my guess is that’s where things are going sideways.

would it be reasonable to do something like ```
cffi==1.12 ; python_version&lt;'3'
cffi==1.12.1 ; python_version&gt;='3'
```?

since the django project is py 3.6.6 anyway