Skip to content

No documentation for Py_TPFLAGS_HAVE_STACKLESS_EXTENSION or Py_TPFLAGS_HAVE_VERSION_TAG. #52289

Description

@stutzbach
mannequin
BPO 8041
Nosy @birkenfeld, @pitrou, @pmp-p

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2010-03-02.15:34:57.356>
labels = ['3.8', '3.9', '3.10', 'docs']
title = 'No documentation for Py_TPFLAGS_HAVE_STACKLESS_EXTENSION or Py_TPFLAGS_HAVE_VERSION_TAG.'
updated_at = <Date 2020-11-08.11:23:53.038>
user = 'https://bugs.python.org/stutzbach'

bugs.python.org fields:

activity = <Date 2020-11-08.11:23:53.038>
actor = 'pmpp'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2010-03-02.15:34:57.356>
creator = 'stutzbach'
dependencies = []
files = []
hgrepos = []
issue_num = 8041
keywords = []
message_count = 4.0
messages = ['100298', '112972', '113491', '227971']
nosy_count = 5.0
nosy_names = ['georg.brandl', 'pitrou', 'stutzbach', 'pmpp', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue8041'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

Activity

  1. stutzbach commented on Mar 2, 2010

    stutzbachmannequin
    MannequinAuthor

    The documentation for Py_TPFLAGS_DEFAULT mentions Py_TPFLAGS_HAVE_STACKLESS_EXTENSION and Py_TPFLAGS_HAVE_VERSION_TAG, but neither of them is documented. They aren't mentioned in the 2.6 documentation (presumably because they were introduced in 3.x?).

    http://docs.python.org/dev/py3k/c-api/typeobj.html?highlight=py_tpflags_have_gc#Py_TPFLAGS_DEFAULT

  2. pitrou commented on Aug 5, 2010

    @pitrou
    Member

    I don't think these flags need documenting or even deserve mentioning. Py_TPFLAGS_HAVE_STACKLESS_EXTENSION seems to be two bits reserved for use by Stackless, while Py_TPFLAGS_HAVE_VERSION_TAG should be considered by extension authors an internal implementation detail (in normal circumstances, it won't impact how they have to write their code or the semantics of their extension types).

  3. stutzbach commented on Aug 9, 2010

    stutzbachmannequin
    MannequinAuthor

    I think if they are mentioned, they should be documented. Removing mention of them would be fine with me.

    Looking at this again, I think the description of Py_TPFLAGS_DEFAULT is no longer accurate. It reads: "This is a bitmask of all the bits that pertain to the existence of certain fields in the type object and its extension structures. Currently, it includes the following bits: Py_TPFLAGS_HAVE_STACKLESS_EXTENSION, Py_TPFLAGS_HAVE_VERSION_TAG."

    But neither of those flags pertain to the existence of certain fields, do they?

    Perhaps it should simply read: "This bitmask should be set by all types to define certain bits used internally by Python."

  4. BreamoreBoy commented on Sep 30, 2014

    BreamoreBoymannequin
    Mannequin

    @daniel could you supply a patch for this?

  5. transferred this issue fromon Apr 10, 2022
  6. methane commented on Sep 5, 2026

    @methane
    Member

    fixed via #145127

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions