automatic import of python-pyicumessageformatopeneuler20.03

3 files changed, 818 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..2704020 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/pyicumessageformat-1.0.0.tar.gz
diff --git a/python-pyicumessageformat.spec b/python-pyicumessageformat.spec
new file mode 100644
index 0000000..bed9409
--- /dev/null
+++ b/python-pyicumessageformat.spec
@@ -0,0 +1,816 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pyicumessageformat
+Version:	1.0.0
+Release:	1
+Summary:	An unopinionated parser for ICU MessageFormat.
+License:	MIT License
+URL:		https://github.com/sirstendec/pyicumessageformat
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/9b/2a/2f12fd041d92adc361ba413df5abfb1d3e5adf62e3ec00e9e4fac04674cc/pyicumessageformat-1.0.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+# pyicumessageformat
+
+An unopinionated library for parsing ICU MessageFormat messages into both
+ASTs and, optionally, token lists.
+
+This library is mainly a re-implementation of the JavaScript library
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+with a few extra configuration flags.
+
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+and `pyicumessageformat` are both licensed MIT.
+
+
+## Parser Options
+
+```python
+from pyicumessageformat import Parser
+
+# The following are the default values for the various available
+# settings for the Parser.
+parser = Parser({
+    # Whether or not to include indices on placeholder objects.
+    'include_indices': False,
+
+    # Maximum depth limits the nesting depth of sub-messages. This is
+    # done to avoid throwing a RecursionError.
+    'maximum_depth': 50,
+
+    # Known types that include sub-messages.
+    'submessage_types': ['plural', 'selectordinal', 'select'],
+
+    # Sub-message types that are numeric and support "#" in sub-messages.
+    'subnumeric_types': ['plural', 'selectordinal'],
+
+    # Whether or not to parse simple XML-style tags. When this is False,
+    # XML-style tags will be treated as plain text.
+    'allow_tags': False,
+
+    # The type that should be set for tags. This should be set to a
+    # unique value that will not overlap with any placeholder types.
+    'tag_type': 'tag',
+
+    # When enabled, strict tags makes the system far less forgiving
+    # about dangling '<' characters in input strings.
+    'strict_tags': False,
+
+    # If this is set, tag names must start with the provided string,
+    # otherwise the tag will be ignored and treated as plain text.
+    # This is overridden by strict_tags, which will always require a
+    # tag opening character to be treated as a tag.
+    'tag_prefix': None,
+
+    # Whether or not to parse sub-messages for unknown types. When this
+    # is set to False and an unknown type has sub-messages, a syntax
+    # error will be raised.
+    'loose_submessages': False,
+
+    # Whether or not spaces should be allowed in format strings.
+    'allow_format_spaces': True,
+
+    # Whether or not the parser should require known types with
+    # sub-messages to have an "other" selector.
+    # See "Require Other" below in README for more details.
+    'require_other': True
+})
+```
+
+### Require Other
+
+The `require_other` setting has a few valid possible values.
+
+* `True`: All known sub-message types are required to have an "other"
+    selector.
+* `False`: No types are required to have an "other" selector.
+* `"subnumeric"`: All known numeric sub-message types are required to have an
+    "other" selector.
+* `"all"`: All types, including unknown types, with sub-messages are required
+    to have an "other" selector.
+
+Additionally, `require_other` can be a list of types. In that event, only those
+types will be required to have an "other" selector.
+
+
+## Tags
+
+By default, tags are not handled in any way. By setting `allow_tags` to True,
+rudimentary support for simple XML-style tags is enabled. In this mode, the
+parser will look for tag opening (`<`) characters and attempt to read a tag.
+If the tag opening is not followed by either a forward slash (`/`) or a
+letter A-Z, the tag will be ignored. If the tag is followed by a forward
+slash, but not then followed by a valid string, then it will not be matched.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`
+Matches, but errors: `<hi`, `<unending`
+Does Not Match: `i <3 programming`, `3 < 4`, `</`
+
+By setting a string to `tag_prefix`, you can only match tags that start with
+a specific string. For example, if you set the tag prefix to `x:` then only
+tags starting with `x:` will be matched.
+
+Matches with `x:`: `<x:link>`, `<x:strong>`, `</x:link>`
+Matches, but errors: `<x:link`,
+Does Not Match: `Usage: /ban <user>`
+
+Finally, you can enable `strict_tags` to require all tag opening (`<`) characters
+to be treated as part of a tag. In strict tags mode, all `<` characters *must*
+be escaped if they are not part of a tag. `tag_prefix` is ignored when strict
+tags are enabled.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`,
+Matches, but errors: `<hi`, `<unending`, `</`, `i <3 programming`, `3 < 4`
+Does Not Match: `i '<'3 programming`
+
+
+## Parsing
+
+The Parser has a single method that is intended to be called externally:
+
+### `parse(input: str, tokens?: list) -> AST`
+
+Simply pass in a string, and get an AST back:
+
+```python
+>>> ast = parser.parse('''Hello, <b>{firstName}</b>! You have {messages, plural,
+    =0 {no messages}
+    =1 {one message}
+    other {# messages}
+} and you're {completion, number, percentage} done.''')
+>>> ast
+[
+    'Hello, ',
+    {
+        'name': 'b',
+        'type': 'tag',
+        'contents': [
+            {
+                'name': 'firstName'
+            }
+        ]
+    },
+    '! You have ',
+    {
+        'name': 'messages',
+        'type': 'plural',
+        'options': {
+            '=0': ['no messages'],
+            '=1': ['one message'],
+            'other': [
+                {
+                    'name': 'messages',
+                    'type': 'number'
+                },
+                ' messages'
+            ]
+        }
+    },
+    " and you're ",
+    {
+        'name': 'completion',
+        'type': 'number',
+        'format': 'percentage'
+    },
+    ' done.'
+]
+```
+
+If there is an error in the message, `parse(...)` will raise a
+`SyntaxError`:
+
+```python
+>>> parser.parse('Hello, {name{!')
+SyntaxError: Expected , or } at position 12 but found {
+```
+
+If you include an empty list for `tokens`, you can also get back your
+input in a tokenized format. Please note that tokenization stops
+when an error is encountered:
+
+```python
+>>> tokens = []
+>>> parse('Hello, {firstName}! You are {age, number} years old.', tokens)
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'firstName'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', 'text': '! You are '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'age'},
+    {'type': 'syntax', 'text': ','},
+    {'type': 'space', 'text': ' '},
+    {'type': 'type', 'text': 'number'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', ' years old.'}
+]
+
+>>> tokens = []
+>>> parser.parse('Hello, {name{!', tokens)
+SyntaxError: Expected , or } at position 12 but found {
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'name'}
+]
+```
+
+## AST Format
+
+```typescript
+type AST = Node[];
+type Node = string | Placeholder;
+
+type Placeholder = Tag | Variable;
+
+type Tag = {
+    name: string;
+    type: 'tag';
+    contents?: AST;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+};
+
+type Variable = {
+    name: string;
+    type?: string;
+    offset?: number;
+    format?: string;
+    options?: Submessages;
+
+    // If hash is present, it should be true and indicate
+    // that the variable was a hash (#).
+    hash?: true;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+}
+
+type Submessages = {
+    [selector: string]: AST;
+};
+```
+
+
+
+
+%package -n python3-pyicumessageformat
+Summary:	An unopinionated parser for ICU MessageFormat.
+Provides:	python-pyicumessageformat
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pyicumessageformat
+# pyicumessageformat
+
+An unopinionated library for parsing ICU MessageFormat messages into both
+ASTs and, optionally, token lists.
+
+This library is mainly a re-implementation of the JavaScript library
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+with a few extra configuration flags.
+
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+and `pyicumessageformat` are both licensed MIT.
+
+
+## Parser Options
+
+```python
+from pyicumessageformat import Parser
+
+# The following are the default values for the various available
+# settings for the Parser.
+parser = Parser({
+    # Whether or not to include indices on placeholder objects.
+    'include_indices': False,
+
+    # Maximum depth limits the nesting depth of sub-messages. This is
+    # done to avoid throwing a RecursionError.
+    'maximum_depth': 50,
+
+    # Known types that include sub-messages.
+    'submessage_types': ['plural', 'selectordinal', 'select'],
+
+    # Sub-message types that are numeric and support "#" in sub-messages.
+    'subnumeric_types': ['plural', 'selectordinal'],
+
+    # Whether or not to parse simple XML-style tags. When this is False,
+    # XML-style tags will be treated as plain text.
+    'allow_tags': False,
+
+    # The type that should be set for tags. This should be set to a
+    # unique value that will not overlap with any placeholder types.
+    'tag_type': 'tag',
+
+    # When enabled, strict tags makes the system far less forgiving
+    # about dangling '<' characters in input strings.
+    'strict_tags': False,
+
+    # If this is set, tag names must start with the provided string,
+    # otherwise the tag will be ignored and treated as plain text.
+    # This is overridden by strict_tags, which will always require a
+    # tag opening character to be treated as a tag.
+    'tag_prefix': None,
+
+    # Whether or not to parse sub-messages for unknown types. When this
+    # is set to False and an unknown type has sub-messages, a syntax
+    # error will be raised.
+    'loose_submessages': False,
+
+    # Whether or not spaces should be allowed in format strings.
+    'allow_format_spaces': True,
+
+    # Whether or not the parser should require known types with
+    # sub-messages to have an "other" selector.
+    # See "Require Other" below in README for more details.
+    'require_other': True
+})
+```
+
+### Require Other
+
+The `require_other` setting has a few valid possible values.
+
+* `True`: All known sub-message types are required to have an "other"
+    selector.
+* `False`: No types are required to have an "other" selector.
+* `"subnumeric"`: All known numeric sub-message types are required to have an
+    "other" selector.
+* `"all"`: All types, including unknown types, with sub-messages are required
+    to have an "other" selector.
+
+Additionally, `require_other` can be a list of types. In that event, only those
+types will be required to have an "other" selector.
+
+
+## Tags
+
+By default, tags are not handled in any way. By setting `allow_tags` to True,
+rudimentary support for simple XML-style tags is enabled. In this mode, the
+parser will look for tag opening (`<`) characters and attempt to read a tag.
+If the tag opening is not followed by either a forward slash (`/`) or a
+letter A-Z, the tag will be ignored. If the tag is followed by a forward
+slash, but not then followed by a valid string, then it will not be matched.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`
+Matches, but errors: `<hi`, `<unending`
+Does Not Match: `i <3 programming`, `3 < 4`, `</`
+
+By setting a string to `tag_prefix`, you can only match tags that start with
+a specific string. For example, if you set the tag prefix to `x:` then only
+tags starting with `x:` will be matched.
+
+Matches with `x:`: `<x:link>`, `<x:strong>`, `</x:link>`
+Matches, but errors: `<x:link`,
+Does Not Match: `Usage: /ban <user>`
+
+Finally, you can enable `strict_tags` to require all tag opening (`<`) characters
+to be treated as part of a tag. In strict tags mode, all `<` characters *must*
+be escaped if they are not part of a tag. `tag_prefix` is ignored when strict
+tags are enabled.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`,
+Matches, but errors: `<hi`, `<unending`, `</`, `i <3 programming`, `3 < 4`
+Does Not Match: `i '<'3 programming`
+
+
+## Parsing
+
+The Parser has a single method that is intended to be called externally:
+
+### `parse(input: str, tokens?: list) -> AST`
+
+Simply pass in a string, and get an AST back:
+
+```python
+>>> ast = parser.parse('''Hello, <b>{firstName}</b>! You have {messages, plural,
+    =0 {no messages}
+    =1 {one message}
+    other {# messages}
+} and you're {completion, number, percentage} done.''')
+>>> ast
+[
+    'Hello, ',
+    {
+        'name': 'b',
+        'type': 'tag',
+        'contents': [
+            {
+                'name': 'firstName'
+            }
+        ]
+    },
+    '! You have ',
+    {
+        'name': 'messages',
+        'type': 'plural',
+        'options': {
+            '=0': ['no messages'],
+            '=1': ['one message'],
+            'other': [
+                {
+                    'name': 'messages',
+                    'type': 'number'
+                },
+                ' messages'
+            ]
+        }
+    },
+    " and you're ",
+    {
+        'name': 'completion',
+        'type': 'number',
+        'format': 'percentage'
+    },
+    ' done.'
+]
+```
+
+If there is an error in the message, `parse(...)` will raise a
+`SyntaxError`:
+
+```python
+>>> parser.parse('Hello, {name{!')
+SyntaxError: Expected , or } at position 12 but found {
+```
+
+If you include an empty list for `tokens`, you can also get back your
+input in a tokenized format. Please note that tokenization stops
+when an error is encountered:
+
+```python
+>>> tokens = []
+>>> parse('Hello, {firstName}! You are {age, number} years old.', tokens)
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'firstName'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', 'text': '! You are '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'age'},
+    {'type': 'syntax', 'text': ','},
+    {'type': 'space', 'text': ' '},
+    {'type': 'type', 'text': 'number'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', ' years old.'}
+]
+
+>>> tokens = []
+>>> parser.parse('Hello, {name{!', tokens)
+SyntaxError: Expected , or } at position 12 but found {
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'name'}
+]
+```
+
+## AST Format
+
+```typescript
+type AST = Node[];
+type Node = string | Placeholder;
+
+type Placeholder = Tag | Variable;
+
+type Tag = {
+    name: string;
+    type: 'tag';
+    contents?: AST;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+};
+
+type Variable = {
+    name: string;
+    type?: string;
+    offset?: number;
+    format?: string;
+    options?: Submessages;
+
+    // If hash is present, it should be true and indicate
+    // that the variable was a hash (#).
+    hash?: true;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+}
+
+type Submessages = {
+    [selector: string]: AST;
+};
+```
+
+
+
+
+%package help
+Summary:	Development documents and examples for pyicumessageformat
+Provides:	python3-pyicumessageformat-doc
+%description help
+# pyicumessageformat
+
+An unopinionated library for parsing ICU MessageFormat messages into both
+ASTs and, optionally, token lists.
+
+This library is mainly a re-implementation of the JavaScript library
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+with a few extra configuration flags.
+
+[format-message-parse](https://www.npmjs.com/package/format-message-parse)
+and `pyicumessageformat` are both licensed MIT.
+
+
+## Parser Options
+
+```python
+from pyicumessageformat import Parser
+
+# The following are the default values for the various available
+# settings for the Parser.
+parser = Parser({
+    # Whether or not to include indices on placeholder objects.
+    'include_indices': False,
+
+    # Maximum depth limits the nesting depth of sub-messages. This is
+    # done to avoid throwing a RecursionError.
+    'maximum_depth': 50,
+
+    # Known types that include sub-messages.
+    'submessage_types': ['plural', 'selectordinal', 'select'],
+
+    # Sub-message types that are numeric and support "#" in sub-messages.
+    'subnumeric_types': ['plural', 'selectordinal'],
+
+    # Whether or not to parse simple XML-style tags. When this is False,
+    # XML-style tags will be treated as plain text.
+    'allow_tags': False,
+
+    # The type that should be set for tags. This should be set to a
+    # unique value that will not overlap with any placeholder types.
+    'tag_type': 'tag',
+
+    # When enabled, strict tags makes the system far less forgiving
+    # about dangling '<' characters in input strings.
+    'strict_tags': False,
+
+    # If this is set, tag names must start with the provided string,
+    # otherwise the tag will be ignored and treated as plain text.
+    # This is overridden by strict_tags, which will always require a
+    # tag opening character to be treated as a tag.
+    'tag_prefix': None,
+
+    # Whether or not to parse sub-messages for unknown types. When this
+    # is set to False and an unknown type has sub-messages, a syntax
+    # error will be raised.
+    'loose_submessages': False,
+
+    # Whether or not spaces should be allowed in format strings.
+    'allow_format_spaces': True,
+
+    # Whether or not the parser should require known types with
+    # sub-messages to have an "other" selector.
+    # See "Require Other" below in README for more details.
+    'require_other': True
+})
+```
+
+### Require Other
+
+The `require_other` setting has a few valid possible values.
+
+* `True`: All known sub-message types are required to have an "other"
+    selector.
+* `False`: No types are required to have an "other" selector.
+* `"subnumeric"`: All known numeric sub-message types are required to have an
+    "other" selector.
+* `"all"`: All types, including unknown types, with sub-messages are required
+    to have an "other" selector.
+
+Additionally, `require_other` can be a list of types. In that event, only those
+types will be required to have an "other" selector.
+
+
+## Tags
+
+By default, tags are not handled in any way. By setting `allow_tags` to True,
+rudimentary support for simple XML-style tags is enabled. In this mode, the
+parser will look for tag opening (`<`) characters and attempt to read a tag.
+If the tag opening is not followed by either a forward slash (`/`) or a
+letter A-Z, the tag will be ignored. If the tag is followed by a forward
+slash, but not then followed by a valid string, then it will not be matched.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`
+Matches, but errors: `<hi`, `<unending`
+Does Not Match: `i <3 programming`, `3 < 4`, `</`
+
+By setting a string to `tag_prefix`, you can only match tags that start with
+a specific string. For example, if you set the tag prefix to `x:` then only
+tags starting with `x:` will be matched.
+
+Matches with `x:`: `<x:link>`, `<x:strong>`, `</x:link>`
+Matches, but errors: `<x:link`,
+Does Not Match: `Usage: /ban <user>`
+
+Finally, you can enable `strict_tags` to require all tag opening (`<`) characters
+to be treated as part of a tag. In strict tags mode, all `<` characters *must*
+be escaped if they are not part of a tag. `tag_prefix` is ignored when strict
+tags are enabled.
+
+Matches: `<b>`, `<strong>`, `<x:link>`, `</b>`,
+Matches, but errors: `<hi`, `<unending`, `</`, `i <3 programming`, `3 < 4`
+Does Not Match: `i '<'3 programming`
+
+
+## Parsing
+
+The Parser has a single method that is intended to be called externally:
+
+### `parse(input: str, tokens?: list) -> AST`
+
+Simply pass in a string, and get an AST back:
+
+```python
+>>> ast = parser.parse('''Hello, <b>{firstName}</b>! You have {messages, plural,
+    =0 {no messages}
+    =1 {one message}
+    other {# messages}
+} and you're {completion, number, percentage} done.''')
+>>> ast
+[
+    'Hello, ',
+    {
+        'name': 'b',
+        'type': 'tag',
+        'contents': [
+            {
+                'name': 'firstName'
+            }
+        ]
+    },
+    '! You have ',
+    {
+        'name': 'messages',
+        'type': 'plural',
+        'options': {
+            '=0': ['no messages'],
+            '=1': ['one message'],
+            'other': [
+                {
+                    'name': 'messages',
+                    'type': 'number'
+                },
+                ' messages'
+            ]
+        }
+    },
+    " and you're ",
+    {
+        'name': 'completion',
+        'type': 'number',
+        'format': 'percentage'
+    },
+    ' done.'
+]
+```
+
+If there is an error in the message, `parse(...)` will raise a
+`SyntaxError`:
+
+```python
+>>> parser.parse('Hello, {name{!')
+SyntaxError: Expected , or } at position 12 but found {
+```
+
+If you include an empty list for `tokens`, you can also get back your
+input in a tokenized format. Please note that tokenization stops
+when an error is encountered:
+
+```python
+>>> tokens = []
+>>> parse('Hello, {firstName}! You are {age, number} years old.', tokens)
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'firstName'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', 'text': '! You are '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'age'},
+    {'type': 'syntax', 'text': ','},
+    {'type': 'space', 'text': ' '},
+    {'type': 'type', 'text': 'number'},
+    {'type': 'syntax', 'text': '}'},
+    {'type': 'text', ' years old.'}
+]
+
+>>> tokens = []
+>>> parser.parse('Hello, {name{!', tokens)
+SyntaxError: Expected , or } at position 12 but found {
+>>> tokens
+[
+    {'type': 'text', 'text': 'Hello, '},
+    {'type': 'syntax', 'text': '{'},
+    {'type': 'name', 'text': 'name'}
+]
+```
+
+## AST Format
+
+```typescript
+type AST = Node[];
+type Node = string | Placeholder;
+
+type Placeholder = Tag | Variable;
+
+type Tag = {
+    name: string;
+    type: 'tag';
+    contents?: AST;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+};
+
+type Variable = {
+    name: string;
+    type?: string;
+    offset?: number;
+    format?: string;
+    options?: Submessages;
+
+    // If hash is present, it should be true and indicate
+    // that the variable was a hash (#).
+    hash?: true;
+
+    // start and end only included with include_indices
+    start?: number;
+    end?: number;
+}
+
+type Submessages = {
+    [selector: string]: AST;
+};
+```
+
+
+
+
+%prep
+%autosetup -n pyicumessageformat-1.0.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-pyicumessageformat -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..b05d7c8
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+c95aa6772f39a766536699f6bab064e3  pyicumessageformat-1.0.0.tar.gz