https://issues.qgis.org/https://issues.qgis.org/favicon.ico2014-05-24T18:06:53ZQGIS Issue TrackingQGIS Application - Feature request #10341: New Plug-in and dependencies. https://issues.qgis.org/issues/10341?journal_id=510322014-05-24T18:06:53ZEtienne Tourigny
<ul></ul><p>This is probably better off in the plugin's bug tracker or contacting the plugin author. By the way you don't even name this plugin.</p> QGIS Application - Feature request #10341: New Plug-in and dependencies. https://issues.qgis.org/issues/10341?journal_id=510442014-05-25T03:14:04ZRhenriques Henriques
<ul></ul><p>The plug-in is called SimpliPy. Beyond this particular plug-in problem, interpret my message as a suggestion for a better plug-in management system in QGIS. It's already great "as is" but it could be even better if there was a simple system for manage dependencies. <br />Best Regards</p> QGIS Application - Feature request #10341: New Plug-in and dependencies. https://issues.qgis.org/issues/10341?journal_id=510792014-05-26T01:39:09ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Resolution</strong> set to <i>invalid</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Rejected</i></li></ul><p>Issues for 3rd party plugins are to be reported in the tracker defined by the developer, in this case the link is in the plugin detail in the qgis plugin manager:</p>
<p><a class="external" href="https://github.com/albertferras/simplipy/issues">https://github.com/albertferras/simplipy/issues</a></p>
<p>About dependencies:</p>
<p>the error you posted seems more an error than a real python dependency. Anyway: the most common dependencies (scipy, matplotlib, etc.) are bundled into Windows installers, on Linux and OsX I guess it is better to handle them as usual, at a system level.</p> QGIS Application - Feature request #10341: New Plug-in and dependencies. https://issues.qgis.org/issues/10341?journal_id=511212014-05-26T12:11:27ZAlbert Ferras
<ul></ul><p>Hi I'm the creator of that plugin. This was a mistake I made when releasing the first version of the plugin, that I forgot to delete some debugging file that I was using. If you update your plugin to 0.2.1 it shouldn't complain again about this.</p>