Skip to content

pyrefly report includes many generated dunders for __main__.py #3505

@jorenham

Description

@jorenham

Running uvx pyrefly report zmq on pyzmq (https://github.com/zeromq/pyzmq) shows the following:

{
  "name": "zmq.log.__main__",
  "path": "/home/joren/Workspace/pyzmq/zmq/log/__main__.py",
  "names": [
    "zmq.log.__main__.__annotations__",
    "zmq.log.__main__.__builtins__",
    "zmq.log.__main__.__cached__",
    "zmq.log.__main__.__debug__",
    "zmq.log.__main__.__dict__",
    "zmq.log.__main__.__file__",
    "zmq.log.__main__.__loader__",
    "zmq.log.__main__.__name__",
    "zmq.log.__main__.__package__",
    "zmq.log.__main__.__path__",
    "zmq.log.__main__.__spec__",

These dunders are all generated by cpython, so Pyrefly should not report these.

__main__.py source: https://github.com/zeromq/pyzmq/blob/9f811c7a10c26c0bf8ded89e3b1c70deafc387a9/zmq/log/__main__.py

Metadata

Metadata

Assignees

No one assigned

    Labels

    quansightreportIssues related to `pyrefly report`

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions