https://pantsbuild.org/ logo
Join Slack
Powered by
We have a new hire running macOS Big Sur (10.16). ...
# general
j
We have a new hire running macOS Big Sur (10.16). They had a working pants setup but something happened and now they get the following error when they run `./pants`:
Copy code
Exception message: Could not satisfy all requirements for pantsbuild.pants==1.25.0:
    pantsbuild.pants==1.25.0(from: pantsbuild.pants.contrib.python.checks==1.25.0)
They have 
libffi
installed.
h
is there more to the exception message?
j
I will ask for the whole output.
I was just wondering if there is something special about Big Sur that might cause issues with this plugin.
But let me get more info and I'll update the thread.
h
Not that I'm aware of. A couple folks have been using Big Sur for some time, but on Pants 2.x It could be a transitive dep failing to build, lots of sdists had/have issues with Big Sur because it no longer follows the versioning scheme 10.x but now is 11.0
j
oh. I thought it reported as 10.16.
h
No I don't think. I had some issues installing things as a result, but I think newer versions of deps fixed it. Which might not be much help if you're stuck on 1.25
👍🏽 1
j
I am removing all references to the 
checks
plugin for Big Sur users and this seems to work
h
It looks like 1.25 already supported 
pants.backend.python.lint.flake8
under 
backend_packages2
, which is a substantially improved version of that 
checks
plugin. I definitely recommend using that instead https://github.com/pantsbuild/flake8-pantsbuild#migrating-from-lintpythonstyle-to-flake8
j
👍🏽
To unblock this one user though I just want them to be able to not load the plugin
👍 1
When I made a 
pants.bigsur.ini
file with all the 
plugin: []
and 
pycheck
out, it seems to be inheriting from the main 
pants.ini
How can I prevent it from loading the 
checks
command?
h
Sounds good (I have a thing against that plugin, it caused so many issues with the Py3 migration)
How can I prevent it from loading the checks command?
I'm not following, what do you mean?
j
${BUILDROOT}/pants.orig --pants-config-files=${BUILDROOT}/pants.bigsur.ini
is the new pants command he is running where 
pants.bigsur.ini
is a copy of our 
pants.ini
but with
Copy code
32   │ plugins: [
  33   │     "pantsbuild.pants.contrib.python.checks==%(pants_version)s",
  34   │   ]
removed. I also removed 
[pycheck-indentation]
and other 
pycheck
configs.
h
if you exclusively want to use that config, then 
./pants --pants-config-files='["pants.bigsur.ini"]
because this is a list option so right now you're appending to the list
j
ahh. Thank you!
h
or set 
PANTS_CONFIG_FILES='["pants.bigsur.ini"]
. Maybe check out envrc to auto-load that
j
👍🏽
perfect.
Ok I can troubleshoot from here. Thank you for pointing me in the right direction.
💯 1
Setting the ENV variables was our best work around. Thank you, again!
💯 1
Open in Slack
PreviousNext
Powered by