Skip to content

Benchmark functions should (if possible) be tested in order #18

@kdodia

Description

@kdodia

It would be nice for scanfuncs to preserve order when scanning functions, although I will admit I don't know if this is possible.

According to the *.py scan

funcs = pyclbr.readmodule_ex(name, [path])
funcnames = []
for key, val in funcs.items():
    if (any(key.startswith(prefix) for prefix in prefixes) and
            val.file == filename):
        funcnames.append(key)
return funcnames

—the functions are stored in a dictionary returned by pyclbr, which clobbers order. Thus, despite providing empty, small, and large benchmark functions in that order, the result generally will not be. Ex:

eriknw_benchtoolz

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions