Page MenuHomePhabricator

When highlighting source, catch "python" for the PHP parser
ClosedPublic

Authored by epriestley on Feb 28 2019, 8:57 PM.
Tags
None
Referenced Files
F22711638: D20231.id.diff
Sat, Oct 3, 1:38 PM
F22553058: D20231.diff
Wed, Sep 23, 8:55 AM
Unknown Object (File)
Sep 14 2026, 7:05 PM
Unknown Object (File)
Sep 12 2026, 2:53 AM
Unknown Object (File)
Aug 10 2026, 4:17 PM
Unknown Object (File)
Jul 12 2026, 5:07 PM
Unknown Object (File)
Jul 12 2026, 5:07 PM
Unknown Object (File)
Jul 1 2026, 11:47 AM
Subscribers
None

Details

Summary

See PHI1065. Normally, Python files are called ".py" and we end up with the lexer coded as "py" by the time we get here, but if you "Highlight As..." and select "Python" we can end up here with "python". (Probably also if you name a file "something.python", although this is very unusual.)

Catch both "py" and "python" for our highlighter.

T3626 should eventually standardize and moot this, but since this patch is only a quarter of a line long it seems reasonable until then.

Test Plan

Added a phlog(), verified we now hit the first-party highlighter with "Highlight As... > Python".

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable