I am trying to install the Google Analytics apps in Django and when trying:
django-google-analytics-app --version
django-google-analytics-app -V
which django-google-analytics-app
I either get
zsh: command not found: django-google-analytics-app
or
django-google-analytics-app not found
How could I check if this app has been installed and how could I check its version?
django-google-analytics-app will not give you a binary file to get the version against. You can run the following command to see if the package is installed.
pip freeze | grep "django-google-analytics-app"
If this command gives you some output similar to
django-google-analytics-app==<version>
then the package is installed. If there is no output then the package is not installed
Related
Installed python installed on system of version 3.8.5 but there is an error with pip. pip is not installed
Below is the path
C:\Users\Comp1\AppData\Local\Programs\Python\Python38-32\Scripts
Found some results and tried running python get-pip.py from cmd but didn't work.
Also checked PATH and was correct
After using pip command in cmd it gives "pip is not recoganized"
Please let me know how can I fix this issue.
I'm on a Mac OSX (Catalina) trying to install the AWS Elastic Beanstalk CLI.
>>>python --version
Python 2.7.16
>>>which python
/usr/bin/python
>>>python3 --version
Python 3.7.5
>>>which python3
/usr/local/bin/python3
What I've tried
Using Brew
>>>brew uninstall awsebcli
>>>brew install awsebcli
>>>eb --version
-bash: /Users/<user>/.local/bin/eb: /Users/<user>/projects/hello-world-flask/venv/bin/python3: bad interpreter: No such file or directory
Now the funny thing is that hello-world-flask is just a toy example I have in one of my directories, but I have no idea why the EB CLI is trying to use that venv, or why it says that it doesn't exist.
>>>ls /Users/<user>/projects/hello-world-flask/venv/bin/python3
/Users/<user>/projects/hello-world-flask/venv/bin/python3
Using Pip3
>>>brew uninstall awsebcli
>>>pip3 install awsebcli
...
Successfully installed awsebcli-3.16.0
>>>eb --version
-bash: /Users/<user>/.local/bin/eb: /Users/<user>/projects/hello-world-flask/venv/bin/python3: bad interpreter: No such file or directory
The Question
I'm assuming the EB CLI is just supposed to execute Python 3.x. How do I fix this and make the EB CLI use the correct version of Python?
I realize this answer is a bit late and ran into a similar issue myself. According to this you might have better luck being explicit about your python executable and using the --python-installation flag. Try something like
python scripts/ebcli_installer.py --python-installation /path/to/some/python/on/your/computer
or to be extra explicit
/path/to/your/exact/python scripts/ebcli_installer.py --python-installation /path/to/some/python/on/your/computer
This is part of the "Advanced Use" section on the EB CLI github
I couldn't figure this out. I keep encountering error env: python: No such file or directory. So I just defaulted to installing it via brew https://formulae.brew.sh/formula/aws-elasticbeanstalk#default
I installed locustio on my ubuntu using pip
"pip install locustio"
the problem is that everytime I run any locust command on my console (for example)
locust --version
the console returns this
zsh: command not found: locust
any solutions ?
here's a trick:
write this command pip uninstall locustio in the console
this is what will be returned in the console
Uninstalling locustio-0.12.2:
Would remove:
/home/elta/.local/bin/locust
/home/elta/.local/lib/python2.7/site-packages/locust/*
/home/elta/.local/lib/python2.7/site-packages/locustio-0.12.2.dist-info/*
Proceed (y/n)?
write n , and copy the first directory which would be in my case
/home/elta/.local/bin/locust
now this is the directory you gonna use every time to call locust command, for example
/home/elta/.local/bin/locust --version
.... not the best solution, but at works perfectly and did the trick
Make sure the scripts are installed in a directory that is available in your PATH environment variable.
Use pip show --file locustio to figure out where the scripts are installed (in your case: ~/.local/bin). Modify your PATH to contain the directory where the scripts are installed. In your case, you probably should add something like the following to your ~/.zshrc file:
if [ -d "~/.local/bin" ] ; then
export PATH="~/.local/bin:$PATH"
fi
Then the locust command should be available in all new shell sessions.
I'd just installed the scrapyd-client(1.1.0) in a virtualenv, and run command 'scrapyd-deploy' successfully, but when I run 'scrapyd-client', the terminal said: command not found: scrapyd-client.
According to the readme file(https://github.com/scrapy/scrapyd-client), there should be a 'scrapyd-client' command.
I had checked the path '/lib/python2.7/site-packages/scrapyd-client', only 'scrapyd-deploy' in the folder.
Is the command 'scrapyd-client' being removed for now?
Create a fresh environment and install scrapyd-client first using below
pip install git+https://github.com/scrapy/scrapyd-client
And it should work. I was able to get it
$ which scrapyd-client
/Users/tarun.lalwani/.virtualenvs/sclient/bin/scrapyd-client
The package on pip may not be the latest one
When I tried creating a virtual environment with python using the command virtualenv venv from Terminal, I got the following error:
Using base prefix '/Users/zacharythomas/anaconda3'
New python executable in /Users/zacharythomas/venv/bin/python
dyld: Library not loaded: #rpath/libpython3.6m.dylib
Referenced from: /Users/zacharythomas/venv/bin/python
Reason: image not found
ERROR: The executable /Users/zacharythomas/venv/bin/python is not functioning
ERROR: It thinks sys.prefix is '/Users/zacharythomas' (should be '/Users/zacharythomas/venv')
ERROR: virtualenv is not compatible with this system or executable
I'm not the first person to encounter a similar error -- I tried following this answer's recommendations and running:
gfind ~/.virtualenvs/my-virtual-env/ -type l -xtype l -delete
That didn't help. Nor did running sudo virtualenv venv to run commmand as a super user.
What should I investigate next?
I had the exact same error message. Ray Donnelly at Continuum Analytics Support Group provided the following solution, which resolved the issue for me:
When you pip installed virtualenvwrapper, pip will have installed
virtualenv for you as it is a dependency. Unfortunately, that
virtualenv is not compatible with Anaconda Python. Fortunately, the
Anaconda Distribution has a virtualenv that is compatible. To fix
this:
pip uninstall virtualenv
conda install virtualenv
can't get virtualenv to work with anaconda3 v4.3 on mac