whims | a collection of scripts

import sys; print "%s.%s.%s"

That's some good old Python 2 notation if I ever saw some :)

As @ElapsedSoul mentioned. macOS 12.3 removed the Python 2 that came by default for all these years. Therefore, I would personally recommend for others not to upgrade to 12.3 if you need Python 2 until you find an alternative solution.

Some possible alternatives include the following:

Homebrew unfortunately got rid of Python 2 a long time ago. There are however some workarounds to try and get it to work: How to reinstall python@2 from Homebrew?.

I haven't tested this, so it might not work. But if it does, this is likely the best solution for your needs. From the following:

Those are not errors but warnings that won't affect your working and how swagger behaves. They just notify the user who might be the maker of the package to update their package as the packages their package depends upon have been deprecated and may have bugs

Try clearing the cache using below code:

As you are using node version 17, I can see that this problem happens,

Downgrading to node version 16 will solve the problem(using nvm):

It's not an error due to npm.

NPM install the package that has a build script to build node-gyp. The build fails due to the license agreement with :

You have not agreed to the Xcode license agreements, please run 'sudo xcodebuild -license' from within a Terminal window to review and agree to the Xcode license agreements.

so just run the command to accept the license agreement

The node-sass package suggests that the Node 16 is supported in node-sass version 6+. So, install the latest version of node-sass (npm i node-sass@latest) or update the package.json dependency to "node-sass": "^7.0.1" and then try a full install again (npm install).

Edit

I had to perform a couple of extra steps to get this to work.

1. Add "node-sass": "^7.0.1" as the dependency in package.json
2. Install react-scripts version 4.0.3: npm install react-scripts@4.0.3
3. Rebuild node-sass with npm rebuild node-sass
4. Start the application with npm start

You could even investigate updating react-scripts to the latest version 5.

It's unclear what version of node-sass it's trying to install, but my guess from the node-gyp 3.8 that it's something around 4.x, so the newest version of Node it likely supports is 14 https://github.com/sass/node-sass#node-version-support-policy

It looks like something in your project is using node-sass, which contains libsass which is deprecated

If it is a direct dependency, you can just switch over to Dart Sass, and things mostly should just work the same. If it is a transitive dependency that is requiring node-sass, you can try to update it by updating your direct dependencies that depend on it. Alternatively, if you're using yarn, you can try to change it with selective version resolutions

If you couldn't manage to switch to using dart-sass and have to deal with the C++ gyp build error, I would probably check to make sure that the particular version of node-sass you're using is compatible with the current c++ compiler you currently have installed. Maybe your compiler became too old because libsass (and in turn, node-sass) decided to up their language requirements?

Edit: Try using this technique (since you are using npm) for resolving the node-sass that is inside vue-mj-daterangepicker to something else. You can change to a newer version or by using the "dart-sass" package. If you use the latter, g++ wouldn't error since dart-sass doesn't use c++. You could also use the "sass" package, since the sass and dart-sass npm pacakges are essentially the same

Maybe something like the following in your package.json... (not tested)

I had the same problem with literally the exact same number of vulnerabilities.

Check out the solution here