diff options
| author | CoprDistGit <infra@openeuler.org> | 2023-05-15 06:35:38 +0000 |
|---|---|---|
| committer | CoprDistGit <infra@openeuler.org> | 2023-05-15 06:35:38 +0000 |
| commit | 13e31805d68396b31dfe35c2de97d40cf0d5bea0 (patch) | |
| tree | 56f69b61aafa7b3f1a4e0d9ac9e1471c60c2db76 /python-inifix.spec | |
| parent | f0f82210d6ff3fca3a8e37a5bc70dd9e941281ff (diff) | |
automatic import of python-inifix
Diffstat (limited to 'python-inifix.spec')
| -rw-r--r-- | python-inifix.spec | 856 |
1 files changed, 856 insertions, 0 deletions
diff --git a/python-inifix.spec b/python-inifix.spec new file mode 100644 index 0000000..362d820 --- /dev/null +++ b/python-inifix.spec @@ -0,0 +1,856 @@ +%global _empty_manifest_terminate_build 0 +Name: python-inifix +Version: 4.3.2 +Release: 1 +Summary: I/O facility for Idefix/Pluto configuration files +License: GPL-3.0 +URL: https://github.com/neutrinoceros/inifix +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/76/ab/5944e99fc27eea171b392dba2c3da266d1fa3278e7ed2f83519f53460993/inifix-4.3.2.tar.gz +BuildArch: noarch + +Requires: python3-more-itertools + +%description +# `inifix` + +[](https://pypi.org/project/inifix/) +[](https://pypi.org/project/inifix/) +[](https://results.pre-commit.ci/badge/github/neutrinoceros/inifix/main.svg) +[](https://github.com/psf/black) +[](https://github.com/charliermarsh/ruff) + + +`inifix` is a small Python library of I/O functions to read and write 'ini' +configuration files in the style of [Pluto](http://plutocode.ph.unito.it) and +[Idefix](https://gricad-gitlab.univ-grenoble-alpes.fr/lesurg/idefix-public). + +While its primary goal is to follow Idefix's 'ini' format specification, it +supports a small superset of it. + +The key differences are: +- `inifix` supports section-free definitions. This means configuration files + from [FARGO 3D](https://fargo3d.bitbucket.io) are also supported. +- in `inifix`, strings can be escaped using `'` or `"`. This allows to have + whitespaces in string values and to force string type decoding where numeric + and boolean types would work. + +In rare cases where Idefix's 'ini' format doesn't match Pluto's, `inifix` will +follow the former. Known differences are: +- Idefix allows booleans to be written as `yes` and `no`. +- Idefix allows integers to be written using scientific notation (e.g. `1e3`) + +## File format specifications details +<details><summary>Unroll !</summary> +- parameter names are strings +- names and values are separated by non-newline white spaces +- values are represented in unicode characters +- all values are considered numbers if possible (e.g., `1e3` is read as `1000`) +- number values are read as integers if no loss of precision ensues, and floats otherwise +- `true` and `false` (resp. `yes` and `no`) are cast to booleans (case-insensitive) +- values that can't be read as number or booleans are read as strings. +- string delimiters `"` and `'` can be used for strings containing whitespace, or to + force string type for values that would otherwise be read as numbers and booleans. +- a parameter can be associated to a single value or a list of whitespace-separated values +- sections titles start with `[` and end with `]` +- comments start with `#` and are ignored + +A file is considered valid if calling `inifix.load(<filename>)` doesn't raise an +error. + +### Examples +The following content is considered valid +```ini +# My awesome experiment +[Grid] +x 1 2 u 10 # a comment +y 4 5 l 100 +[Time Integrator] +CFL 1e-3 +tstop 1E3 +``` +and maps to +```json +{ + "Grid": { + "x": [1, 2, "u", 10], + "y": [4, 5, "l", 100] + }, + "Time Integrator": { + "CFL": 0.001, + "tstop": 1000.0 + } +} +``` +The following section-less format doesn't comply to Pluto/Idefix's +specifications, but it is considered valid for inifix. This is the one +intentional differences in specifications, which makes inifix format a superset +of Pluto's inifile format. +```ini +mode fargo + +# Time integrator +CFL 1e-3 +tstop 1e3 +``` +and maps to +```json +{ + "mode": "fargo", + "CFL": 0.001, + "tstop": 1000.0 +} +``` +Note that strings using e-notation (e.g. `1e-3` or `1E3` here) are decoded as +floats. Reversely, when writing files, floats are re-encoded using e-notation +if it leads to a more compact representation. For instance, `100000.0` is encoded +as `1e5`, but `189.0` is left unchanged because `1.89e2` takes one more character. +In cases where both reprensations are equally compact (e.g. `1.0` VS `1e0`), +decimal is prefered in encoding. + +While decoding, `e` can be lower or upper case, but they are always encoded as +lower case. +</details> + +## Installation + +```shell +python -m pip install inifix +``` + +## Usage + +The public API mimicks that of Python's standard library `json`, +and consists in four main functions: +- `inifix.load` and `inifix.dump` read from and write to files respectively +- `inifix.loads` reads from a `str` and returns a `dict`, while `inifix.dumps` + does the reverse operation. + +### Reading data +`inifix.load` reads from a file and returns a `dict` + +```python +import inifix + +with open("pluto.ini", "rb") as fh: + conf = inifix.load(fh) + +# or equivalently +conf = inifix.load("pluto.ini") +``` +Files are assumed to be encoded as UTF-8. + +`inifix.load` and `inifix.loads` accept a optional boolean flag +`parse_scalars_as_list` (new in `inifix` v4.0.0), that is useful to simplify +handling unknown data: all values can be safely treated as arrays, and iterated +over, even in the presence of scalar strings. For illustration + +```python +>>> import inifix +>>> from pprint import pprint +>>> pprint(inifix.load("example.ini")) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': 0.001, 'tstop': 1000.0}} +>>> pprint(inifix.load("ex.ini", parse_scalars_as_lists=True)) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': [0.001], 'tstop': [1000.0]}} +``` + +By default, `inifix.load` and `inifix.loads` validate input data. This step can +be skipped by specifying `skip_validation=True`. + +### ... and writing back to disk + +`inifix.dump` writes data back to a file. + +This allows to change a value on the fly and create new +configuration files programmatically, for instance. +```python +conf["Time"]["CFL"] = 0.1 + +with open("pluto-mod.ini", "wb") as fh: + inifix.dump(conf, fh) + +# or equivalently +inifix.dump(conf, "pluto-mod.ini") +``` +Data will be validated against inifix's format specification at write time. +Files are always encoded as UTF-8. + +`inifix.dumps` is the same as `inifix.dump` except that it returns a string +instead of writing to a file. + +By default, `inifix.dump` and `inifix.dumps` validate input data. This step can +be skipped by specifying `skip_validation=True`. + + +### Schema Validation + +`inifix.validate_inifile_schema` can be used to validate an arbitrary +dictionary as writable to an inifile, following Pluto/Idefix's format. This +will raise an exception (`ValueError`) if the dictionnary `data` is invalid. +```python +inifix.validate_inifile_schema(data) +``` + +### CLI + +Command line tools are shipped with the package to validate or format compatible +inifiles. + +#### Validation + +This checks that your inifiles can be loaded with `inifix.load` from the command line +```shell +$ inifix-validate pluto.ini +Validated pluto.ini +``` + + +#### Formatting + +To format a file in place, use +```shell +$ inifix-format pluto.ini +``` +inifix-format is guaranteed to preserve comments and to *only* edit (add or remove) +whitespace characters. + +Files are always encoded as UTF-8. + +To print a diff patch to stdout instead of editing the file, use the `--diff` flag +```shell +$ inifix-format pluto.ini --diff +``` + +By default, `inifix-format` also validates input data. This step can be skipped with the +`--skip-validation` flag + +### pre-commit hooks + +`inifix-validate` and `inifix-format` can be used as `pre-commit` hooks with the +following configuration (add to `.pre-commit-config.yaml`) + +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate +``` +or +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-format +``` + +Note that `inifix-format` also validates data by default, so it is redundant to +utilize both hooks. Validation and formatting may nonetheless be decoupled as +```patch + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate + - id: inifix-format ++ args: [--skip-validation] +``` + +By default, both hooks target files matching the regular expression `(\.ini)$`. +It is possible to override this expression as, e.g., +```patch + hooks: + - id: inifix-format ++ files: (\.ini|\.par)$ +``` + +## Testing + +We use the [pytest](https://docs.pytest.org/en/latest/) framework to test +`inifix`. The test suite can be run from the top level with a simple `pytest` +invocation. +```shell +$ python -m pip install --requirement requirements/tests.txt +$ pytest +``` + + +%package -n python3-inifix +Summary: I/O facility for Idefix/Pluto configuration files +Provides: python-inifix +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-inifix +# `inifix` + +[](https://pypi.org/project/inifix/) +[](https://pypi.org/project/inifix/) +[](https://results.pre-commit.ci/badge/github/neutrinoceros/inifix/main.svg) +[](https://github.com/psf/black) +[](https://github.com/charliermarsh/ruff) + + +`inifix` is a small Python library of I/O functions to read and write 'ini' +configuration files in the style of [Pluto](http://plutocode.ph.unito.it) and +[Idefix](https://gricad-gitlab.univ-grenoble-alpes.fr/lesurg/idefix-public). + +While its primary goal is to follow Idefix's 'ini' format specification, it +supports a small superset of it. + +The key differences are: +- `inifix` supports section-free definitions. This means configuration files + from [FARGO 3D](https://fargo3d.bitbucket.io) are also supported. +- in `inifix`, strings can be escaped using `'` or `"`. This allows to have + whitespaces in string values and to force string type decoding where numeric + and boolean types would work. + +In rare cases where Idefix's 'ini' format doesn't match Pluto's, `inifix` will +follow the former. Known differences are: +- Idefix allows booleans to be written as `yes` and `no`. +- Idefix allows integers to be written using scientific notation (e.g. `1e3`) + +## File format specifications details +<details><summary>Unroll !</summary> +- parameter names are strings +- names and values are separated by non-newline white spaces +- values are represented in unicode characters +- all values are considered numbers if possible (e.g., `1e3` is read as `1000`) +- number values are read as integers if no loss of precision ensues, and floats otherwise +- `true` and `false` (resp. `yes` and `no`) are cast to booleans (case-insensitive) +- values that can't be read as number or booleans are read as strings. +- string delimiters `"` and `'` can be used for strings containing whitespace, or to + force string type for values that would otherwise be read as numbers and booleans. +- a parameter can be associated to a single value or a list of whitespace-separated values +- sections titles start with `[` and end with `]` +- comments start with `#` and are ignored + +A file is considered valid if calling `inifix.load(<filename>)` doesn't raise an +error. + +### Examples +The following content is considered valid +```ini +# My awesome experiment +[Grid] +x 1 2 u 10 # a comment +y 4 5 l 100 +[Time Integrator] +CFL 1e-3 +tstop 1E3 +``` +and maps to +```json +{ + "Grid": { + "x": [1, 2, "u", 10], + "y": [4, 5, "l", 100] + }, + "Time Integrator": { + "CFL": 0.001, + "tstop": 1000.0 + } +} +``` +The following section-less format doesn't comply to Pluto/Idefix's +specifications, but it is considered valid for inifix. This is the one +intentional differences in specifications, which makes inifix format a superset +of Pluto's inifile format. +```ini +mode fargo + +# Time integrator +CFL 1e-3 +tstop 1e3 +``` +and maps to +```json +{ + "mode": "fargo", + "CFL": 0.001, + "tstop": 1000.0 +} +``` +Note that strings using e-notation (e.g. `1e-3` or `1E3` here) are decoded as +floats. Reversely, when writing files, floats are re-encoded using e-notation +if it leads to a more compact representation. For instance, `100000.0` is encoded +as `1e5`, but `189.0` is left unchanged because `1.89e2` takes one more character. +In cases where both reprensations are equally compact (e.g. `1.0` VS `1e0`), +decimal is prefered in encoding. + +While decoding, `e` can be lower or upper case, but they are always encoded as +lower case. +</details> + +## Installation + +```shell +python -m pip install inifix +``` + +## Usage + +The public API mimicks that of Python's standard library `json`, +and consists in four main functions: +- `inifix.load` and `inifix.dump` read from and write to files respectively +- `inifix.loads` reads from a `str` and returns a `dict`, while `inifix.dumps` + does the reverse operation. + +### Reading data +`inifix.load` reads from a file and returns a `dict` + +```python +import inifix + +with open("pluto.ini", "rb") as fh: + conf = inifix.load(fh) + +# or equivalently +conf = inifix.load("pluto.ini") +``` +Files are assumed to be encoded as UTF-8. + +`inifix.load` and `inifix.loads` accept a optional boolean flag +`parse_scalars_as_list` (new in `inifix` v4.0.0), that is useful to simplify +handling unknown data: all values can be safely treated as arrays, and iterated +over, even in the presence of scalar strings. For illustration + +```python +>>> import inifix +>>> from pprint import pprint +>>> pprint(inifix.load("example.ini")) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': 0.001, 'tstop': 1000.0}} +>>> pprint(inifix.load("ex.ini", parse_scalars_as_lists=True)) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': [0.001], 'tstop': [1000.0]}} +``` + +By default, `inifix.load` and `inifix.loads` validate input data. This step can +be skipped by specifying `skip_validation=True`. + +### ... and writing back to disk + +`inifix.dump` writes data back to a file. + +This allows to change a value on the fly and create new +configuration files programmatically, for instance. +```python +conf["Time"]["CFL"] = 0.1 + +with open("pluto-mod.ini", "wb") as fh: + inifix.dump(conf, fh) + +# or equivalently +inifix.dump(conf, "pluto-mod.ini") +``` +Data will be validated against inifix's format specification at write time. +Files are always encoded as UTF-8. + +`inifix.dumps` is the same as `inifix.dump` except that it returns a string +instead of writing to a file. + +By default, `inifix.dump` and `inifix.dumps` validate input data. This step can +be skipped by specifying `skip_validation=True`. + + +### Schema Validation + +`inifix.validate_inifile_schema` can be used to validate an arbitrary +dictionary as writable to an inifile, following Pluto/Idefix's format. This +will raise an exception (`ValueError`) if the dictionnary `data` is invalid. +```python +inifix.validate_inifile_schema(data) +``` + +### CLI + +Command line tools are shipped with the package to validate or format compatible +inifiles. + +#### Validation + +This checks that your inifiles can be loaded with `inifix.load` from the command line +```shell +$ inifix-validate pluto.ini +Validated pluto.ini +``` + + +#### Formatting + +To format a file in place, use +```shell +$ inifix-format pluto.ini +``` +inifix-format is guaranteed to preserve comments and to *only* edit (add or remove) +whitespace characters. + +Files are always encoded as UTF-8. + +To print a diff patch to stdout instead of editing the file, use the `--diff` flag +```shell +$ inifix-format pluto.ini --diff +``` + +By default, `inifix-format` also validates input data. This step can be skipped with the +`--skip-validation` flag + +### pre-commit hooks + +`inifix-validate` and `inifix-format` can be used as `pre-commit` hooks with the +following configuration (add to `.pre-commit-config.yaml`) + +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate +``` +or +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-format +``` + +Note that `inifix-format` also validates data by default, so it is redundant to +utilize both hooks. Validation and formatting may nonetheless be decoupled as +```patch + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate + - id: inifix-format ++ args: [--skip-validation] +``` + +By default, both hooks target files matching the regular expression `(\.ini)$`. +It is possible to override this expression as, e.g., +```patch + hooks: + - id: inifix-format ++ files: (\.ini|\.par)$ +``` + +## Testing + +We use the [pytest](https://docs.pytest.org/en/latest/) framework to test +`inifix`. The test suite can be run from the top level with a simple `pytest` +invocation. +```shell +$ python -m pip install --requirement requirements/tests.txt +$ pytest +``` + + +%package help +Summary: Development documents and examples for inifix +Provides: python3-inifix-doc +%description help +# `inifix` + +[](https://pypi.org/project/inifix/) +[](https://pypi.org/project/inifix/) +[](https://results.pre-commit.ci/badge/github/neutrinoceros/inifix/main.svg) +[](https://github.com/psf/black) +[](https://github.com/charliermarsh/ruff) + + +`inifix` is a small Python library of I/O functions to read and write 'ini' +configuration files in the style of [Pluto](http://plutocode.ph.unito.it) and +[Idefix](https://gricad-gitlab.univ-grenoble-alpes.fr/lesurg/idefix-public). + +While its primary goal is to follow Idefix's 'ini' format specification, it +supports a small superset of it. + +The key differences are: +- `inifix` supports section-free definitions. This means configuration files + from [FARGO 3D](https://fargo3d.bitbucket.io) are also supported. +- in `inifix`, strings can be escaped using `'` or `"`. This allows to have + whitespaces in string values and to force string type decoding where numeric + and boolean types would work. + +In rare cases where Idefix's 'ini' format doesn't match Pluto's, `inifix` will +follow the former. Known differences are: +- Idefix allows booleans to be written as `yes` and `no`. +- Idefix allows integers to be written using scientific notation (e.g. `1e3`) + +## File format specifications details +<details><summary>Unroll !</summary> +- parameter names are strings +- names and values are separated by non-newline white spaces +- values are represented in unicode characters +- all values are considered numbers if possible (e.g., `1e3` is read as `1000`) +- number values are read as integers if no loss of precision ensues, and floats otherwise +- `true` and `false` (resp. `yes` and `no`) are cast to booleans (case-insensitive) +- values that can't be read as number or booleans are read as strings. +- string delimiters `"` and `'` can be used for strings containing whitespace, or to + force string type for values that would otherwise be read as numbers and booleans. +- a parameter can be associated to a single value or a list of whitespace-separated values +- sections titles start with `[` and end with `]` +- comments start with `#` and are ignored + +A file is considered valid if calling `inifix.load(<filename>)` doesn't raise an +error. + +### Examples +The following content is considered valid +```ini +# My awesome experiment +[Grid] +x 1 2 u 10 # a comment +y 4 5 l 100 +[Time Integrator] +CFL 1e-3 +tstop 1E3 +``` +and maps to +```json +{ + "Grid": { + "x": [1, 2, "u", 10], + "y": [4, 5, "l", 100] + }, + "Time Integrator": { + "CFL": 0.001, + "tstop": 1000.0 + } +} +``` +The following section-less format doesn't comply to Pluto/Idefix's +specifications, but it is considered valid for inifix. This is the one +intentional differences in specifications, which makes inifix format a superset +of Pluto's inifile format. +```ini +mode fargo + +# Time integrator +CFL 1e-3 +tstop 1e3 +``` +and maps to +```json +{ + "mode": "fargo", + "CFL": 0.001, + "tstop": 1000.0 +} +``` +Note that strings using e-notation (e.g. `1e-3` or `1E3` here) are decoded as +floats. Reversely, when writing files, floats are re-encoded using e-notation +if it leads to a more compact representation. For instance, `100000.0` is encoded +as `1e5`, but `189.0` is left unchanged because `1.89e2` takes one more character. +In cases where both reprensations are equally compact (e.g. `1.0` VS `1e0`), +decimal is prefered in encoding. + +While decoding, `e` can be lower or upper case, but they are always encoded as +lower case. +</details> + +## Installation + +```shell +python -m pip install inifix +``` + +## Usage + +The public API mimicks that of Python's standard library `json`, +and consists in four main functions: +- `inifix.load` and `inifix.dump` read from and write to files respectively +- `inifix.loads` reads from a `str` and returns a `dict`, while `inifix.dumps` + does the reverse operation. + +### Reading data +`inifix.load` reads from a file and returns a `dict` + +```python +import inifix + +with open("pluto.ini", "rb") as fh: + conf = inifix.load(fh) + +# or equivalently +conf = inifix.load("pluto.ini") +``` +Files are assumed to be encoded as UTF-8. + +`inifix.load` and `inifix.loads` accept a optional boolean flag +`parse_scalars_as_list` (new in `inifix` v4.0.0), that is useful to simplify +handling unknown data: all values can be safely treated as arrays, and iterated +over, even in the presence of scalar strings. For illustration + +```python +>>> import inifix +>>> from pprint import pprint +>>> pprint(inifix.load("example.ini")) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': 0.001, 'tstop': 1000.0}} +>>> pprint(inifix.load("ex.ini", parse_scalars_as_lists=True)) +{'Grid': {'x': [1, 2, 'u', 10], 'y': [4, 5, 'l', 100]}, + 'Time Integrator': {'CFL': [0.001], 'tstop': [1000.0]}} +``` + +By default, `inifix.load` and `inifix.loads` validate input data. This step can +be skipped by specifying `skip_validation=True`. + +### ... and writing back to disk + +`inifix.dump` writes data back to a file. + +This allows to change a value on the fly and create new +configuration files programmatically, for instance. +```python +conf["Time"]["CFL"] = 0.1 + +with open("pluto-mod.ini", "wb") as fh: + inifix.dump(conf, fh) + +# or equivalently +inifix.dump(conf, "pluto-mod.ini") +``` +Data will be validated against inifix's format specification at write time. +Files are always encoded as UTF-8. + +`inifix.dumps` is the same as `inifix.dump` except that it returns a string +instead of writing to a file. + +By default, `inifix.dump` and `inifix.dumps` validate input data. This step can +be skipped by specifying `skip_validation=True`. + + +### Schema Validation + +`inifix.validate_inifile_schema` can be used to validate an arbitrary +dictionary as writable to an inifile, following Pluto/Idefix's format. This +will raise an exception (`ValueError`) if the dictionnary `data` is invalid. +```python +inifix.validate_inifile_schema(data) +``` + +### CLI + +Command line tools are shipped with the package to validate or format compatible +inifiles. + +#### Validation + +This checks that your inifiles can be loaded with `inifix.load` from the command line +```shell +$ inifix-validate pluto.ini +Validated pluto.ini +``` + + +#### Formatting + +To format a file in place, use +```shell +$ inifix-format pluto.ini +``` +inifix-format is guaranteed to preserve comments and to *only* edit (add or remove) +whitespace characters. + +Files are always encoded as UTF-8. + +To print a diff patch to stdout instead of editing the file, use the `--diff` flag +```shell +$ inifix-format pluto.ini --diff +``` + +By default, `inifix-format` also validates input data. This step can be skipped with the +`--skip-validation` flag + +### pre-commit hooks + +`inifix-validate` and `inifix-format` can be used as `pre-commit` hooks with the +following configuration (add to `.pre-commit-config.yaml`) + +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate +``` +or +```yaml + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-format +``` + +Note that `inifix-format` also validates data by default, so it is redundant to +utilize both hooks. Validation and formatting may nonetheless be decoupled as +```patch + - repo: https://github.com/neutrinoceros/inifix.git + rev: v4.3.2 + hooks: + - id: inifix-validate + - id: inifix-format ++ args: [--skip-validation] +``` + +By default, both hooks target files matching the regular expression `(\.ini)$`. +It is possible to override this expression as, e.g., +```patch + hooks: + - id: inifix-format ++ files: (\.ini|\.par)$ +``` + +## Testing + +We use the [pytest](https://docs.pytest.org/en/latest/) framework to test +`inifix`. The test suite can be run from the top level with a simple `pytest` +invocation. +```shell +$ python -m pip install --requirement requirements/tests.txt +$ pytest +``` + + +%prep +%autosetup -n inifix-4.3.2 + +%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-inifix -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 4.3.2-1 +- Package Spec generated |