[issue33890] Pathlib does not compare Windows and MinGW paths as equal
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 bug, because it's the same bug but 3 different writings and pathlib is not able to identify the equality. Environment: Windows 10 Latest MinGW identified in Python 3.6.2 as MINGW64_NT-10.0 Question on Stack Overflow: https://stackoverflow.com/questions/50900779/how-to-compare-absolute-windows-and-mingw-paths-with-pathlib -- components: Windows messages: 319832 nosy: Patrick Lehmann, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Pathlib does not compare Windows and MinGW paths as equal type: behavior versions: Python 3.6 ___ Python tracker <https://bugs.python.org/issue33890> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in the standard library
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/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in the standard library
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/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33890] Pathlib does not compare Windows and MinGW paths as equal
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() to solve this problem. pathlib just needs to detect the environment and then it needs to extend its understanding of equal in MinGW and Cygwin that C:\ is equal to /c/. That's not a big deal. Do I realy need to register in a heavy overloaded mailing list for such a simple fix? This will take months to implement and deploy... Python is now on GitHub, why can't we use an issue as any other open source project does? What is a "MinGW facility"? -- ___ Python tracker <https://bugs.python.org/issue33890> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in the standard library docstrings
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 <https://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
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 these messages: D:\git\PoC\py\lib\ExtendedConfigParser\__init__.py:docstring of lib.ExtendedConfigParser.ExtendedConfigParser.read_file:3: WARNING: Inline interpreted text or phrase reference start-str ing without end-string. Note: ExtendedConfigParser is class derived from configparser.ConfigParser. Inherited methods get documented too. Btw. I have some improvements for this class, how can I contribute them? Who is the maintainer for this class? Please contact me: patrick.lehm...@tu-dresden.de The improved version is available at GitHub: https://github.com/Paebbels/ExtendedConfigParser?ts=2 -- assignee: docs@python components: Documentation messages: 280907 nosy: Patrick Lehmann, docs@python priority: normal severity: normal status: open title: Sphinx incompatible markup in configparser.ConfigParser. versions: Python 3.4, Python 3.5 ___ Python tracker <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
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 tracker <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
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/docstring_markup.patch ___ Python tracker <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
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 around 139 matches in the whole CPython repository. I found some of these markup in non docstring strings, which I reverted as far as I found them by manually reviewing all changed files. For a colored diff, see my Git branch: https://github.com/Paebbels/cpython/commit/6d3f348f71b5b0ae9fbfcb8fdbba72dc5fac428a?ts=2 There is also a PR-, commit-, and line-based comment feature box GitHub. How you solve it is up to you, but I would like to get rid of hundreds of warnings in my Sphinx runs, when modules are inherting code (and docstrings) from Python. Kind regards Patrick -- ___ Python tracker <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
Patrick Lehmann added the comment: I signed the CLA. -- ___ Python tracker <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28710] Sphinx incompatible markup in configparser.ConfigParser.
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 <http://bugs.python.org/issue28710> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
