[Qgis-developer] standard way for custom plugin python dependencies

[Luigi Pirelli]

why not package critical/missing dep with the plugin itself? import
from local egg only if not present in the installation.
Luigi Pirelli

**************************************************************************************************
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS:
https://www.packtpub.com/application-development/mastering-qgis
**************************************************************************************************


On 22 September 2016 at 14:08, Jachym Cepicky <jachym.cepicky at gmail.com> wrote:
> Hi all,
>
> we've developed an (python) plugin for QGIS, which is somehow using (among
> others) nice "requests" python library. We use it the standard way
>
> import requests
>
> But when we distributed the plugin to other computers, it turned out, they
> do not have it installed.
>
> Is there any standard way, how to distribute dependencies along with python
> plugin? Something in metadata.txt? Some requirements file?
>
> Thanks
>
> Jachym
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer