You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope this is the right place to ask - my apologies if it is not: I am currently running a QGIS Enhancement Proposal (QEP) for turning plugin management into actual package management. As part of this process, I am looking for existing QGIS plugins and plugin developers who could significantly benefit from the proposed ideas and concepts. In a nutshell, I am proposing to allow to package QGIS plugins as regular Python wheels and/or conda packages - with all relevant packaging features such as proper Python package dependencies and binary extensions. Looking at this project's source code, it appears to be a good candidate for greatly benefiting from such features. If you find this work interesting and potentially relevant for your plugin, I am rather curious about your opinion. Among other issues, there appears to be some serious doubt about the existence of actual use cases for the proposed changes in QGIS among its core developers. Besides, the proposed work may also "confuse plugin developers". Feedback is therefore highly welcome.
The text was updated successfully, but these errors were encountered:
I hope this is the right place to ask - my apologies if it is not: I am currently running a QGIS Enhancement Proposal (QEP) for turning plugin management into actual package management. As part of this process, I am looking for existing QGIS plugins and plugin developers who could significantly benefit from the proposed ideas and concepts. In a nutshell, I am proposing to allow to package QGIS plugins as regular Python wheels and/or conda packages - with all relevant packaging features such as proper Python package dependencies and binary extensions. Looking at this project's source code, it appears to be a good candidate for greatly benefiting from such features. If you find this work interesting and potentially relevant for your plugin, I am rather curious about your opinion. Among other issues, there appears to be some serious doubt about the existence of actual use cases for the proposed changes in QGIS among its core developers. Besides, the proposed work may also "confuse plugin developers". Feedback is therefore highly welcome.
The text was updated successfully, but these errors were encountered: