Skip to content
This repository has been archived by the owner. It is now read-only.

Fix XXX docstrings #83

Closed
GoogleCodeExporter opened this issue Apr 10, 2015 · 3 comments
Closed

Fix XXX docstrings #83

GoogleCodeExporter opened this issue Apr 10, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Apr 10, 2015

A lot of docstrings are still """XXX""". Fix these.

Original issue reported on code.google.com by gvanrossum@gmail.com on 25 Oct 2013 at 12:41

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 10, 2015

Some docstrings have been filled in changeset 69047a75b091 (CPython issue 
#21252).

Here is a patch to fill more XXX docstrings:
http://codereview.appspot.com/108750043

Original comment by victor.s...@gmail.com on 5 Jun 2014 at 10:17

Loading

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 10, 2015

Patch commited into Tulip (71fd976b56fe), Python 3.4 (aaee7df990a2) and Python 
3.5 (493d1ae3227b).

Original comment by victor.s...@gmail.com on 19 Jun 2014 at 3:14

Loading

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 10, 2015

Remainding XXX docstrings are less important, I consider that the issue can now 
be fixed.

Don't hesitate to send patches to fix remaining XXX doctrings and enhance the 
doc ;-)

Original comment by victor.s...@gmail.com on 19 Jun 2014 at 3:16

  • Changed state: Fixed

Loading

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant