| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pyupgrade is a tool to automatically upgrade syntax for newer versions
of the Python language.
The project has been Python 3 only since
35544e2fc6eed0ce4a27ec7285aac71ff0ddc473, allowing for several cleanups:
- Remove unnecessary "-*- coding: utf-8 -*-" cookie. Python 3 reads all
source files as utf-8 by default.
- Replace IOError/EnvironmentError with OSError. Python 3 unified these
exceptions. The old names are aliases only.
- Use the Python 3 shorter super() syntax.
- Remove "utf8" argument form encode/decode. In Python 3, this value is
the default.
- Remove "r" from open() calls. In Python 3, this value is the default.
- Remove u prefix from Unicode strings. In Python 3, all strings are
Unicode.
- Replace io.open() with builtin open(). In Python 3, these functions
are functionally equivalent.
Co-authored-by: Matthäus G. Chajdas <Anteru@users.noreply.github.com>
|
| | |
|
| |
|
|
| |
fixes #1679
|
| |\
| |
| |
| | |
felixhao28-master
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Some of the keywords are missing for JavaScript and TypeScript.
And some of reserved keywords have been moved to
`keywords` and `declarations keywords`.
There are also non-existent builtins that I removed.
Added missing builtins.
|
| | | |
|
| | |
| |
| | |
Resolves #1646
|
| | | |
|
| | |
| |
| |
| | |
fixes #1637
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The output from pygments.lexers.get_all_lexers() contains 'juttle'
twice in the aliases section for the Juttle lexer entry.
This could be reproduced using:
>>> from pygments.lexers import get_all_lexers
>>> lexers = get_all_lexers()
>>> {alias[0]: alias[1] for alias in lexers}.get('Juttle')
('juttle', 'juttle')
This patch fixes the duplicate entry and generates the associated
_mapping.py file.
Fixes: #1604
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* all: remove "u" string prefix
* util: remove unirange
Since Python 3.3, all builds are wide unicode compatible.
* unistring: remove support for narrow-unicode builds
which stopped being relevant with Python 3.3
|
| | |
| |
| |
| | |
Add a quick reminder that Javascript doesn't need integers.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Rename the "Javascript" tests to reflect that they are for CoffeeScript
This change also modifies the module docstring to reflect the file's purpose.
* Overhaul the Javascript numeric literal parsing
Fixes #307
This patch contains the following changes:
* Adds 50+ unit tests for Javascript numeric literals
* Forces ASCII numbers for float literals (so, now reject `.୪`)
* Adds support for Javascript's BigInt notation (`100n`)
* Adds support for leading-zero-only octal notation (`0777`)
* Adds support for scientific notation with no significand (`1e10`)
Numeric literal parsing is based on information at:
* https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types
* https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Remove Python 2 compatibility
* remove 2/3 shims in pygments.util
* update setup.py metadata
* Remove unneeded object inheritance.
* Remove unneeded future imports.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
.typoscript is used for TypoScript files, removing the ambiguity with
TypeScript.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
lexer files
|
| |/ |
|
| |\
| |
| |
| | |
Implement guessing and resolution between TypeScript and TypoScript.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These values would trigger problems when guessing content without a filename,
and really aren't needed. They've been removed, allowing the standard behavior
to take place.
On top of this, the regex for TypeScript has been slightly altered to include
a whitespace match after "export" to be within the group for the "export"
text.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new TypoScript lexer was taking precedence over TypeScript, which share
the same file extension. This meant that any previously-working TypeScript
source files would be misidentified and highlighted incorrectly. This was due
to the lack of a guesser for TypeScript, and TypoScript having a naturally
higher priority.
This change balances things a bit between the lexers. TypoScript now has an
explicitly-higher priority than TypeScript, both for the file extension and
defaults when guessing content, as it has less we can rely on in terms of
content. TypeScript has a lower priority, but has an analyse_text() method
that checks for common symbols in code, giving it a better chance of matching
for actual TypeScript source files.
TypeScript also gains an additional file extension, *.tsx. Ideally, this would
have its own lexer that understood inline JSX syntax, but giving general
TypeScript syntax highlighting for these files is a step in the right
direction.
|
| |\ \
| | |
| | |
| | | |
update LassoLexer
|
| | |\ \
| | | |
| | | |
| | | | |
Add support for string literals to TypeScriptLexer.
|
| | | |/
| | |
| | |
| | |
| | |
| | | |
This introduces support for string literals to the TypeScript lexer. The rules
are consistent with those in JavascriptLexer, helping to ensure the same
behavior and capabilities between the two.
|
| | | |
| | |
| | |
| | | |
punctuation and add new es2015 regex flags (sticky and unicode)
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
devoncarew1/pygments-main/devoncarew1/javascriptpy-edited-online-with-bitbucke-1472355033252 (pull request #657)
javascript.py edited online with Bitbucket
|
| | | |/ |
|
| | | | |
|
| | /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces support for some missing features to the Handlebars lexer:
Partials and path segments. Partials mostly appeared to work before, but the
`>` in `{{> ... }}` would appear as a syntax error, as could other
components of the partial. This change introduces support for:
* Standard partials: `{{> partialName}}`
* Partials with parameters: `{{> partialName varname="value"}}`
* Ddynamic partials: `{{> (partialFunc)}}`
* Ddynamic partials with lookups: `{{> (lookup ../path "partialName")}}`
* Partial blocks: `{{> @partial-block}}`
* Inline partials: `{{#*inline}}..{{/inline}}`
It also introduces support for path segments, which can reference content in
the current context or in a parent context. For instance, `this.name`,
`this/name`, `./name`, `../name`, `this/name`, etc. These are all now tracked
as variables.
|
| | | |
|
| |/ |
|
| |
|
|
| |
Fixes #991
|
| | |
|
| | |
|
| | |
|
