-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conda path #6
Comments
There is an If we want a better integration of conda for plugin dependencies, I think we should do something like qgis/QGIS-Enhancement-Proposals#202 or https://github.com/opengisch/qpip, where plugins can add a requirements.txt and we could ship a dedicated conda backend to install these. |
Thanks for the input. Personally it would be great if we had access to conda here. My system conda install is not seeing the QGIS venv. I assume I can activate it with (having said that, I was quite surprised to see most of my dependencies install without issues with the QGIS pip here) As for plugin dependencies, I agree that this should be up to plugin publishers who will simply use pip, but they too sometimes have to either provide instructions for custom installs, or produce hackish scripts for some edge cases (for instance, we added behaviour in our plugin to install miniconda in a custom folder just to add 'triangle' which tends to trip pip). |
An update on this. Could be worth exploring installing the venv somewhere outside the QGIS.app package (Lib/App Support or ~/.config maybe?), and add a menu item or an option on the installer to delete that location for those who need a clean install. |
I think ideally the venv would go into the profile folder (i.e. you can have one venv per profile, just like plugins), just like done with qpip listed above |
That is a great idea. The only issue I can see is what happens when you change profiles. QGIS will pick up the new folder for packages, but will it also activate the new venv (with all the new c library paths)? |
C libraries are always a tricky topic, however, I think it boils down to this:
|
I similarly chose the default, not a specific drive, and cannot find the install directory to activate the env. I ran a search on my file system for Contents directory and found some related to other apps (like mito) but not for QGIS. I'm still a relative newb at the nuances of venv's and have very little conda env experience. Mostly use pipenv - when it works. I will re-install into a specific folder but I wanted to capture the experience here. |
I nearly always struggle with environments. I'm pretty sure these are operator errors (mine) but I don't seem to have the env set up right. When I right click and "open" the QGIS3.32.app application I get this error: Traceback (most recent call last): Python version: QGIS version: Python path: |
So, I re-installed miniconda. created an env. Tried to run the app from the command line: |
Then, with the new install of minconda, I tried to open the QGIS3.32.app and QGIS quit on me. Error file attached. |
Next I tried a conda install from a new conda env. This completed: |
Hi @tsmcgrath I think you are getting qgis for conda (developed here: https://github.com/conda-forge/qgis-feedstock) and the new qgis installer (this repository, and which happens to be based on conda) confused. The first one is installed through conda like you just did, and is launched through the terminal by activating the qgis conda environment and typing The error message message you described is an issue that is common to both versions and being tracked in their respective repositories. |
Hi @joaoponceleao You're correct. I did confuse them. I'll try again with just the pkg. |
This is the error I get when I open it. Installed to applications folder. Somehow I have a permissions error to sort out. There is read/write on the app file. The Lima splash screen comes up. Then this pops up: Traceback (most recent call last): Python version: QGIS version: Python path: |
Ok, got it working. Somehow an "allow" screen didn't show up for me before the error. 2nd time it did. Set to "Always allow". |
So far testing is going well. It's more than 3x faster than the Rosetta version I was using (3.30.3). Well done @m-kuhn! I do still get a PATH error which I think is a conflict with the previous conda installs I did. I will try to get rid of that version and see if it clears up the error. But, the error doesn't stop the app from launching. The error I'm seeing. Traceback (most recent call last): Python version: QGIS version: Python path: |
Hi.
Thanks for the new installer.
I can see pip3 in the Contents/bin folder, but I can't see where the conda env is to activate it. How does one install new packages for plugins? I assume conda would be preferred over pip here (I realise plugins will call pip anyway).
On a related note, please consider pinning any relevant conda packages to prevent dependency issues when installing or updating extra plugin dependencies.
The text was updated successfully, but these errors were encountered: