Mailman 3 April 2020 - docs

[issue40269] Inconsistent complex behavior with (-1j)
by Serhiy Storchaka 13 Apr '20

13 Apr '20

Serhiy Storchaka <storchaka+cpython(a)gmail.com> added the comment: The Imaginary type could help to solve other "gotchas". For example, in Python >>> complex(0, float('inf')) * 1 (nan+infj) But in C++ you will get the real component 0, because multiplication of complex and real numbers is component wise. With the Imaginary type we could get that 1j * x == complex(0, x) for all float x, including infinity and NaN. Returning to the repr, the other way to correctly represent the repr of complex(-0.0, 1.0) is writing it as "-(0.0-1j)", but it looks unnatural to me. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40269> _______________________________________

1 0

[issue40269] Inconsistent complex behavior with (-1j)
by Mark Dickinson 13 Apr '20

13 Apr '20

Mark Dickinson <dickinsm(a)gmail.com> added the comment: See also #25839, #22548; there's lot of discussion of the core issue on those tickets. As Serhiy says, the only reasonable "true" fix would be to have 1j be a genuine imaginary literal, but that's a lot of work and potential disruption (not just to core Python, but to 3rd party libraries that care about complex numbers) for not a lot of gain. A documentation improvement as suggested by Raymond sounds good. I'm not keen on messing with the complex __repr__ again, but if we did, I'd propose not only representing real and imaginary parts in a way that's consistent with floats (so with both real and imaginary parts having either decimal points or exponents), but also showing _both_ the real and imaginary parts in all complex numbers. That is: >>> 1j 0.0 + 1.0j Or if we're willing to accept more backwards compatibility breakage, there's a case for having the __repr__ (but not the __str__) of a complex number take the form >>> 1j complex(0.0, 1.0) since this the only way that allows easy round-tripping. Otherwise you still have this problem: >>> complex(-0.0, 1.0) (-0+1j) >>> -0 + 1j 1j BTW, I still dislike the parentheses around the current complex repr. Let's keep this issue open for potential documentation improvements. If we want to change the repr of complex, let's open another issue for that. ---------- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python type: behavior -> enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40269> _______________________________________

1 0

[issue13743] xml.dom.minidom.Document class is not documented
by Sandro Tosi 12 Apr '20

12 Apr '20

New submission from Sandro Tosi <sandro.tosi(a)gmail.com>: Hello, following up http://mail.python.org/pipermail/docs/2012-January/007026.html I noticed the whole Document class (and relative methods) is not documented. Maybe it is a choice to not document it, or maybe it's just a missing doc, dunno, the's why I'm opening this :) ---------- assignee: docs@python components: Documentation messages: 150935 nosy: docs@python, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: xml.dom.minidom.Document class is not documented versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13743> _______________________________________

6 9

[issue21760] inspect documentation describes module type inaccurately
by Eric Snow 11 Apr '20

11 Apr '20

New submission from Eric Snow: In the documentation for the inspect module, the module type is described with just 2 of its potential 7 attributes. The language reference[2] and importlib docs[3] both provide an accurate list of module attributes. Furthermore, the description for __file__ should be fixed. It should be clear that __file__ reflects the location from which the module was loaded, that location is not necessarily a filename, and the attribute may not exist if the module was not loaded from a specific location (e.g. builtin and frozen modules). The same goes for __cached__ [1] https://docs.python.org/dev/library/inspect.html#types-and-members [2] https://docs.python.org/3/reference/import.html#import-related-module-attri… [3] https://docs.python.org/3/library/importlib.html#importlib.machinery.Module… ---------- assignee: docs@python components: Documentation messages: 220576 nosy: docs@python, eric.snow priority: normal severity: normal stage: needs patch status: open title: inspect documentation describes module type inaccurately versions: Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21760> _______________________________________

4 5

About documentation
by jeevan Tutorial 11 Apr '20

11 Apr '20

Your documentation is very helpful.so I am thanking you to make the documentation.

1 0

[issue40249] __import__ doesn't honour globals
by Stefan Seefeld 11 Apr '20

11 Apr '20

Stefan Seefeld <stefan(a)seefeld.name> added the comment: OK, thanks for the clarification. I think this is obscure enough to warrant at least a paragraph or two to clarify the semantics of these arguments. I changed the issue "components" and "type" to reflect that. ---------- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python type: behavior -> enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40249> _______________________________________

1 0

[issue40205] Profile 'builtins' parameter documentation missing
by Bar Harel 11 Apr '20

11 Apr '20

New submission from Bar Harel <bzvi7919(a)gmail.com>: Profile and cProfile's documentation does not say anything about the builtins parameter. Also, it exists only on cProfile, which means Profile is not a drop-in replacement. Lastly, enable() method, that exists on cProfile, also accepts params, and are undocumented. ---------- assignee: docs@python components: Documentation, Library (Lib) messages: 365859 nosy: bar.harel, docs@python priority: normal severity: normal status: open title: Profile 'builtins' parameter documentation missing versions: Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40205> _______________________________________

2 1

[issue40197] Add microseconds to timing table in What's new python 3.8
by Morten Hels 11 Apr '20

11 Apr '20

New submission from Morten Hels <morten(a)hels.dk>: It is not immediately obvious to me what the units are in the timing table here: https://docs.python.org/3/whatsnew/3.8.html#demos-and-tools Clicking through to https://bugs.python.org/issue35884 shows that the unit is microseconds, but I think it would be helpful to many readers to put that information in the docs itself, e.g., "Here’s a summary of performance improvements since Python 3.3 (timings are in microseconds):" ---------- assignee: docs@python components: Demos and Tools, Documentation messages: 365823 nosy: docs@python, frozenpaving priority: normal severity: normal status: open title: Add microseconds to timing table in What's new python 3.8 type: enhancement versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40197> _______________________________________

5 11

[issue40245] Add description meta tags to docs.python.org
by Andrew Zhou 11 Apr '20

11 Apr '20

New submission from Andrew Zhou <andrewfzhou(a)gmail.com>: This isn't a particularly high priority, but it would be nice to have the first paragraph of docs pages show up when searched or posted in Slack, Discord, Twitter, etc. This is done through the description meta tag, as well as Open Graph, etc. As the description meta tag covers most of the potential use cases, the others can wait. What implementing this would entail is either manual addition of meta tags, or an automatic transform step that grabs the first paragraph of the relevant RST source. [1] http://www.sphinx-doc.org/en/master/extdev/appapi.html#sphinx.application.S… ---------- assignee: docs@python components: Documentation messages: 366138 nosy: 0az, docs@python priority: normal severity: normal status: open title: Add description meta tags to docs.python.org type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue40245> _______________________________________

2 1

ImportError: No module named 'pip._vendor.urllib3'
by SuryaChethanReddy ChennamiReddy 10 Apr '20

10 Apr '20

i am getting an error when i am using pip to install a library. full error(ex: pip install keras): Traceback (most recent call last): File "c:\program files\python35\lib\runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "c:\program files\python35\lib\runpy.py", line 85, in _run_code exec(code, run_globals) File "C:\Program Files\Python35\Scripts\pip.exe\__main__.py", line 4, in <module> File "C:\Users\aks\AppData\Roaming\Python\Python35\site-packages\pip\_internal\__init__.py", line 20, in <module> from pip._vendor.urllib3.exceptions import DependencyWarning ImportError: No module named 'pip._vendor.urllib3' when i try python -m pip install(package name ex:keras): Traceback (most recent call last): File "C:\Program Files\Python35\lib\runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "C:\Program Files\Python35\lib\runpy.py", line 85, in _run_code exec(code, run_globals) File "C:\Users\aks\AppData\Roaming\Python\Python35\site-packages\pip\__main__.py", line 16, in <module> from pip._internal import main as _main # isort:skip # noqa File "C:\Users\aks\AppData\Roaming\Python\Python35\site-packages\pip\_internal\__init__.py", line 20, in <module> from pip._vendor.urllib3.exceptions import DependencyWarning ImportError: No module named 'pip._vendor.urllib3' you can reproduce it by upgrading pip, interrupting the install when it is deleting pip. please fix this issue.

1 0