Mailman 3 March 2019 - docs

[issue36196] sys.executable does not return python3 executable when using uwsgi
by Joris VAN HOUTVEN 06 Mar '19

06 Mar '19

New submission from Joris VAN HOUTVEN <joris.vanhoutven(a)uhasselt.be>: when serving a Flask app with uwsgi, using `sys.executable` will provide you the path to your uwsgi executable, not your python executable. However, the docs specify that it should always return the python interpreter: https://docs.python.org/3/library/sys.html#sys.executable ---------- assignee: docs@python components: Documentation messages: 337190 nosy: Joris VAN HOUTVEN, docs@python priority: normal severity: normal status: open title: sys.executable does not return python3 executable when using uwsgi type: behavior _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36196> _______________________________________

3 5

[issue36203] PyWeakref_NewRef docs are misleading
by SilentGhost 06 Mar '19

06 Mar '19

Change by SilentGhost <ghost.adh(a)runbox.com>: ---------- assignee: -> docs@python components: +Documentation, ctypes nosy: +docs@python type: -> behavior _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36203> _______________________________________

1 0

[issue36198] Misleading in library/sets document
by Han 06 Mar '19

06 Mar '19

New submission from Han <phoenix.seek(a)gmail.com>: Doc/library/sets.rst said operation s.update(t)'s result is "return set s with elements added from t". But update()'s return value is None. I think change it to "set s with elements added from t" would be better. So are operations intersection_update(), difference_update(), and symmetric_difference_update(). ---------- assignee: docs@python components: Documentation messages: 337192 nosy: DeadmanWalking, docs@python priority: normal severity: normal status: open title: Misleading in library/sets document versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36198> _______________________________________

3 3

https://docs.python.org/3/library/multiprocessing.html
by Goldberg, Arthur P 05 Mar '19

05 Mar '19

Great package. I’ve some suggested documentation improvements: s/necessary to run the process objects/necessary to run the process object's/ s/Given this blocks/Given this blocking/ in class multiprocessing.pool.AsyncResult, the behavior of get() when timeout is None needs to be documented. Also, in my opinion, the signatures of get() and wait() should be written get(timeout=None) wait(timeout=None) to make it clear that the default values of timeout is None. Thanks for your good work. Arthur Arthur Goldberg, PhD Associate Professor of Genetics and Data Science Institute for Data Science and Genomic Technology Mount Sinai School of Medicine 1255 Fifth Ave., Suite C-2 New York, NY 10029 646 526 5020 Karr Lab Arthur.Goldberg(a)mssm.edu<mailto:Arthur.Goldberg@mssm.edu>

1 0

[issue36195] initializer is not a valid param in ThreadPoolExecutor
by Harmandeep Singh 05 Mar '19

05 Mar '19

Change by Harmandeep Singh <harmandeep3091(a)gmail.com>: ---------- keywords: +patch pull_requests: +12178 stage: -> patch review _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36195> _______________________________________

1 0

Error 404 | Prebuilt Docs
by Dimitrios N. Kouveris 05 Mar '19

05 Mar '19

Hello, The download links at https://docs.python.org/dev/download.html are responding with error 404. Why this happens? Thank you, Kouveris N. Dimitrios MEng Candidate, UOI https://[dimkouv.com](http://www.dimkouv.com/) Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

[issue36195] initializer is not a valid param in ThreadPoolExecutor
by Stéphane Wirtel 05 Mar '19

05 Mar '19

Stéphane Wirtel <stephane(a)wirtel.be> added the comment: harman786 good luck for your PR, if you need a review. Have a nice day, ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36195> _______________________________________

1 0

[issue36195] initializer is not a valid param in ThreadPoolExecutor
by Stéphane Wirtel 05 Mar '19

05 Mar '19

Change by Stéphane Wirtel <stephane(a)wirtel.be>: ---------- keywords: +easy _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36195> _______________________________________

1 0

[issue36195] initializer is not a valid param in ThreadPoolExecutor
by Stéphane Wirtel 05 Mar '19

05 Mar '19

Stéphane Wirtel <stephane(a)wirtel.be> added the comment: ok, I was working on a PR for this issue. but I am going to classify it as easy. ---------- nosy: +matrixise _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36195> _______________________________________

1 0

[issue36195] initializer is not a valid param in ThreadPoolExecutor
by Harmandeep Singh 05 Mar '19

05 Mar '19

Harmandeep Singh <harmandeep3091(a)gmail.com> added the comment: I will raise a PR ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36195> _______________________________________

1 0