Skip to content

remote.py: Denote optional parameters as such#519

Merged
jdavid merged 1 commit intolibgit2:masterfrom
rmoehn:optional-args
May 3, 2015
Merged

remote.py: Denote optional parameters as such#519
jdavid merged 1 commit intolibgit2:masterfrom
rmoehn:optional-args

Conversation

@rmoehn
Copy link
Contributor

@rmoehn rmoehn commented Apr 22, 2015

In the online documentation to Pygit2 it was not visible that (some of)
the parameters to Remote.fetch() and Remote.push() were optional. Fix
this. (I'm not sure if the way I did it is the idiomatic way of marking
a parameter optional in Python docstrings.)

In the online documentation to Pygit2 it was not visible that (some of)
the parameters to Remote.fetch() and Remote.push() were optional. Fix
this. (I'm not sure if the way I did it is the idiomatic way of marking
a parameter optional in Python docstrings.)
@jdavid jdavid merged commit 7a64658 into libgit2:master May 3, 2015
@jdavid
Copy link
Member

jdavid commented May 3, 2015

Actually signatures only need to be defined in C code, it works automatically for Python files. So to reduce development/maintenance costs and improve coherence of the documentation I went through the Python files and removed manually defined signatures from the docstrings.

See commit deb5053

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants