# general


12/19/2022, 8:56 PM
We've put a lot of effort recently into getting most of our python repo (and all of our default resolve) compatible with native apple m1 development. There are a couple places where it is not feasible to use only packages that are compatible with m1, but we have isolated them into their own resolve. This has worked well for being able to manage packaging the different artifacts, but resulted in a state where developers who running in a native m1 environment are now unable to run commands like
./pants lint ::
. Is there anything we can do? An env var we could set on these systems to always filter out targets on the "bad" resolve?