Why not just hide it using Python method overriding: QgsVectorLayer.attributeMap = QgsVectorLayer.attributes
Then you can just call attributesMap()[] and it will call QgsVectorLayer.attributes for you. - Nathan On Tue, Feb 19, 2013 at 8:53 PM, Victor Olaya <[email protected]> wrote: > The ideas in the document that Richard mentions, about how to make it > compatible for both versions, are maybe a better idea. I do not know > if a maximum version can be set in the plugin metadata. :-( > > Regards > Victor > > 2013/2/19 Sandro Santilli <[email protected]>: > > On Tue, Feb 19, 2013 at 11:36:13AM +0100, Victor Olaya wrote: > >> I faced the same problem with SEXTANTE (and there were a large number > >> of calls to replace), and decided to go ahead and break compatibility > >> with 1.8. Should be better in the mid-term, but it's true that it is > >> not nice to leave a plugin depending now on an yet-unreleased > >> version... > >> > >> If it is not a big work, maybe you can keep two versions, more or less > >> synchronized > > > > I can try that. How do I encode that one version does NOT work > > with a newer QGIS ? > > > > I see there's a qgisMinimumVersion setting, > > is there also a qgisMaximumVersion ? Would it be used by plugin fetcher ? > > > > --strk; > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
