[Qgis-developer] Processing subplugins broken on master?
volayaf at gmail.com
Mon Jul 28 02:35:06 PDT 2014
Great idea. I will try to do that for all the modules/packages that have
changed. Thanks for the suggestion!
2014-07-26 0:33 GMT+02:00 Nathan Woodrow <madmanwoo at gmail.com>:
> We need to be careful because now processing is core it is really part of
> the API and we really shouldnt be breaking that. As such I think you should
> just redirect the module so old code still works.
> You can just do something like this in __init__.py for processing
> Import processing.core.output
> Output = processing.core.output
> So when you import processing and call output it really calls the new
> On Jul 26, 2014 3:04 AM, "Victor Olaya" <volayaf at gmail.com> wrote:
>> Yes, it is supposed to stay. The refactoring was made to have a more
>> consistent structure, so we should keep it like that.
>> Let me know if you need help with that, although, as Alex say, it
>> shouldn't be too difficult to adapt
>> 2014-07-25 16:48 GMT+02:00 Paolo Cavallini <cavallini at faunalia.it>:
>>> Il 25/07/2014 16:40, Alexander Bruy ha scritto:
>>> > seems this is result of the huge refactoring of inputs and outputs.
>>> > Now all inputs are in processing.core.parameters and all outputs in
>>> > processing.core.outputs packages.
>>> > So fixing this is trivial task, just adjust import clauses
>>> Yes, that's what I understood. Will this syntax stay? If so, I can open
>>> tickets, possibly PRs, on the involved plugins.
>>> Paolo Cavallini - www.faunalia.eu
>>> Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
>>> Qgis-developer mailing list
>>> Qgis-developer at lists.osgeo.org
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qgis-developer