docs

docs@python.org

7 participants
15642 discussions

[issue43804] Add more info about building C/C++ Extensions on Windows using MSVC

by Shreyan Avigyan

New submission from Shreyan Avigyan <shreyan.avigyan(a)gmail.com>: In the context of Docs/extending/windows.rst, the command provided, for compiling the source code and linking the libraries to create a DLL, only works for Python 32-bit versions. But the documentation doesn't inform anything about that. The PR linked with this issue adds a note section with the text :- """ The above commands are only applicable for Python 32-bit versions. """ This PR is against the master branch and if accepted, it needs to be backported to all the previous supported versions. Kindly have a review of my PR. Thanking you, With Regards ---------- assignee: docs@python components: Documentation messages: 390773 nosy: docs@python, shreyanavigyan priority: normal severity: normal status: open title: Add more info about building C/C++ Extensions on Windows using MSVC versions: Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43804> _______________________________________

1 hour, 23 minutes

[issue43837] Operator precedence documentation could be more clear

by Aidan Feldman

New submission from Aidan Feldman <aidan.feldman(a)gmail.com>: I am teaching a class on Python for people who are new to coding, and I was talking them through the operator precedence table: https://docs.python.org/3/reference/expressions.html#operator-precedence A couple things that confused the students: - "Highest precedence" is on the bottom, while "lowest precedence" is on top - There isn't any mention of variables. While not operators, probably worth mentioning that they (effectively?) have higher precedence than any of the operators. I'd be happy to try making my first contribution to Python if there's interest in those edits. Also, I have an example breaking down operator precedence in practice here, which I could include: https://colab.research.google.com/github/afeld/python-public-policy/blob/ma… Thanks! ---------- assignee: docs@python components: Documentation messages: 391030 nosy: aidan.feldman, docs@python priority: normal severity: normal status: open title: Operator precedence documentation could be more clear type: enhancement versions: Python 3.10, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43837> _______________________________________

3 hours, 13 minutes

[issue43777] Remove description of "pip search" command from tutorial

by Bob Kline

New submission from Bob Kline <bkline(a)rksystems.com>: The official tutorial instructs users to find third-party packages by using the "pip search" command, which no longer works (and will be deprecated -- and presumably subsequently removed -- according to the error message). See https://docs.python.org/3.10/tutorial/venv.html#managing-packages-with-pip That passage should be removed from the tutorial. ---------- assignee: docs@python components: Documentation messages: 390550 nosy: bkline, docs@python priority: normal severity: normal status: open title: Remove description of "pip search" command from tutorial versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43777> _______________________________________

5 hours, 49 minutes

[issue43834] Use context manager in StringIO example

by John Hagen

New submission from John Hagen <johnthagen(a)gmail.com>: The example for StringIO currently manually closes the object rather than using a context manager. Since this is likely the first code that a new user encounters and context managers reduce error-prone situations, I think it would be helpful to show usage as a context manager. https://docs.python.org/3/library/io.html#io.StringIO.getvalue Something like: import io with io.StringIO() as output: output.write('First line.\n') print('Second line.', file=output) # Retrieve file contents -- this will be # 'First line.\nSecond line.\n' contents = output.getvalue() # Context manager will automatically close # object and discard memory buffer -- # .getvalue() will now raise an exception. ---------- assignee: docs@python components: Documentation messages: 391000 nosy: John Hagen, docs@python priority: normal severity: normal status: open title: Use context manager in StringIO example type: enhancement versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43834> _______________________________________

15 hours, 27 minutes

translate Documentation

by Soroush Neyestani

Hello I am learning Python and I did not see Persian in the Documentation section It seemed to me that many people might need Persian If I translate the whole document into Persian, will you put it on the site? <mailto:docs@python.org>

19 hours, 23 minutes

[issue43803] ctypes string_at/wstring_at - bad argument name used in docs and in docstring

by Shreyan Avigyan

Shreyan Avigyan <shreyan.avigyan(a)gmail.com> added the comment: PR opened for this issue. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43803> _______________________________________

1 day, 1 hour

[issue43803] ctypes string_at/wstring_at - bad argument name used in docs and in docstring

by Shreyan Avigyan

Change by Shreyan Avigyan <shreyan.avigyan(a)gmail.com>: ---------- keywords: +patch pull_requests: +24116 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25384 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43803> _______________________________________

1 day, 1 hour

[issue43803] ctypes string_at/wstring_at - bad argument name used in docs and in docstring

by Shreyan Avigyan

Shreyan Avigyan <shreyan.avigyan(a)gmail.com> added the comment: Ok..then submitting the PR in 10 minutes. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43803> _______________________________________

1 day, 4 hours

[issue43803] ctypes string_at/wstring_at - bad argument name used in docs and in docstring

by Eryk Sun

Eryk Sun <eryksun(a)gmail.com> added the comment: > So are you telling that we should change the name to "ptr" to > avoid a breaking change? The function parameter name is "ptr". Changing that name could break existing code. I don't think it's likely, but it's not worth breaking even one script just for this. So change the docstring and documentation to refer to "ptr". ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43803> _______________________________________

1 day, 4 hours

[issue43803] ctypes string_at/wstring_at - bad argument name used in docs and in docstring

by Shreyan Avigyan

Shreyan Avigyan <shreyan.avigyan(a)gmail.com> added the comment: Ok...let me review again. Having different names for the same argument can cause confusion, right? So are you telling that we should change the name to "ptr" to avoid a breaking change? If this issue is confirmed, I'm ready to submit a PR to make this change. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43803> _______________________________________

1 day, 5 hours

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

docs