I created a virtual python environment and installed the GDAL-Wheel into it:
When I run my python-program I get the following message:
ERROR 1: PROJ: proj_identify: C:\Program Files\PostgreSQL\11\share\contrib\postgis-3.2\proj\proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 0 whereas a number >= 2 is expected. It comes from another PROJ installation.
I have also installed postgresSQL 11 on my machine.
Seems GDAL-Wheel and PostgresSQL 11 interfere /disturb each other?
the GDAL-wheel is from:
https://www.lfd.uci.edu/~gohlke/pythonlibs/
Check the package path under system environment its probably pointing to PostGIS folder. Get the windows binary pyproj file from the site you got the GDAL. Install with pip install, after it's done re run the pip install command to get the directory path.
Now just change the variable path for PROJ_LIB under system environment variables.
Related
I am following the steps stated here: How to use Stable Diffusion in Apple Silicon (M1/M2).
At my local MacBook M1 machine, I saved the below script in stable-diffusion.py file:
# make sure you're logged in with `huggingface-cli login`
from diffusers import StableDiffusionPipeline
pipe = StableDiffusionPipeline.from_pretrained("runwayml/stable-diffusion-v1-5")
pipe = pipe.to("mps")
# Recommended if your computer has < 64 GB of RAM
pipe.enable_attention_slicing()
prompt = "a photo of an astronaut riding a horse on mars"
# First-time "warmup" pass (see explanation above)
_ = pipe(prompt, num_inference_steps=1)
# Results match those from the CPU device after the warmup pass.
image = pipe(prompt).images[0]
Now when I am trying to execute: python stable-diffusion.py from Terminal, I am getting following error:
Traceback (most recent call last):
File "/Users/apple/Desktop/area_51/stable-diffusion.py", line 2, in <module>
from diffusers import StableDiffusionPipeline
ModuleNotFoundError: No module named 'diffusers'
In order to fix it even I tried: pip install diffusers, however I still got same error.
Am I missing anything over here?
If you have already installed diffusers but are still encountering the ModuleNotFoundError, it's possible that the module is installed in a different Python environment than the one you are running your script from. In that case, you may need to check your Python environment settings and ensure that the module is installed in the correct environment.
To check your Python environment settings, you can use the following steps:
First, determine which Python interpreter you are currently using by running the following command in your terminal:
which python3
This should output the path to the Python interpreter that is currently being used. (I assume you're using python3. If you are using python2 for some ungodly reason, you should switch to python3.)
Next, ensure that the diffusers package is installed in the environment associated with the Python interpreter you are using. You can do this by running the following command:
python3 -m site
This will output information about the Python installation, including the location of the site-packages directory where installed packages are stored.
Look for a line that says "sys.path" or "USER_SITE" to find the location of the site-packages directory. This is the directory where Python looks for installed packages.
Check if the diffusers package is installed in the site-packages directory. You can do this by looking for a directory called diffusers inside the site-packages directory.
For example, if the site-packages directory is located at /usr/local/lib/python3.9/site-packages, you can check for the diffusers package by running the following command:
ls /usr/local/lib/python3.9/site-packages | grep diffusers
If the diffusers package is installed, this command should output a directory called diffusers. If the package is not installed, the command will not output anything.
If the diffusers package is not installed in the correct environment, you can try installing it using the appropriate package manager for that environment. For example, if you are using a conda environment, you can try installing the package using conda (conda install -c conda-forge diffusers). If you are using a virtual environment created with venv, you can try activating the environment and installing the package using pip (pip3 install diffusers).
I have installed Anaconda from its site and was working fine for sometime, however I needed to install Plotly and used the below steps mentioned in another site.
I just got it up and running on spyder 3.0 using the following steps. (windows 10)
Download plotly using pip usig command line (python -m pip install plotly) this requires downloading python 3.5 separately from Spyder as well. (so far I haven’t had any conflicts)
In Spyder, goto->Tools ->PYTHONPATH Manager -> addPath -> insert path to Plotly library (mine was in python\python36-32\Lib\site-packages), then synchronize
Restart Spyder
test it out with import plotly.plotly \n import plotly.graph_objs as go in a new .py scrypt
Hope it works out for you.
Cheers
After the above steps I was able to import plotly in Spyder and didn't face any issues, however after I restarted my machine I'm unable to run Anaconda navigator or Spyder.
I'm able to launch Anaconda prompt but any command executed returns different kinds of errors like
"conda install anaconda-navigator"
environment variables:
conda info could not be constructed.
KeyError('pkgs_dirs')
"spyder"
ImportError: cannot import name 'constants' from partially initialized module 'zmq.backend.cython' (most likely due to a circular import) (C:\Python\Lib\site-packages\zmq\backend\cython_init_.py)
anaconda-navigator
ImportError: DLL load failed while importing shell: The specified module could not be found.
I tried every solution on internet like uninstalling and reinstalling, deleting all the trace files on anaconda and even the Environment variables seem to be fine
echo %PATH% command returns
C:\ProgramData\Anaconda3;C:\ProgramData\Anaconda3\Library\mingw-w64\bin;C:\ProgramData\Anaconda3\Library\usr\bin;C:\ProgramData\Anaconda3\Library\bin;C:\ProgramData\Anaconda3\Scripts;C:\ProgramData\Anaconda3\bin;C:\ProgramData\Anaconda3\condabin;C:\Python\Scripts;C:\Python;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0;C:\windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files\nodejs;C:\Program Files\Microsoft VS Code\bin;C:\Users\saish\AppData\Local\Programs\Python\Python38;C:\Program Files\Java\jre1.8.0_301\bin;C:\apache-zookeeper-3.7.0\bin;C:\Spark\spark-3.0.2-bin-hadoop2.7\bin;C:\hadoop\bin;C:\Users\saish\AppData\Local\Microsoft\WindowsApps;C:\Users\saish\AppData\Roaming\np
where python command returns
C:\ProgramData\Anaconda3\python.exe
C:\Users\saish\AppData\Local\Microsoft\WindowsApps\python.exe
Please suggest any new measures other than the ones I have mentioned. Thanks in advance
Per this github issue, you may have a conflict between dependencies of packages anaconda installed and the one you installed manually. Check your pythonpath and see if removing the pip folder from the pythonpath fixes the issue.
I have been trying to get the gdal library work using Python 2.7 and Anaconda in Windows 8 environment.
Besides gdal, I have also installed libgdal (frankly, I don't really understand the difference between the two). I now seem to have gdal 2.1.0 and 2.0.2 as well as libgdal 2.1.0.
However, when I run my Py code, there is a gdal error:
'gdalwarp' is not recognized as an internal or external command,
operable program or batch file.
I have already set the GDAL_DATA environmental variable to point to
C:\Anaconda\pkgs\libgdal-2.1.0-vc9_0\Library\share\gdal
I have also added a path, although I am not entirely sure where this should point to:
C:\Anaconda\pkgs\libgdal-2.1.0-vc9_0\Library\bin
I have tried the same with gdal 2.0.2 without success. gdalwarp.exe does seem to exist under libgdal 2.1.0 and gdal 2.0.2.
Any ideas? Is there an issue with the installation or have I not set the environmental variables correctly?
FYI, I have tried various installation commands, notably:
conda install gdal
conda install -c conda-forge gdal
conda install -c anaconda gdal
Addendum: I have found a manual solution: I set the GDAL_DATA and PATH variables in the terminal (pointing to libgdal 2.1.0) before running the code...
However, there is still an issue when I run my Py code: it is supposed to convert a tiff file to shp with gdal_polygonize:
cmd = 'gdal_polygonize.py %s -f "ESRI Shapefile" %s'%(dst_tif, dst_shp)
There is no error but the shapefile is not created (which leads to an error later on in the code). Any ideas as to why gdal is still not working correctly?
I have tried pointing the env variables to osgeo:
set PATH=%PATH%;C:\Anaconda2\Lib\site-packages\osgeo\scripts
set GDAL_DATA=C:\Anaconda2\Lib\site-packages\osgeo\data\gdal
Gdalinfo works but the gdal_polygonize used in my Py code does not appear to work.
The key is the activation script which is (potentially) executed when activating the environment. Not every GDAL build for Conda contains this. In my experience recent Conda-Forge builds are really good.
With your requirements of py27 and GDAL 2.1 i can get it working by following these steps:
1) Create a new environment: conda create -n gdaltest python=2.7
2) Activate: activate gdaltest
3) Install GDAL: conda install gdal=2.1 -c conda-forge
4) Reactivate environment: deactivate + activate gdaltest
This forces the just installed activation script to be executed, this sets the environment variables.
If i start python and run os.system("gdalinfo"), i can see its picked up correctly. And running os.environ['GDAL_DATA'] confirms the path is set correctly.
You can view the (de)activation script yourself at:
C:\Miniconda3\envs\<env name>\etc\conda\activate.d\gdal-activate.bat
A few years ago this didn't work as well as it does today, so make sure you have a recent Conda version (4.3.x) etc.
The benefit of this method is, that when switching environments, your paths are also changed accordingly. A "hard coded" GDAL_DATA path could potentially cause some compatibility issues if you mix and match different GDAL versions (although normally is should work OK).
I had python 2.7 before and then I installed python 3.4.The OS is windows 10
I have renamed
C:\python27\python.exe to python2.exe (when I run python2 --version it shows correct version)
and
C:\python34\python.exe to python3.exe (when I run python3 --version it shows correct version)
I have set the path variable manually and there is no space etc.
I was trying to create a virtual environment and assign python34 to this new environment.
I was going through this SO reference -- Using VirtualEnv with multiple Python versions on windows
prompt>> virtualenv -p c:\Python34\python3.exe casenv
But I got an error--
Fatal error in launcher: Unable to create process using '"'
Do I need to install virtualenv again for python34 or somewhere I need to set virtualenv path for each python installation.
Any help is highly welcomed.
In my case, i had installed python 3.6 and uninstalled python 2.7 when i got this error.
Completely deleting the C:\Python2.7 directory did the trick.
This error is usually caused because of python directory of different versions stored at same location.
i.e in my case I was using python 3.5.X for development and when I updated to 3.7.6 I got this error.
People on internet suggest that it is because of pip but main cause is 2 or more python directory.
The following steps should fix it:
Uninstall previous python version (or use virtual environment if you want to play with multiple python version)
Delete the python directory you are not using (as it causes confusion for terminal to understand which python path it should pick to execute the command)
and this should fix the error of
fatal error in launcher unable to create process using ' '
Pip version: 10.0.0
Python version: 3.6.5 64 bit
Operating system: Windows 7 Ultimate, Service Pack 1, 64-bit
Description:
After upgrading pip to the version 10.0.0 (from Pycharm, that is using pip as a package) any attempts to start updated pip cause an error:
Fatal error in launcher: Unable to create process using '""c:\program files\python 3.6\python.exe" "C:\Program Files\Python 3.6\Scripts\pip.EXE"'
Command python -m pip works as expected.
I found text "Fatal error in launcher" only in executables:
src\pip_vendor\distlib\t32.exe
src\pip_vendor\distlib\t64.exe
and in the pip.exe itself.
After
python -m pip uninstall pip
easy_install.exe pip
error disappeared.
It is interesting, that initially pip.exe had almost the same size as t64.exe, now it significantly shorter.
If someone came after installing a newer version like 3.X and uninstalled the older version, what you need to do is to delete the old version's folder from C Drive.
Clean Fix (Windows)
The fastest way to fix the issue you were facing is to uninstall and reinstall.
Why it happened?
You probably moved the directory where python was installed.
You probably have both environmental variables listed in Environmental Variables.
Things to consider
You can only use 1 active version of python at a time if you use the MSI installer.
If you downloaded the zip file of Python, you can have unlimited versions in your computer BUT you can only have 1 active version under Environmental Variables.
You can always use any version of Python explicitly by writing the direct path to the specific location of the version of Python.
C:\Users\%USER%>conda info
Current conda install:
platform : win-32
conda version : 3.16.0
conda-build version : not installed
python version : 2.7.10.final.0
requests version : 2.7.0
root environment : C:\Users\%USER%\Miniconda (writable)
default environment : C:\Users\%USER%\Miniconda
envs directories : C:\Users\%USER%\Miniconda\envs
package cache : C:\Users\%USER%\Miniconda\pkgs
channel URLs : https://repo.continuum.io/pkgs/free/win-32/
https://repo.continuum.io/pkgs/free/noarch/
https://repo.continuum.io/pkgs/pro/win-32/
https://repo.continuum.io/pkgs/pro/noarch/
config file : None
is foreign system : True
# NOTE:
# root directory 'C:\Users\%USER%\Miniconda' is uninitialized
I see my root directory is not initialized.
Additionally when I try to install a package (pandas eg) I get the following error:
C:\Users\%USER%>conda install pandas
Error: This installation of conda is not initialized. Use 'conda create -n
envname' to create a conda environment and 'source activate envname' to
activate it.
# Note that pip installing conda is not the recommended way for setting up your
# system. The recommended way for setting up a conda system is by installing
# Miniconda, see: http://repo.continuum.io/miniconda/index.html
I assume they are related but I am not sure the course of action.
I had anaconda/python27 up and running but wanted to update matplotlib and thought to reinstall python with conda to be "up to date".
The error is documented here, but to be honest I do not really get it.
I regret this as it is a bit tough to get up and running again!
I had a similar problem, but with Anaconda on Windows 8.1.
The python env variables are set from a previous python install.
The installer did not update (user)PYTHONHOME, (system)PYTHON_DIR, and (system)PYTHONPATH, so I manually set them to /Users/me/Anaconda/.
conda update conda
gave the error mentioned above. I added a new conda environment...
conda create -n notebook jupyter
activate notebook
which succeeded, but...
conda info --envs
...gives...
notebook C:\Users\<me>\Anaconda\envs\notebook
root * C:\Users\<me>\Anaconda
...and...
conda info
...
# NOTE: root directory 'C:\Users\me\Anaconda' is uninitialized.
I suspect that the installer failed due to the presence of the environment variables. I deleted the environment variables and the /Users/me/Anaconda directory, then installed miniconda.
All seems to be well now.
Note:
I had previously installed python at least three different ways.
{Chocolatey, Anaconda(all)[failed], python msi}