[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-20 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-20 Thread Patrick Lehmann
Patrick Lehmann added the comment: I also found some docstrings using double back-tick plus double single quotes. For example: ``x.y = v'' in builtins.py in function setattr(...). -- ___ Python tracker ___

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-18 Thread Patrick Lehmann
Patrick Lehmann added the comment: I signed the CLA. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-18 Thread Patrick Lehmann
Patrick Lehmann added the comment: Hello, I used this regexp on all files: -- match pattern: `([A-Za-z0-9_]+)' replace pattern ``\1`` -- I assumed that only identifiers where quoted in such way. I think my editor found arou

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-18 Thread R. David Murray
R. David Murray added the comment: I think that we do not generally use ReST markup in our docstrings. So replacing `x' with 'x' would be more correct, I think. In many cases the quotes could just be omitted entirely. The patch command says: patch unexpectedly ends in middle of line pat

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-18 Thread Terry J. Reedy
Terry J. Reedy added the comment: As far as I looked, the patch changes `xyz' in docstrings and quotes to ``xyz``. A rst expert should verify that this is correct. In printed strings, `zyz' is changed to 'xyz', which I consider to be correct. Before applying this, I would want to review in R

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-16 Thread Patrick Lehmann
Patrick Lehmann added the comment: Here is the patch file created with: PS> git diff > docstring_markup.patch This patchfile effects all files with this markup in the CPython repository. Kind regards Patrick -- keywords: +patch Added file: http://bugs.python.org/file45515/docstrin

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-16 Thread R. David Murray
R. David Murray added the comment: We will accept github pull requests in the future (the transition is underway). For now, you can create a diff file (using hg diff by preference, but git diff will work) and uploaded it to the issue. For this issue, please only upload the docstring changes.

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-16 Thread Patrick Lehmann
Patrick Lehmann added the comment: How can I supply a fix? I have a branch with lots of fixes. https://github.com/Paebbels/cpython/tree/paebbels/issue-28710?ts=2 Why don't you accept pull requests via GitHub? Kind regards Patrick -- ___ Python

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-15 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- keywords: +easy stage: -> needs patch versions: +Python 2.7, Python 3.6, Python 3.7 -Python 3.4 ___ Python tracker ___ _

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-15 Thread Patrick Lehmann
New submission from Patrick Lehmann: Why does e.g. configparser.ConfigParser contain doc strings with Sphinx incompatible markup? The markup starts with back-tick, but ends with a single quote. Example: https://github.com/python/cpython/blob/master/Lib/configparser.py?ts=2#L26 Sphinx writes t