[Qgis-developer] side effect of sextante renaming

2013-08-25 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subplugins are not working: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/qgis/utils.py", line 204, in startPlugin plugins[packageName] = package.classFactory(iface) File "/home/paolo/.qgis2/python/plugins/sextante

Re: [Qgis-developer] side effect of sextante renaming

2013-08-25 Thread Nathan Woodrow
I would say having an alias isn't going to hurt. For me that would also be good as it would allow old code to keep working without needing to do any updates. - Nathan On Sun, Aug 25, 2013 at 7:15 PM, Paolo Cavallini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Subplugins are not

Re: [Qgis-developer] side effect of sextante renaming

2013-08-25 Thread Albin Blaschka
Am 2013-08-25 11:19, schrieb Nathan Woodrow: I would say having an alias isn't going to hurt. For me that would also be good as it would allow old code to keep working without needing to do any updates. - Nathan Hello! The Semi-Automatic Classification Plugin is also affected, BTW... http

Re: [Qgis-developer] side effect of sextante renaming

2013-08-25 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 25/08/2013 11:38, Albin Blaschka ha scritto: > The Semi-Automatic Classification Plugin is also affected, BTW... > > http://fromgistors.blogspot.co.at/p/semi-automatic-classification-plugin.html I guess all of them are: http://hub.qgis.org/issues

Re: [Qgis-developer] side effect of sextante renaming

2013-08-25 Thread Victor Olaya
The alias is not a bad idea, but, how many such plugins exist? 4? 5?. It's pretty easy to rename and adapt them, and then we leave no traces of sextante imports in their code, which will make them probably easier to understand, mantain, etc Can be call plugin devs and tell them to adapt them (just