Skip to content

Updades description of the popen module #5117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: latest
Choose a base branch
from

Conversation

AArdeev
Copy link
Contributor

@AArdeev AArdeev commented May 19, 2025

Got rid of repeated "ph" abbriviateion everywhere except for examples
Removed "Index" heading
Added Subheadings for constructors, fields, and constants
Fixes #5104
@AArdeev AArdeev self-assigned this May 19, 2025
@AArdeev AArdeev requested review from Totktonada and veod32 May 19, 2025 13:30
@AArdeev AArdeev added the documentation Improvements or additions to documentation label May 19, 2025
@github-actions github-actions bot temporarily deployed to branch-gh-5104-update-popen-module-description May 19, 2025 13:31 Destroyed
Changed datatype for popen handle objects from ``handle`` to ``userdata`` in parameters
Added "object" word to ``popen.shell`` and ``popen.new`` constructors' successful results

Fixes #5117
@github-actions github-actions bot temporarily deployed to branch-gh-5104-update-popen-module-description May 19, 2025 14:48 Destroyed
Changed headings structures and levels by comments for consistency
Fixes #5117
@github-actions github-actions bot temporarily deployed to branch-gh-5104-update-popen-module-description May 19, 2025 15:56 Destroyed
Table names changed for headings by comment
Fixes #5117
@@ -30,7 +30,9 @@ object:
syscall
* :ref:`popen.new <popen-new>` to create a popen object with more specific options

Below is a list of all ``popen`` functions and handle methods.
Below are tables with summaries of ``popen`` constructors, constants, mrthods, and fields.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: mrthods.

Comment on lines 104 to 112
Popen handle fields:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
popen module fields
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are handle fields, not module fields.

Comment on lines +70 to +72
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
popen module methods
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Copy link
Member

@Totktonada Totktonada May 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are handle methods.

Comment on lines +35 to +37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
popen module constructors
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Copy link
Member

@Totktonada Totktonada May 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really place these ToC tables into sub-sections? It is rendered this way:

image

Maybe we can do it in the following way (add the 'summary' words)?

  • Overview
    • popen module constructors summary
    • popen module constants summary
    • popen handle methods summary
    • popen handle fields summary
  • popen module constructors
  • popen module constants
  • popen handle methods
  • popen handle fields

It seems less confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update popen_handle term description
2 participants