Skip to content

C3 MRO algorithm implementation #37275

Closed
Closed

Description

@pedronis
mannequin
BPO 619475
Nosy @gvanrossum
Files
  • c3_impl.patch: c3 impl and test_descr additions
  • 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 = 'https://github.com/gvanrossum'
    closed_at = <Date 2007-11-14.18:26:50.745>
    created_at = <Date 2002-10-07.03:02:42.000>
    labels = ['interpreter-core']
    title = 'C3 MRO algorithm implementation'
    updated_at = <Date 2007-11-14.18:26:50.745>
    user = 'https://bugs.python.org/pedronis'

    bugs.python.org fields:

    activity = <Date 2007-11-14.18:26:50.745>
    actor = 'gvanrossum'
    assignee = 'gvanrossum'
    closed = True
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2002-10-07.03:02:42.000>
    creator = 'pedronis'
    dependencies = []
    files = ['4625']
    hgrepos = []
    issue_num = 619475
    keywords = ['patch']
    message_count = 4.0
    messages = ['41347', '41348', '41349', '57495']
    nosy_count = 2.0
    nosy_names = ['gvanrossum', 'pedronis']
    pr_nums = []
    priority = 'normal'
    resolution = 'accepted'
    stage = None
    status = 'closed'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue619475'
    versions = ['Python 2.3']

    Activity

    1. pedronis commented on Oct 7, 2002

      pedronismannequin
      MannequinAuthor

      At least is a beginning. On Linux all tests and the
      modified test_descr.py pass.

      A few cases in test_descr.py are commented out,
      maybe they should be adjusted, reconstructed.

      For order disagreement situations: backup logic
      picking an element from the first non-empty list and
      removing it from all lists, where it appears, and just
      throwing a warning instead of an exception could be
      put where I set the exception now.

      Although in the long run people should learn to use
      consistent hiearchies anyway.

      PS: I was wondering how to get/reuse lst.remove(o)
      functionality from C, apart through
      PyObject_CallMethod...

    2. pedronis commented on Nov 3, 2002

      pedronismannequin
      MannequinAuthor

      Logged In: YES
      user_id=61408

      FYI, I will be off-line from 4 to 16 Nov.

    3. gvanrossum commented on Nov 14, 2002

      @gvanrossum
      Member

      Logged In: YES
      user_id=6380

      All checked in. Thanks, Samuele!

    4. gvanrossum commented on Nov 14, 2007

      @gvanrossum
      Member
    5. transferred this issue fromon Apr 9, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    Labels

    interpreter-core(Objects, Python, Grammar, and Parser dirs)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions