Hot answers tagged

15

Bash Since Bash is typically the default shell you can open up this file in your home directory: $ vim ~/.bash_profile And add your variable to this file: export ENV_VAR=12345 You can do this without even having to edit this file if you like, using the following one-liner: $ echo 'export ENV_VAR=12345' >> ~/.bash_profile And then confirm like so:...


15

Kinda. A clean installation of Catalina includes a /usr/bin/python3 binary, but it's a stub for installing the command line developer tools, which includes Python 3. If/when the command line developer tools are installed, the /usr/bin/python3 stub will run the actual python3 binary, but a clean install will just have the stub. The Python 2 binaries (/usr/...


8

From Xcode 11 Beta Release Notes: Scripting language runtimes such as Python, Ruby, and Perl are included in macOS for compatibility with legacy software. In future versions of macOS, scripting language runtimes won’t be available by default, and may require you to install an additional package. If your software depends on scripting languages, it’s ...


5

If you want to list all files/folders in a directory, you should type ls not Is. It is L, not i. To learn python, you won't need to reach ~/.bash_profile unless you need to change versions. Just use which python or python --version and use the syntax for the version that appears. Or use online compilers for quick testing. Suppose you have your file learn....


5

Ideally you can restore whatever you‘ve deleted from a backup. If you removed the standard Python installation of macOS, boot into the Recovery Partition (if any) and reinstall macOS from there. This should leave your other files intact, it‘s not a bad idea to do a backup before nevertheless. Alternatively, you can through Homebrew. Once Homebrew is ...


4

Yes - that file is part of the system image and ships on every Mac. When fully installed, version 3.7.3 is what Catalina installs from this stub. Keep in mind python 2.7.16 is still the default python if you don’t call python3 ~ % /usr/bin/python3 --version Python 3.7.3


4

You can accomplish this by adding export PATH="/path/to/python:"$PATH to your ~/.zshrc (or ~/.bash_profile if you're not on Catalina). I'd like to propose an alternative and suggest pyenv, available via Homebrew. You can set a specific Python version to be "global" (i.e. default everywhere) and/or "local" (i.e. using that version in a specific directory ...


3

So after some further testing, it looked like it was an issue with only certain virtual environments that I was using that I had reconfigured by following the guide on anaconda: https://www.anaconda.com/how-to-restore-anaconda-after-macos-catalina-update/ My system python had also been set to the conda one by default by this, which was why I was getting ...


3

That problem is caused by asn1crypto. You could try: rm -rf /usr/local/lib/python3.7/site-packages/asn1crypto* Which will uninstall asn1crypto. Reference: This Stack Overflow Post


3

I suggest that you use an absolute path in ProgramArguments, so <key>ProgramArguments</key> <array> <string>python</string> would become <key>ProgramArguments</key> <array> <string>/usr/local/bin/python3</string> .......... Your PATH variable is not correct. Change it ...


3

I installed Python 3.8 for macOS using the installer from python.org, not homebrew which is also installed on my Mac but rarely used. I think the first three lines below to my ~/.bash_profile was automatically added by the installer from python.org. With those, any changes I make using pip3 seem to affect only the 3.8 whereas those made via pip seem to ...


2

As well as xattr, other scripts in /usr/bin/ are smtpd.py and systriage. A number of Automator actions for working with PDFs have at their heart python scripts -- the ones for combining PDFs, watermarking PDFs, extracting pages and converting images. Quite a few scripts in Server.app are python. It's not so much that they're definitively "not compatible" ...


2

I installed MacOS Catalina Beta and it was packaged with scripting languages like python (2.7) and ruby. Python3 was not available. So probably they might remove it in the next major release (10.16) or they might remove it in the stable version of 10.15. In the former case, everything would function as expected, I believe.


2

For running Python on a mac start at Python's documentation Python Launcher allows you to run python scripts from the desktop. The documentation says To run your script from the Finder you have two options: Drag it to PythonLauncher Select PythonLauncher as the default application to open your script (or any .py script) through the ...


2

if python is installed already just go to terminal, go to correct directory and type "python filename.py"


2

First, execute in a terminal with zsh (Z Shell): echo 'export ENV_VAR=12345' >> ~/.zshenv Then, reload changes: source ~/.zshenv Finally, test if your new variable is set: echo $ENV_VAR Note: By standard, the .zshenv file should only contain environment variables setting commands. .zshenv is sourced on all invocations of the shell, hence it will ...


2

Running python scripts in shell scripts seems to work for me. Does the script have executable flags set? Also, is there any reason you're using a shell script to pass the arguments to the python script, and not just embedding the python script in the Action? You can set the 'Shell' drop-down value to /usr/bin/python, to use the bundled system python; or ...


2

Type python3 and you will be running the new version. How you install can vary a bit, but on the current macOS you don’t need to install anything as the stub exists. On any older os I recommend installing https://brew.sh as it has a very friendly on boarding and helps you set your PATH properly to run the v3 of python. A shell alias is an easy way to fix ...


2

https://github.com/pyenv/pyenv#basic-github-checkout Define environment variable PYENV_ROOT to point to the path where pyenv repo is cloned and add $PYENV_ROOT/bin to your $PATH for access to the pyenv command-line utility. $ echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bash_profile $ echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/....


2

chown the usr/local directory: sudo chown -R $(whoami) /usr/local Then try to install python3 again and it should work: brew install python3 OR, You can try this also if the above solution didn't help sudo chown -R $(whoami) $(brew --prefix)/* Reference: https://gist.github.com/irazasyed/7732946


1

You can try below options: brew install pipenv # if you have brew installed pip3 install pipenv # if you don't have brew installed


1

You can try the following command on the terminal: sudo easy_install pip.


1

If I understand correctly, you want to have pip for your installation of Python 2.7. The builtin Python 2.7 with macOS does not include pip, so you will have to install Python 2.7 as well, either by brew or from the installation packages on Python.org. This will install pip for your installation of Python 2.7 and will additionally give you the alias pip2.


1

The library Dynamic Audio Normalizer works with FFmpeg, you can install FFMpeg on macOS Catalina using Homebrew. Then to normalize the audio or video file run this command from the Terminal app: $ ffmpeg -i <input_file> -af dynaudnorm <output_file>


1

Amadeus is an audio editing software I've used for many years. They have a menu option Effects ==> Audio Units ==> AUDynamicsProcessor that does what Levelator did, and it takes only a few seconds instead of a few minutes to process the file. I run it through that effect twice and then Amplify the sound to my preferred level afterward. This is great for ...


1

Perhaps not the solution you're looking for, in that it is not free (the "Basic" plan is $6/mo), but Landr offers a great online tool to "Master" all audio, add levels, tone, warmth, etc. Hope some of this helps.


1

brew uninstall --ignore-dependencies python3 Then: brew install python3 and done: python3


1

When you run python launcher you should get a set of menu items. Go to the Python Launcher menu item and under that select Preferences. The panel that appears should look like the image below. As you can see there is a checkbox to run in a terminal window.


1

I had to do this; I used: sudo find / -name '*3.7*' 2>/dev/null | grep -e '[Pp]y' | xargs sudo ls -lad I pipe stderr to /dev/null to eliminate internal files that even with sudo I can't access. Things like: find: /private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/0: Operation not permitted That returned all the possible Python 3.7 files / folders /...


1

The short arrow is indicating alias. Some like that are also there in my Applications folder for apps which are located in ~/Library folder. So I can guess that when first photo's original process is done, alias is still active. This happens to me while using OpenCV. closewindow() is hard to perform. I have to force quit it every time(it kills jupyter ...


Only top voted, non community-wiki answers of a minimum length are eligible