[QGIS-Developer] Keyword args for python bindings?

[Luigi Pirelli]

+++1
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 2nd Edition:
* https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
**************************************************************************************************


On 22 June 2017 at 04:33, Nyall Dawson <nyall.dawson at gmail.com> wrote:
> Hi all,
>
> Been thinking about this lately, with all the excellent work which is
> being done on sipify and improving the usability of the PyQGIS through
> docstrings and such... do we want to also turn on named argument
> support for PyQGIS methods?
>
> I gather it's just a matter of adding the annotation KeywordArgs=All
> to function definitions. We should be able to code this into sipify to
> handle this automatically.
>
> I'd see the big benefit here would be readability of python code - no
> more someMethod( True,False, 5, None) deciphering!
>
> The downside would be that the argument names would become part of
> stable API. We've still gots lots of unhelpful argument names (things
> like 's', 'c',.... ), so that's a potential downside if these get
> locked in (although maybe we can fix them before freeze).
>
> Thoughts?
> Nyall
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer