-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
salt 3000.1 #52835
salt 3000.1 #52835
Conversation
Now refuses to run unless a huge list of pyobjc dependencies are installed first. |
I don't even see what they use pyobjc for... |
Can we drop this list of resources and install them as |
|
Oh boy, it's PyObjC time. |
Probably. Ideally we wouldn't unless upstream lock their versions, but there becomes a point where it is infeasible to vendor everything. We give other projects some slack, like everything that depends on |
Both Not sure what is the right way to handle this. Just drop High Sierra support? |
Would it be bad if we just do |
c050aa3
to
ed8b340
Compare
I don't really like an idea of pathing packages in such way (on the contrary with what salt developers do). But on the other hand, it will just limit some feature on High Sierra, but other available. Btw, the funniest thing is that
|
I suppose it might make sense in the context of a virtualenv, depending on whether said user scripts are able to play nicely with such setup. PyObjC is almost always doomed to cause broken linkage on anything that's not the latest OS. It's because it's not lightweight - the PyObjC dependency pulls in modules for every supported system framework, which can mean new frameworks only present on recent OS versions. The reason it doesn't on Mojave is because Salt use an older version that predates Catalina. |
Fair enough, let's try without PyObjC |
Co-Authored-By: Alexander Bayandin <[email protected]>
0f807e3
to
58845d1
Compare
Created with
brew bump-formula-pr
.