It breaks all sorts of things, even the version of py2app that Apple themselves ship - but are too lazy to test or read bug reports about for year after year.
“All sorts of things” is a broad statement to toss around without at least some links. I primarily work in python and had never even heard of the py2app issue since it’s not an incredibly common tool and most python developers I know use newer versions of python.
That’s why I questioned the original broad claim: I know there are edge cases but most of the developers I know work on Macs and SIP just isn’t mentioned often enough for it to be anywhere near as bad in general as a few random commenters claim, not to mention that anyone I know who’s at all security savvy appreciates that it’s a trade off rather than a unilateral bad move.
I develop against the deployment environment run in virtual machines for two reasons.
1) Too many packages/servers/etc. I've tried to install under OS X over the years just didn't quite work right. That's probably not the case so much any more, but I have experienced it recently.
2) Developing against a macOS localhost can mask problems associated with my code running in the deployment environment. So to avoid those surprises, I develop against the deployment environment.
If I need root for package install or other server deployments, I log into the VM and do it there. I rarely need to install stuff on my macOS workstation.
Re: #1 that’s been generally smooth for me since Homebrew stabilized but I think your second point is key: it’s faster to develop locally but you definitely want to have some regular test that you’re in sync with the actual deployment environment. Docker has made that pretty easy now that the Mac Docker app is solid.
Brew is what I was alluding to, they have straightened out much of the package management issues. I ran into problems recently where certain CPAN modules wouldn't compile under OS X.
