Install DeepSpeech on Mac M1 - mozilla-deepspeech

At the moment I need to install and run DeepSpeech on my local.
Can someone help me how with installing DeepSpeech on my Mac. I have already installed Python 3.10.0 but it seems like this version do not work with DeepSeech

Related

Can't install Postgres on MacBook M1, Mac OS Monterey 12.4

I have problems installing Postgres on my MacBook M1
The Downloaded Installer is failing (Error in Postprocessing) from www.enterprisedb.com and when I try it with "Port" it is not working (it installs, but doesn't install executables like "pg_ctl")
Is there a solution?
(10 years ago I´ve downloaded the source and compiled it)
Nowadays I would suggest same like Calin's comment:
Install using Homebrew
brew install postgresql
As you can see on brew.sh when searching for formula postgresql it has binaries (Bottle) supporting:
Apple Silicon (M1) on macOS Monterey
See also:
Installing Postgres via Brew (OSX)
Installing Postgres with brew in 2 easy steps – An Integrated World
postgresql not installed but homebrew reports it is

Unable to install locust on windows

Hi i am trying to install locust on windows with python version 3.7.3, using pip install locustio but getting below error.
ERROR: Could not build wheels for gevent which use PEP 517 and cannot be installed directly
I was getting above error because Visual Studio was not installed in my machine. When I did I was able to install locust, and its working fine now.
Had faced a similiar issue on MacOS.
The MacOS Catalina update upgraded my system python was 3.8. (Gevent works with <3.7)
Installing a lower version with pyenv fixed it.

Enthought Canopy, pip not installing freshest github commit

I'm really perplexed by this behavior:
I am installing a github repo using pip with the Canopy Command Prompt in Enthought Canopy version 1.5.2
When I install a package from github, it clones the file, installs and says everything is up to date and even changes the version number, but the imported package is still the old version
For instance, I change the names of a function from version 7.1.1 to 7.1.2. When I go to install the latest version, pip tells me I have installed version 7.1.2, but the changes are not taking place in the actual install when I import the file in the Canopy Editor, in fact a simple help(package) is showing the old version as still installed. So pip in the Canopy Command Prompt is telling me I am installing the latest version, but when I import that package in the actual Canopy Editor, the older version is installed.
I have restarted my kernel, closed the Enthought program, but neither seem to fix the problem.

Issues understanding homebrew on my mac running 10.7 os/x

I tried installing postgres on my mac using homebrew.
It's not working.
How do I remove what homebrew put in for me?
Thanks.
How about 'brew list' to see what you installed and 'brew remove [your-program]'? I guess this is all in the brew manpage. And even more info on this page about PostgreSQL on OS X.

paperclip image broken in rails 3.1rc4

I am using rails 3.1rc4 with paperclip and i cannot upload any image file with. I keep getting this error
Image D:/Users/MOBILE/AppData/Local/Temp/stream20110612-3872-y7hmme-0.jpg is not recognized by the 'identify' command. I have imagemagic installed. But it works in <= rails 3.0.8rc4.
I'm on Mac and I had the exact same problem after I updated to Mac OS Lion,
in order to fix this error I had to reinstall imagemagick
This might help other Mac OS Lion users:
First make sure to download the latest XCode from the app store (4.1 atm I believe, it's free)
Using Homebrew:
brew uninstall imagemagick
brew update
if you get any errors, clean up files ending in .a or .la with "brew doctor",
then just do
brew install imagemagick
If you are using MacPorts do:
port uninstall imagemagick
port selfupdate
port install imagemagick
I am not sure if this will adress your specific issue but I found this and maybe its related:
https://github.com/thoughtbot/paperclip/issues/481
It states:
The paperclip:refresh:metadata rake task fails with Rails 3.1 as ActiveRecord no longer supports instance.save(false) - you must now use instance.save(:validate => false) instead.