0x1949 Team - FAZEMRX - MANAGER
Edit File: formatter.cpython-310.pyc
o �|�ar@ � @ s� d dl mZ dZdZdZzd dlmZmZ d dlm Z m Z W n e y' Y nw G dd� de �Z e d e�Ze d e�Zd d � Zd d� ZdS )� )� Deb822Token�is_value� is_comment� is_separator)�Iterator�Union)�TokenOrElement�FormatterCallbackc @ s� e Zd ZdZdZdd� Zedd� �Zedd� �Zed d � �Z ed d � �Z e d d� �Z e dd� �Z e dd� �Ze dd� �Ze dd� �Zdd� Zdd� ZdS ) �FormatterContentTokenz�Typed, tagged text for use with the formatting API The FormatterContentToken is used by the formatting API and provides the formatter callback with context about the textual tokens it is supposed to format. ��_text� _content_typec C s || _ || _d S �Nr )�self�text� content_type� r �@/usr/lib/python3/dist-packages/debian/_deb822_repro/formatter.py�__init__ s z FormatterContentToken.__init__c C sD t |t�r|jr| �|j�S |jrtd��| �|j�S | �|�� �S )Nz)FormatterContentType cannot be whitespace) � isinstancer r � comment_tokenr � is_whitespace� ValueError� value_token�convert_to_text)�cls�token_or_elementr r r �from_token_or_element s z+FormatterContentToken.from_token_or_elementc C s" |dkrt S |dkr tS | |t�S )N� �,)�SPACE_SEPARATOR_FT�COMMA_SEPARATOR_FT�_CONTENT_TYPE_SEPARATOR�r r r r r �separator_token, s z%FormatterContentToken.separator_tokenc C � | |t �S )zoGenerates a single comment token with the provided text Mostly useful for creating test cases )�_CONTENT_TYPE_COMMENTr# r r r r 6 � z#FormatterContentToken.comment_tokenc C r% )zmGenerates a single value token with the provided text Mostly useful for creating test cases )�_CONTENT_TYPE_VALUEr# r r r r ? r' z!FormatterContentToken.value_tokenc C � | j tu S )a� True if this formatter token represent a comment This should be used for determining whether the token is a comment or not. It might be tempting to check whether the text in the token starts with a "#" but that is insufficient because a value *can* start with that as well. Whether it is a comment or a value is based on the context (it is a comment if and only if the "#" was at the start of a line) but the formatter often do not have the context available to assert this. The formatter *should* preserve the order of comments and interleave between the value tokens in the same order as it see them. Failing to preserve the order of comments and values can cause confusing comments (such as associating the comment with a different value than it was written for). The formatter *may* discard comment tokens if it does not want to preserve them. If so, they would be omitted in the output, which may be acceptable in some cases. This is a lot better than re-ordering comments. Formatters must be aware of the following special cases for comments: * Comments *MUST* be emitted after a newline. If the very first token is a comment, the formatter is expected to emit a newline before it as well (Fields cannot start immediately on a comment). )r r& �r r r r r H s z FormatterContentToken.is_commentc C r) )at True if this formatter token represents a semantic value The formatter *MUST* preserve values as-in in its output. It may "unpack" it from the token (as in, return it as a part of a plain str) but the value content must not be changed nor re-ordered relative to other value tokens (as that could change the meaning of the field). )r r( r* r r r r g s z FormatterContentToken.is_valuec C r) )a� True if this formatter token represents a separator token The formatter is not required to preserve the provided separators but it is required to properly separate values. In fact, often is a lot easier to discard existing separator tokens. As an example, in whitespace separated list of values space, tab and newline all counts as separator. However, formatting-wise, there is a world of difference between the a space, tab and a newline. In particularly, newlines must be followed by an additional space or tab (to act as a value continuation line) if there is a value following it (otherwise, the generated output is invalid). )r r" r* r r r r s s z"FormatterContentToken.is_separatorc C s | j tu o | j�� S )z:True if this formatter token represents a whitespace token)r r" r �isspacer* r r r r � s z#FormatterContentToken.is_whitespacec C � | j S )a� The actual context of the token This field *must not* be used to determine the type of token. The formatter cannot reliably tell whether "#..." is a comment or a value (it can be both). Use is_value and is_comment instead for discriminating token types. For value tokens, this the concrete value to be omitted. For comment token, this is the full comment text. This is the same as str(token). �r r* r r r r � s zFormatterContentToken.textc C r, r r- r* r r r �__str__� s z FormatterContentToken.__str__c C s d� | jj| j| j�S )Nz{}({!r}, {}=True))�format� __class__�__name__r r r* r r r �__repr__� s z FormatterContentToken.__repr__N)r1 � __module__� __qualname__�__doc__� __slots__r � classmethodr r$ r r �propertyr r r r r r. r2 r r r r r s0 r r r c c sx � t | �d }d| }d}|D ]*}|jr |rdV |V n|jr6|r&dV n|V |V |js2|V dV nqd}qdS )zCUse "one value per line, always trailing separator" formatting � r T� FN)�lenr r r )�name� sep_token�formatter_tokens� indent_len�indent� emitted_first�tr r r �%one_value_per_line_trailing_separator� s( � �rC c C s@ |dg}d}d}t |t�r|d }|jrtd��| |||�D ]q}t|�} t |t�rh|jrE|s2td��| �d�s;td��| �d�sDtd ��n |jrd| d � � sT| d � � rXtd ��|r^td ��|rdtd ��|j}nd}|r�| d dv rvtd��| d � � s�| �d�s�td��|� | � | �d�}q d� |�} | �d�s�td��| S )a� Format a field using a provided formatter This function formats a series of tokens using the provided formatter. It can be used as a standalone formatter engine and can be used in test suites to validate third-party formatters (enabling them to test for corner cases without involving parsing logic). The formatter receives series of FormatterContentTokens (via the token_iter) and is expected to yield one or more str or FormatterContentTokens. The calling function will combine all of these into a single string, which will be used as the value. The formatter is recommended to yield the provided value and comment tokens interleaved with text segments of whitespace and separators as part of its output. If it preserve comment and value tokens, the calling function can provide some runtime checks to catch bugs (like the formatter turning a comment into a value because it forgot to ensure that the comment was emitted directly after a newline character). When writing a formatter, please keep the following in mind: * The output of the formatter is appended directly after the ":" separator. Most formatters will want to emit either a space or a newline as the very first character for readability. (compare "Depends:foo\n" to "Depends: foo\n") * The formatter must always end its output on a newline. This is a design choice of how the round-trip safe parser represent values that is imposed on the formatter. * It is often easier to discard/ignore all separator tokens from the the provided token sequence and instead just yield separator tokens/str where the formatter wants to place them. - The formatter is strongly recommended to special-case formatting for whitespace separators (check for `separator_token.is_whitespace`). This is because space, tab and newline all counts as valid separators and can all appear in the token sequence. If the original field uses a mix of these separators it is likely to completely undermine the desired result. Not to mention the additional complexity of handling when a separator token happens to use the newline character which affects how the formatter is supposed what comes after it (see the rules for comments, empty lines and continuation line markers). * The formatter must remember to emit a "continuation line" marker (typically a single space or tab) when emitting a value after a newline or a comment. A `yield " "` is sufficient. - The continuation line marker may be embedded inside a str with other whitespace (such as the newline coming before it or/and whitespace used for indentation purposes following the marker). * The formatter must not cause the output to contain completely empty/whitespace lines as these cause syntax errors. The first line never counts as an empty line (as it will be appended after the field name). * Tokens must be discriminated via the `token.is_value` (etc.) properties. Assuming that `token.text.startswith("#")` implies a comment and similar stunts are wrong. As an example, "#foo" is a perfectly valid value in some contexts. * Comment tokens *always* take up exactly one complete line including the newline character at the end of the line. They must be emitted directly after a newline character or another comment token. * Special cases that are rare but can happen: - Fields *can* start with comments and requires a formatter provided newline. (Example: "Depends:\n# Comment here\n foo") - Fields *can* start on a separator or have two separators in a row. This is especially true for whitespace separated fields where every whitespace counts as a separator, but it can also happen with other separators (such as comma). - Value tokens can contain whitespace (for non-whitespace separators). When they do, the formatter must not attempt change nor "normalize" the whitespace inside the value token as that might change how the value is interpreted. (If you want to normalize such whitespace, the formatter is at the wrong abstraction level. Instead, manipulate the values directly in the value interpretation layer) This function will provide *some* runtime checks of its input and the output from the formatter to detect some errors early and provide helpful diagnostics. If you use the function for testing, you are recommended to rely on verifying the output of the function rather than relying on the runtime checks (as these are subject to change). :param formatter: A formatter (see FormatterCallback for an example) :param field_name: The name of the field. :param separator_token: One of SPACE_SEPARATOR and COMMA_SEPARATOR :param token_iter: An iterable of tokens to be formatted. The following example shows how to define a formatter_callback along with a few verifications. >>> fmt = one_value_per_line_trailing_separator >>> # Omit separator tokens for in the token list for simplicity (the formatter does >>> # not use them and it enables us to keep the example simple by reusing the list) >>> tokens = [ ... FormatterContentToken.value_token("foo"), ... FormatterContentToken.comment_token("# some comment about bar\n"), ... FormatterContentToken.value_token("bar"), ... ] >>> print(format_field(fmt, "Depends", COMMA_SEPARATOR_FT, tokens), end='') Depends: foo, # some comment about bar bar, >>> print(format_field(fmt, "Architecture", SPACE_SEPARATOR_FT, tokens), end='') Architecture: foo # some comment about bar bar >>> # Control check for the special case where the field starts with a comment >>> print(format_field(fmt, "Depends", COMMA_SEPARATOR_FT, tokens[1:]), end='') Depends: # some comment about bar bar, >>> # Also, check single line values (to ensure it ends on a newline) >>> print(format_field(fmt, "Depends", COMMA_SEPARATOR_FT, tokens[2:]), end='') Depends: bar, �:F���z9Invalid token_iter: Field values cannot end with commentsz:Bad format: Comments must appear directly after a newline.�#z(Invalid Comment token: Must start with #r: z,Invalid Comment token: Must end on a newliner z:Invalid Value token: It cannot start nor end on whitespacez,Bad format: Missing continuation line markerz)Bad format: Formatter omitted a separator)� r: z&Bad format: Saw completely empty line.� z1Bad format: The field value must end on a newline) r �listr r �strr � startswith�endswithr r+ �append�join) � formatter� field_namer$ � token_iter�formatted_tokens�just_after_newline�last_was_value_token� last_token�token� token_as_text�formatted_textr r r � format_field� sN � rY N)�debian._deb822_repro.tokensr r( r& r" �typingr r �debian._deb822_repro.typesr r � ImportError�objectr r r! rC rY r r r r �<module> s � !