[issue28710] Sphinx incompatible markup in the standard library docstrings

2018-06-18 Thread Patrick Lehmann
Patrick Lehmann added the comment: Having single quotes in docstrings is also ok for Sphinx documentation. Btw. ReStructured text (docutils) was invented to document Python sources, why is it not used by Python? -- ___ Python tracker <ht

[issue33890] Pathlib does not compare Windows and MinGW paths as equal

2018-06-17 Thread Patrick Lehmann
Patrick Lehmann added the comment: I don't think is cross-platform, because I'm still on Windows but in different shells. More over, pathlib currently support cross-platform comparison. I can save a configuration file on Linux and open it on Windows with such paths. I use myPath.as_posix

[issue28710] Sphinx incompatible markup in the standard library

2018-06-17 Thread Patrick Lehmann
Patrick Lehmann added the comment: Against what branch should I create the PR? I was a huge number of changes. I think I'll create multiple PRs to ease the review. -- ___ Python tracker <https://bugs.python.org/issue28

[issue28710] Sphinx incompatible markup in the standard library

2018-06-17 Thread Patrick Lehmann
Patrick Lehmann added the comment: Any progress on that issue? 1.5 years passed by and it should be possible to fix the Python documentation in that time, right? -- ___ Python tracker <https://bugs.python.org/issue28

[issue33890] Pathlib does not compare Windows and MinGW paths as equal

2018-06-17 Thread Patrick Lehmann
New submission from Patrick Lehmann : pathlib does not compare absolute paths from Windows and MinGW as equal. Windows absolute path: "C:\path\to\tool" MinGW absolute path: "/c/path/to/tool" Cygwin absolute path: "/cygdrive/c/path/to/tool" I consider this a

[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 <rep...@bugs.python.org>

[issue28710] Sphinx incompatible markup in configparser.ConfigParser.

2016-11-18 Thread Patrick Lehmann
Patrick Lehmann added the comment: I signed the CLA. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28710> ___ ___ Pyth

[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

[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/fil

[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

[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