Skip to content

bug with pygments 2.16.0 #6121

@tlambert03

Description

@tlambert03

A heads up on a new bug I just saw when running superqt tests on napari:

napari/utils/events/evented_model.py:246: in __init__
    super().__init__(**kwargs)
pydantic/main.py:341: in pydantic.main.BaseModel.__init__
    ???
E   pydantic.error_wrappers.ValidationError: 1 validation error for Theme
E   syntax_style
E     Incorrect `syntax_style` value: native provided. Please use one of the following:  abap, algol, algol_nu, arduino, autumn, bw, borland, colorful, default, dracula, emacs, fruity, friendly, friendly_grayscale, github-dark, gruvbox-dark, gruvbox-light, igor, inkpot, lightbulb, lilypond, lovelace, manni, material, monokai, murphy, nord, nord-darker, one-dark, paraiso-dark, paraiso-light, pastie, perldoc, rainbow_dash, rrt, sas, solarized-dark, solarized-light, staroffice, stata, stata-dark, stata-light, tango, trac, vim, vs, xcode, zenburn
E   assert 'native' in {'abap': 'abap::AbapStyle', 'algol': 'algol::AlgolStyle', 'algol_nu': 'algol_nu::Algol_NuStyle', 'arduino': 'arduino::ArduinoStyle', ...} (type=assertion_error)

looks like the new release of pygments (2.16.0) may have broken the theme naming strategy here

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working as expected

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions