pygments.rb 1.2.1 → 2.2.0

data/vendor/pygments-main/scripts/detect_missing_analyse_text.py

@@ -1,33 +0,0 @@
-from __future__ import print_function
-import sys
-
-from pygments.lexers import get_all_lexers, find_lexer_class
-from pygments.lexer import Lexer
-
-def main():
-    uses = {}
-
-    for name, aliases, filenames, mimetypes in get_all_lexers():
-        cls = find_lexer_class(name)
-        if not cls.aliases:
-            print(cls, "has no aliases")
-        for f in filenames:
-            if f not in uses:
-                uses[f] = []
-            uses[f].append(cls)
-
-    ret = 0
-    for k, v in uses.items():
-        if len(v) > 1:
-            #print "Multiple for", k, v
-            for i in v:
-                if i.analyse_text is None:
-                    print(i, "has a None analyse_text")
-                    ret |= 1
-                elif Lexer.analyse_text.__doc__ == i.analyse_text.__doc__:
-                    print(i, "needs analyse_text, multiple lexers for", k)
-                    ret |= 2
-    return ret
-
-if __name__ == '__main__':
-    sys.exit(main())

data/vendor/pygments-main/scripts/epydoc.css

@@ -1,280 +0,0 @@
-
-
-/* Epydoc CSS Stylesheet
- *
- * This stylesheet can be used to customize the appearance of epydoc's
- * HTML output.
- *
- */
-
-/* Adapted for Pocoo API docs by Georg Brandl */
-
-/* Default Colors & Styles
- *   - Set the default foreground & background color with 'body'; and 
- *     link colors with 'a:link' and 'a:visited'.
- *   - Use bold for decision list terms.
- *   - The heading styles defined here are used for headings *within*
- *     docstring descriptions.  All headings used by epydoc itself use
- *     either class='epydoc' or class='toc' (CSS styles for both
- *     defined below).
- */
-body                        { background: #ffffff; color: #000000;
-                              font-family: Trebuchet MS,Tahoma,sans-serif;
-                              font-size: 0.9em; line-height: 140%;
-                              margin: 0; padding: 0 1.2em 1.2em 1.2em; }
-a:link                      { color: #C87900; text-decoration: none;
-                              border-bottom: 1px solid #C87900; }
-a:visited                   { color: #C87900; text-decoration: none;
-                              border-bottom: 1px dotted #C87900; }
-a:hover                     { color: #F8A900; border-bottom-color: #F8A900; }
-dt                          { font-weight: bold; }
-h1                          { font-size: +180%; font-style: italic;
-                              font-weight: bold; margin-top: 1.5em; }
-h2                          { font-size: +140%; font-style: italic;
-                              font-weight: bold; }
-h3                          { font-size: +110%; font-style: italic;
-                              font-weight: normal; }
-p                           { margin-top: .5em; margin-bottom: .5em; }
-hr                          { margin-top: 1.5em; margin-bottom: 1.5em;
-                              border: 1px solid #BBB; }
-tt.literal                  { background: #F5FFD0; padding: 2px;
-                              font-size: 110%; }
-table.rst-docutils          { border: 0; }
-table.rst-docutils td       { border: 0; padding: 5px 20px 5px 0px; }
-
-/* Page Header & Footer
- *   - The standard page header consists of a navigation bar (with
- *     pointers to standard pages such as 'home' and 'trees'); a
- *     breadcrumbs list, which can be used to navigate to containing
- *     classes or modules; options links, to show/hide private
- *     variables and to show/hide frames; and a page title (using
- *     <h1>).  The page title may be followed by a link to the
- *     corresponding source code (using 'span.codelink').
- *   - The footer consists of a navigation bar, a timestamp, and a
- *     pointer to epydoc's homepage.
- */ 
-h1.epydoc                   { margin-top: .4em; margin-bottom: .4em;
-                              font-size: +180%; font-weight: bold;
-                              font-style: normal; }
-h2.epydoc                   { font-size: +130%; font-weight: bold;
-                              font-style: normal; }
-h3.epydoc                   { font-size: +115%; font-weight: bold;
-                              font-style: normal; }
-table.navbar                { background: #E6F8A0; color: #000000;
-                              border-top: 1px solid #c0d0d0;
-                              border-bottom: 1px solid #c0d0d0;
-                              margin: -1px -1.2em 1em -1.2em; }
-table.navbar th             { padding: 2px 7px 2px 0px; }
-th.navbar-select            { background-color: transparent; }
-th.navbar-select:before     { content: ">" }
-th.navbar-select:after      { content: "<" }
-table.navbar a              { border: 0; }  
-span.breadcrumbs            { font-size: 95%; font-weight: bold; }
-span.options                { font-size: 80%; }
-span.codelink               { font-size: 85%; }
-td.footer                   { font-size: 85%; }
-
-/* Table Headers
- *   - Each summary table and details section begins with a 'header'
- *     row.  This row contains a section title (marked by
- *     'span.table-header') as well as a show/hide private link
- *     (marked by 'span.options', defined above).
- *   - Summary tables that contain user-defined groups mark those
- *     groups using 'group header' rows.
- */
-td.table-header             { background: #B6C870; color: #000000;
-                              border-bottom: 1px solid #FFF; }
-span.table-header           { font-size: 110%; font-weight: bold; }
-th.group-header             { text-align: left; font-style: italic; 
-                              font-size: 110%; }
-td.spacer { width: 5%; }
-
-/* Summary Tables (functions, variables, etc)
- *   - Each object is described by a single row of the table with
- *     two cells.  The left cell gives the object's type, and is
- *     marked with 'code.summary-type'.  The right cell gives the
- *     object's name and a summary description.
- *   - CSS styles for the table's header and group headers are
- *     defined above, under 'Table Headers'
- */
-table.summary               { border-collapse: collapse;
-                              background: #E6F8A0; color: #000000;
-                              margin: 1em 0 .5em 0;
-                              border: 0; }
-table.summary tr            { border-bottom: 1px solid #BBB; }
-td.summary a                { font-weight: bold; }
-code.summary-type           { font-size: 85%; }
-
-/* Details Tables (functions, variables, etc)
- *   - Each object is described in its own single-celled table.
- *   - A single-row summary table w/ table-header is used as
- *     a header for each details section (CSS style for table-header
- *     is defined above, under 'Table Headers').
- */
-
-table.detsummary            { margin-top: 2em; }
-
-table.details               { border-collapse: collapse;
-                              background: #E6F8A0; color: #000000;
-                              border-bottom: 1px solid #BBB;
-                              margin: 0; }
-table.details td            { padding: .2em .2em .2em .5em; }
-table.details table td      { padding: 0; }
-table.details h3            { margin: 5px 0 5px 0; font-size: 105%;
-                              font-style: normal; }
-
-table.details dd            { display: inline; margin-left: 5px; }
-table.details dl            { margin-left: 5px; }
-
-
-/* Index tables (identifier index, term index, etc)
- *   - link-index is used for indices containing lists of links
- *     (namely, the identifier index & term index).
- *   - index-where is used in link indices for the text indicating
- *     the container/source for each link.
- *   - metadata-index is used for indices containing metadata
- *     extracted from fields (namely, the bug index & todo index).
- */
-table.link-index            { border-collapse: collapse;
-                              background: #F6FFB0; color: #000000;
-                              border: 1px solid #608090; }
-td.link-index               { border-width: 0px; }
-span.index-where            { font-size: 70%; }
-table.metadata-index        { border-collapse: collapse;
-                              background: #F6FFB0; color: #000000;
-                              border: 1px solid #608090; 
-                              margin: .2em 0 0 0; }
-td.metadata-index           { border-width: 1px; border-style: solid; }
-
-/* Function signatures
- *   - sig* is used for the signature in the details section.
- *   - .summary-sig* is used for the signature in the summary 
- *     table, and when listing property accessor functions.
- * */
-.sig-name                   { color: #006080; }
-.sig-arg                    { color: #008060; }
-.sig-default                { color: #602000; }
-.summary-sig-name           { font-weight: bold; }
-.summary-sig-arg            { color: #006040; }
-.summary-sig-default        { color: #501800; }
-
-/* Variable values
- *   - In the 'variable details' sections, each varaible's value is
- *     listed in a 'pre.variable' box.  The width of this box is
- *     restricted to 80 chars; if the value's repr is longer than
- *     this it will be wrapped, using a backslash marked with
- *     class 'variable-linewrap'.  If the value's repr is longer
- *     than 3 lines, the rest will be ellided; and an ellipsis
- *     marker ('...' marked with 'variable-ellipsis') will be used.
- *   - If the value is a string, its quote marks will be marked
- *     with 'variable-quote'.
- *   - If the variable is a regexp, it is syntax-highlighted using
- *     the re* CSS classes.
- */
-pre.variable                { padding: .5em; margin: 0;
-                              background-color: #dce4ec;
-                              border: 1px solid #708890; }
-.variable-linewrap          { display: none; }
-.variable-ellipsis          { color: #604000; font-weight: bold; }
-.variable-quote             { color: #604000; font-weight: bold; }
-.re                         { color: #000000; }
-.re-char                    { color: #006030; }
-.re-op                      { color: #600000; }
-.re-group                   { color: #003060; }
-.re-ref                     { color: #404040; }
-
-/* Base tree
- *   - Used by class pages to display the base class hierarchy.
- */
-pre.base-tree               { font-size: 90%; margin: 1em 0 2em 0;
-                              line-height: 100%;}
-
-/* Frames-based table of contents headers
- *   - Consists of two frames: one for selecting modules; and
- *     the other listing the contents of the selected module.
- *   - h1.toc is used for each frame's heading
- *   - h2.toc is used for subheadings within each frame.
- */
-h1.toc                      { text-align: center; font-size: 105%;
-                              margin: 0; font-weight: bold;
-                              padding: 0; }
-h2.toc                      { font-size: 100%; font-weight: bold; 
-                              margin: 0.5em 0 0 -0.3em; }
-
-/* Syntax Highlighting for Source Code
- *   - doctest examples are displayed in a 'pre.py-doctest' block.
- *     If the example is in a details table entry, then it will use
- *     the colors specified by the 'table pre.py-doctest' line.
- *   - Source code listings are displayed in a 'pre.py-src' block.
- *     Each line is marked with 'span.py-line' (used to draw a line
- *     down the left margin, separating the code from the line
- *     numbers).  Line numbers are displayed with 'span.py-lineno'.
- *     The expand/collapse block toggle button is displayed with
- *     'a.py-toggle' (Note: the CSS style for 'a.py-toggle' should not
- *     modify the font size of the text.)
- *   - If a source code page is opened with an anchor, then the
- *     corresponding code block will be highlighted.  The code
- *     block's header is highlighted with 'py-highlight-hdr'; and
- *     the code block's body is highlighted with 'py-highlight'.
- *   - The remaining py-* classes are used to perform syntax
- *     highlighting (py-string for string literals, py-name for names,
- *     etc.)
- */
-pre.rst-literal-block,
-pre.py-doctest              { margin-left: 1em; margin-right: 1.5em;
-                              line-height: 150%;
-                              background-color: #F5FFD0; padding: .5em;
-                              border: 1px solid #B6C870; 
-                              font-size: 110%; }
-pre.py-src                  { border: 1px solid #BBB; margin-top: 3em;
-                              background: #f0f0f0; color: #000000;
-                              line-height: 150%; }
-span.py-line                { margin-left: .2em; padding-left: .4em; }
-span.py-lineno              { border-right: 1px solid #BBB; 
-                              padding: .3em .5em .3em .5em;
-                              font-style: italic; font-size: 90%; }
-a.py-toggle                 { text-decoration: none; }
-div.py-highlight-hdr        { border-top: 1px solid #BBB;
-                              background: #d0e0e0; }
-div.py-highlight            { border-bottom: 1px solid #BBB;
-                              background: #d0e0e0; }
-.py-prompt                  { color: #005050; font-weight: bold;}
-.py-string                  { color: #006030; }
-.py-comment                 { color: #003060; }
-.py-keyword                 { color: #600000; }
-.py-output                  { color: #404040; }
-.py-name                    { color: #000050; }
-.py-name:link               { color: #000050; }
-.py-name:visited            { color: #000050; }
-.py-number                  { color: #005000; }
-.py-def-name                { color: #000060; font-weight: bold; }
-.py-base-class              { color: #000060; }
-.py-param                   { color: #000060; }
-.py-docstring               { color: #006030; }
-.py-decorator               { color: #804020; }
-/* Use this if you don't want links to names underlined: */
-/*a.py-name                   { text-decoration: none; }*/
-
-/* Graphs & Diagrams
- *   - These CSS styles are used for graphs & diagrams generated using
- *     Graphviz dot.  'img.graph-without-title' is used for bare
- *     diagrams (to remove the border created by making the image
- *     clickable).
- */
-img.graph-without-title     { border: none; }
-img.graph-with-title        { border: 1px solid #000000; }
-span.graph-title            { font-weight: bold; }
-span.graph-caption          { }
-
-/* General-purpose classes
- *   - 'p.indent-wrapped-lines' defines a paragraph whose first line
- *     is not indented, but whose subsequent lines are.
- *   - The 'nomargin-top' class is used to remove the top margin (e.g.
- *     from lists).  The 'nomargin' class is used to remove both the
- *     top and bottom margin (but not the left or right margin --
- *     for lists, that would cause the bullets to disappear.)
- */
-p.indent-wrapped-lines      { padding: 0 0 0 7em; text-indent: -7em; 
-                              margin: 0; }
-.nomargin-top               { margin-top: 0; }
-.nomargin                   { margin-top: 0; margin-bottom: 0; }

data/vendor/pygments-main/scripts/get_vimkw.py

@@ -1,74 +0,0 @@
-from __future__ import print_function
-
-import re
-
-from pygments.util import format_lines
-
-r_line = re.compile(r"^(syn keyword vimCommand contained|syn keyword vimOption "
-                    r"contained|syn keyword vimAutoEvent contained)\s+(.*)")
-r_item = re.compile(r"(\w+)(?:\[(\w+)\])?")
-
-HEADER = '''\
-# -*- coding: utf-8 -*-
-"""
-    pygments.lexers._vim_builtins
-    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-    This file is autogenerated by scripts/get_vimkw.py
-
-    :copyright: Copyright 2006-2017 by the Pygments team, see AUTHORS.
-    :license: BSD, see LICENSE for details.
-"""
-
-# Split up in multiple functions so it's importable by jython, which has a
-# per-method size limit.
-'''
-
-METHOD = '''\
-def _get%(key)s():
-%(body)s
-    return var
-%(key)s = _get%(key)s()
-'''
-
-def getkw(input, output):
-    out = file(output, 'w')
-
-    # Copy template from an existing file.
-    print(HEADER, file=out)
-
-    output_info = {'command': [], 'option': [], 'auto': []}
-    for line in file(input):
-        m = r_line.match(line)
-        if m:
-            # Decide which output gets mapped to d
-            if 'vimCommand' in m.group(1):
-                d = output_info['command']
-            elif 'AutoEvent' in m.group(1):
-                d = output_info['auto']
-            else:
-                d = output_info['option']
-
-            # Extract all the shortened versions
-            for i in r_item.finditer(m.group(2)):
-                d.append('(%r,%r)' %
-                         (i.group(1), "%s%s" % (i.group(1), i.group(2) or '')))
-
-    output_info['option'].append("('nnoremap','nnoremap')")
-    output_info['option'].append("('inoremap','inoremap')")
-    output_info['option'].append("('vnoremap','vnoremap')")
-
-    for key, keywordlist in output_info.items():
-        keywordlist.sort()
-        body = format_lines('var', keywordlist, raw=True, indent_level=1)
-        print(METHOD % locals(), file=out)
-
-def is_keyword(w, keywords):
-    for i in range(len(w), 0, -1):
-        if w[:i] in keywords:
-            return keywords[w[:i]][:len(w)] == w
-    return False
-
-if __name__ == "__main__":
-    getkw("/usr/share/vim/vim74/syntax/vim.vim",
-          "pygments/lexers/_vim_builtins.py")

data/vendor/pygments-main/scripts/pylintrc

@@ -1,301 +0,0 @@
-# lint Python modules using external checkers.
-# 
-# This is the main checker controling the other ones and the reports
-# generation. It is itself both a raw checker and an astng checker in order
-# to:
-# * handle message activation / deactivation at the module level
-# * handle some basic but necessary stats'data (number of classes, methods...)
-# 
-[MASTER]
-
-# Specify a configuration file.
-#rcfile=
-
-# Profiled execution.
-profile=no
-
-# Add <file or directory> to the black list. It should be a base name, not a
-# path. You may set this option multiple times.
-ignore=.svn
-
-# Pickle collected data for later comparisons.
-persistent=yes
-
-# Set the cache size for astng objects.
-cache-size=500
-
-# List of plugins (as comma separated values of python modules names) to load,
-# usually to register additional checkers.
-load-plugins=
-
-
-[MESSAGES CONTROL]
-
-# Enable only checker(s) with the given id(s). This option conflict with the
-# disable-checker option
-#enable-checker=
-
-# Enable all checker(s) except those with the given id(s). This option conflict
-# with the disable-checker option
-#disable-checker=
-
-# Enable all messages in the listed categories.
-#enable-msg-cat=
-
-# Disable all messages in the listed categories.
-#disable-msg-cat=
-
-# Enable the message(s) with the given id(s).
-#enable-msg=
-
-# Disable the message(s) with the given id(s).
-disable-msg=C0323,W0142,C0301,C0103,C0111,E0213,C0302,C0203,W0703,R0201
-
-
-[REPORTS]
-
-# set the output format. Available formats are text, parseable, colorized and
-# html
-output-format=colorized
-
-# Include message's id in output
-include-ids=yes
-
-# Put messages in a separate file for each module / package specified on the
-# command line instead of printing them on stdout. Reports (if any) will be
-# written in a file name "pylint_global.[txt|html]".
-files-output=no
-
-# Tells wether to display a full report or only the messages
-reports=yes
-
-# Python expression which should return a note less than 10 (10 is the highest
-# note).You have access to the variables errors warning, statement which
-# respectivly contain the number of errors / warnings messages and the total
-# number of statements analyzed. This is used by the global evaluation report
-# (R0004).
-evaluation=10.0 - ((float(5 * error + warning + refactor + convention) / statement) * 10)
-
-# Add a comment according to your evaluation note. This is used by the global
-# evaluation report (R0004).
-comment=no
-
-# Enable the report(s) with the given id(s).
-#enable-report=
-
-# Disable the report(s) with the given id(s).
-#disable-report=
-
-
-# checks for
-# * unused variables / imports
-# * undefined variables
-# * redefinition of variable from builtins or from an outer scope
-# * use of variable before assigment
-# 
-[VARIABLES]
-
-# Tells wether we should check for unused import in __init__ files.
-init-import=no
-
-# A regular expression matching names used for dummy variables (i.e. not used).
-dummy-variables-rgx=_|dummy
-
-# List of additional names supposed to be defined in builtins. Remember that
-# you should avoid to define new builtins when possible.
-additional-builtins=
-
-
-# try to find bugs in the code using type inference
-# 
-[TYPECHECK]
-
-# Tells wether missing members accessed in mixin class should be ignored. A
-# mixin class is detected if its name ends with "mixin" (case insensitive).
-ignore-mixin-members=yes
-
-# When zope mode is activated, consider the acquired-members option to ignore
-# access to some undefined attributes.
-zope=no
-
-# List of members which are usually get through zope's acquisition mecanism and
-# so shouldn't trigger E0201 when accessed (need zope=yes to be considered).
-acquired-members=REQUEST,acl_users,aq_parent
-
-
-# checks for :
-# * doc strings
-# * modules / classes / functions / methods / arguments / variables name
-# * number of arguments, local variables, branchs, returns and statements in
-# functions, methods
-# * required module attributes
-# * dangerous default values as arguments
-# * redefinition of function / method / class
-# * uses of the global statement
-# 
-[BASIC]
-
-# Required attributes for module, separated by a comma
-required-attributes=
-
-# Regular expression which should only match functions or classes name which do
-# not require a docstring
-no-docstring-rgx=__.*__
-
-# Regular expression which should only match correct module names
-module-rgx=(([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+))$
-
-# Regular expression which should only match correct module level names
-const-rgx=(([A-Z_][A-Z1-9_]*)|(__.*__))$
-
-# Regular expression which should only match correct class names
-class-rgx=[A-Z_][a-zA-Z0-9]+$
-
-# Regular expression which should only match correct function names
-function-rgx=[a-z_][a-z0-9_]{2,30}$
-
-# Regular expression which should only match correct method names
-method-rgx=[a-z_][a-z0-9_]{2,30}$
-
-# Regular expression which should only match correct instance attribute names
-attr-rgx=[a-z_][a-z0-9_]{2,30}$
-
-# Regular expression which should only match correct argument names
-argument-rgx=[a-z_][a-z0-9_]{2,30}$
-
-# Regular expression which should only match correct variable names
-variable-rgx=[a-z_][a-z0-9_]{2,30}$
-
-# Regular expression which should only match correct list comprehension /
-# generator expression variable names
-inlinevar-rgx=[A-Za-z_][A-Za-z0-9_]*$
-
-# Good variable names which should always be accepted, separated by a comma
-good-names=i,j,k,ex,Run,_
-
-# Bad variable names which should always be refused, separated by a comma
-bad-names=foo,bar,baz,toto,tutu,tata
-
-# List of builtins function names that should not be used, separated by a comma
-bad-functions=apply,input
-
-
-# checks for sign of poor/misdesign:
-# * number of methods, attributes, local variables...
-# * size, complexity of functions, methods
-# 
-[DESIGN]
-
-# Maximum number of arguments for function / method
-max-args=12
-
-# Maximum number of locals for function / method body
-max-locals=30
-
-# Maximum number of return / yield for function / method body
-max-returns=12
-
-# Maximum number of branch for function / method body
-max-branchs=30
-
-# Maximum number of statements in function / method body
-max-statements=60
-
-# Maximum number of parents for a class (see R0901).
-max-parents=7
-
-# Maximum number of attributes for a class (see R0902).
-max-attributes=20
-
-# Minimum number of public methods for a class (see R0903).
-min-public-methods=0
-
-# Maximum number of public methods for a class (see R0904).
-max-public-methods=20
-
-
-# checks for
-# * external modules dependencies
-# * relative / wildcard imports
-# * cyclic imports
-# * uses of deprecated modules
-# 
-[IMPORTS]
-
-# Deprecated modules which should not be used, separated by a comma
-deprecated-modules=regsub,string,TERMIOS,Bastion,rexec
-
-# Create a graph of every (i.e. internal and external) dependencies in the
-# given file (report R0402 must not be disabled)
-import-graph=
-
-# Create a graph of external dependencies in the given file (report R0402 must
-# not be disabled)
-ext-import-graph=
-
-# Create a graph of internal dependencies in the given file (report R0402 must
-# not be disabled)
-int-import-graph=
-
-
-# checks for :
-# * methods without self as first argument
-# * overridden methods signature
-# * access only to existant members via self
-# * attributes not defined in the __init__ method
-# * supported interfaces implementation
-# * unreachable code
-# 
-[CLASSES]
-
-# List of interface methods to ignore, separated by a comma. This is used for
-# instance to not check methods defines in Zope's Interface base class.
-ignore-iface-methods=isImplementedBy,deferred,extends,names,namesAndDescriptions,queryDescriptionFor,getBases,getDescriptionFor,getDoc,getName,getTaggedValue,getTaggedValueTags,isEqualOrExtendedBy,setTaggedValue,isImplementedByInstancesOf,adaptWith,is_implemented_by
-
-# List of method names used to declare (i.e. assign) instance attributes.
-defining-attr-methods=__init__,__new__,setUp
-
-
-# checks for similarities and duplicated code. This computation may be
-# memory / CPU intensive, so you should disable it if you experiments some
-# problems.
-# 
-[SIMILARITIES]
-
-# Minimum lines number of a similarity.
-min-similarity-lines=10
-
-# Ignore comments when computing similarities.
-ignore-comments=yes
-
-# Ignore docstrings when computing similarities.
-ignore-docstrings=yes
-
-
-# checks for:
-# * warning notes in the code like FIXME, XXX
-# * PEP 263: source code with non ascii character but no encoding declaration
-# 
-[MISCELLANEOUS]
-
-# List of note tags to take in consideration, separated by a comma.
-notes=FIXME,XXX,TODO
-
-
-# checks for :
-# * unauthorized constructions
-# * strict indentation
-# * line length
-# * use of <> instead of !=
-# 
-[FORMAT]
-
-# Maximum number of characters on a single line.
-max-line-length=90
-
-# Maximum number of lines in a module
-max-module-lines=1000
-
-# String used as indentation unit. This is usually " " (4 spaces) or "\t" (1
-# tab).
-indent-string='    '