[QGIS-Developer] Embedded py libs in plugis
Paolo Cavallini
cavallini at faunalia.it
Tue Apr 30 10:26:34 PDT 2019
Hi all,
thanks for comments. We have always encouraged devs to use shared libs,
and to declare dependencies in metadata. I see two problems in letting
anybody including wildly:
* code duplication: with hundreds of plugins, reinstalling the same
libraries over and over, possibly in different versions, does not look
the Right Thing To Do to me; when needed, commonly used libs have been
included (thanks Juerghen!) in osgeo4w standalone installer, a much
cleaner solution IMHO; of course, in Linux this would only be a burden
with no significant advantages. In addition, this encourages devs to
take shortcuts, patching and forking libs, including older versions
instead of upgrading, etc.; to me this sounds a bit like windows vs
linux approach
* licences: I should check then the licences of all the libraries
embedded, that often do not include a LICENCE file.
Cheers.
On 30/04/19 18:31, Etienne Trimaille wrote:
> Nothing is written in the documentation about not embedding python
> libraries:
> https://plugins.qgis.org/publish/
>
> Le mar. 30 avr. 2019 à 18:17, Matthias Kuhn <matthias at opengis.ch
> <mailto:matthias at opengis.ch>> a écrit :
>
> Hi,
>
> I also was under the impression that this it's ok to ship
> dependencies within plugins.
>
> One of the major blockers towards a better world (TM) is that no
> pip(-like) tool to auto-install dependency packages at runtime is
> available on all platforms (looking at you, Windows). Meanwhile
> shipping dep libraries as wheels/eggs/... sounds like the best user
> experience a plugin dev can deliver.
>
> Regards
>
> Matthias
>
> On 4/30/19 6:11 PM, Tim Sutton wrote:
>> Hi
>>
>> Yeah I also don’t remember any specific policy discouraging it,
>> and as long as they are namespaces nicely it is nicer IMHO than
>> requiring users to go and manually fetch extra packages so your
>> plugin will work.
>>
>> Regards
>>
>> Tim
>>
>>> On 30 Apr 2019, at 16:57, Luigi Pirelli <luipir at gmail.com
>>> <mailto:luipir at gmail.com>> wrote:
>>>
>>> Are you sure? or are you referring embedding binary library? pure
>>> python lib or python eggs, IMHO do not generate problems if used
>>> in the plugin code without modify pythonpath for the all the env.
>>>
>>> Am I wrong?
>>>
>>> Luigi Pirelli
>>>
>>> **************************************************************************************************
>>> * LinkedIn: https://www.linkedin.com/in/luigipirelli
>>> * Stackexchange:
>>> http://gis.stackexchange.com/users/19667/luigi-pirelli
>>> * GitHub: https://github.com/luipir
>>> * Mastering QGIS 2nd Edition:
>>> *
>>> https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
>>> * Hire me: http://goo.gl/BYRQKg
>>> **************************************************************************************************
>>>
>>>
>>> On Mon, 29 Apr 2019 at 20:50, Paolo Cavallini
>>> <cavallini at faunalia.it <mailto:cavallini at faunalia.it>> wrote:
>>>
>>> Hi all,
>>> until now we discouraged the inclusion of external python
>>> libraries in
>>> python plugins. I still think this is the right, clean
>>> approach. I just
>>> want to check with main core devs if there are strong reasons
>>> to change
>>> the approach.
>>> Thanks for comments.
>>> Cheers.
>>> --
>>> Paolo Cavallini - www.faunalia.eu <http://www.faunalia.eu/>
>>> QGIS.ORG <http://qgis.org/> Chair:
>>> http://planet.qgis.org/planet/user/28/tag/qgis%20board/
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer at lists.osgeo.org
>>> <mailto:QGIS-Developer at lists.osgeo.org>
>>> List info:
>>> https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe:
>>> https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer at lists.osgeo.org
>>> <mailto:QGIS-Developer at lists.osgeo.org>
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>> —
>>
>>
>>
>>
>>
>>
>>
>>
>> *Tim Sutton*
>>
>> *Co-founder:* Kartoza
>> *Ex Project chair:* QGIS.org <http://QGIS.org>
>>
>> Visit http://kartoza.com <http://kartoza.com/> to find out about
>> open source:
>>
>> Desktop GIS programming services
>> Geospatial web development
>> GIS Training
>> Consulting Services
>>
>> *Skype*: timlinux
>> *IRC:* timlinux on #qgis at freenode.net <http://freenode.net>
>>
>> I'd love to connect. Here's my calendar link
>> <https://calendly.com/timlinux> to make finding time easy.
>>
>>
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org <mailto:QGIS-Developer at lists.osgeo.org>
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> --
> Matthias Kuhn
> matthias at opengis.ch <mailto:matthias at opengis.ch>
> +41 (0)76 435 67 63 <tel:+41764356763>
> OPENGIS.ch Logo <http://www.opengis.ch>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org <mailto:QGIS-Developer at lists.osgeo.org>
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
--
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
More information about the QGIS-Developer
mailing list