diff options
Diffstat (limited to 'python-f2format.spec')
| -rw-r--r-- | python-f2format.spec | 848 |
1 files changed, 848 insertions, 0 deletions
diff --git a/python-f2format.spec b/python-f2format.spec new file mode 100644 index 0000000..e88a32d --- /dev/null +++ b/python-f2format.spec @@ -0,0 +1,848 @@ +%global _empty_manifest_terminate_build 0 +Name: python-f2format +Version: 0.8.6 +Release: 1 +Summary: Back-port compiler for Python 3.6 f-string literals. +License: Apache Software License +URL: https://github.com/JarryShaw/f2format +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/13/7a/8b01cc5992117842f5891b4b629a79846ce8ade8600f2ee8b952ca4ea283/f2format-0.8.6.tar.gz +BuildArch: noarch + +Requires: python3-parso +Requires: python3-tbtrim + +%description +# f2format + +[](https://pepy.tech/count/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) + +[](https://travis-ci.org/JarryShaw/f2format) +[](https://codecov.io/gh/JarryShaw/f2format) +[](https://www.apache.org/licenses/LICENSE-2.0.html) +[](https://github.com/996icu/996.ICU/blob/master/LICENSE) + +> Write *f-string* in Python 3.6 flavour, and let `f2format` worry about back-port issues :beer: + +  Since [PEP 498](https://www.python.org/dev/peps/pep-0498/), Python introduced +*[f-string](https://docs.python.org/3/reference/lexical_analysis.html#formatted-string-literals)* +literals in version __3.6__. Though released ever since +[December 23, 2016](https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-0-final), Python +3.6 is still not widely used as expected. For those who are now used to *f-string*s, `f2format` +provides an intelligent, yet imperfect, solution of a **backport compiler** by converting +*f-string*s to `str.format` expressions, which guarantees you to always write *f-string*s in Python +3.6 flavour then compile for compatibility later. + +  `f2format` is inspired and assisted by my good mate [@gousaiyang](https://github.com/gousaiyang). +It functions by tokenising and parsing Python code into multiple abstract syntax trees (AST), +through which it shall synthesise and extract expressions from *f-string* literals, and then +reassemble the original string using `str.format` method. Besides +**[conversion](https://docs.python.org/3/library/string.html#format-string-syntax)** and +**[format specification](https://docs.python.org/3/library/string.html#formatspec)**, `f2format` +also considered and resolved +**[string concatenation](https://docs.python.org/3/reference/lexical_analysis.html#string-literal-concatenation)**. +Also, it always tries to maintain the original layout of source code, and accuracy of syntax. + +## Installation + +> Note that `f2format` only supports Python versions __since 3.3__ 🐍 + +  For macOS users, `f2format` is now available through [Homebrew](https://brew.sh): + +```sh +brew tap jarryshaw/tap +brew install f2format +# or simply, a one-liner +brew install jarryshaw/tap/f2format +``` + +  Simply run the following to install the current version from PyPI: + +```sh +pip install f2format +``` + +  Or install the latest version from the git repository: + +```sh +git clone https://github.com/JarryShaw/f2format.git +cd f2format +pip install -e . +# and to update at any time +git pull +``` + +## Basic Usage + +### CLI + +  It is fairly straightforward to use `f2format`: + +> context in `${...}` changes dynamically according to runtime environment + +```man +usage: f2format [options] <python source files and folders...> + +Convert f-string to str.format for Python 3 compatibility. + +positional arguments: + SOURCE python source files and folders to be converted (${CWD}) + +optional arguments: + -h, --help show this help message and exit + -V, --version show program's version number and exit + -q, --quiet run in quiet mode + +archive options: + duplicate original files in case there's any issue + + -na, --no-archive do not archive original files + -p PATH, --archive-path PATH + path to archive original files (${CWD}/archive) + +convert options: + compatibility configuration for non-unicode files + + -c CODING, --encoding CODING + encoding to open source files (${LOCALE_ENCODING}) + -v VERSION, --python VERSION + convert against Python version (${LATEST_VERSION}) +``` + +  `f2format` will read then convert all *f-string* literals in every Python file under this +path. In case there might be some problems with the conversion, `f2format` will duplicate all +original files it is to modify into `archive` directory ahead of the process, if `-n` not set. + +  For instance, the code will be converted as follows. + +```python +# the original code +var = f'foo{(1+2)*3:>5}bar{"a", "b"!r}boo' +# after `f2format` +var = 'foo{:>5}bar{!r}boo'.format((1+2)*3, ("a", "b")) +``` + +### Docker + +> Well... it's not published to the Docker Hub yet ;) + +  Considering `f2format` may be used in scenarios where Python is not reachable. +We provide also a Docker image for those poor little guys. + +  See +[`Dockerfile`](https://github.com/JarryShaw/f2format/blob/master/docker/Dockerfile) for more +information. + +### Bundled Executable + +> Coming soooooooooooon... + +  For the worst case, we also provide bundled executables of `f2format`. In such case, +you may simply download it then, voilà, it's ready for you. + +  Special thanks to [PyInstaller](https://www.pyinstaller.org) ❤️ + +## Developer Reference + +### Automator + +  [`make-demo.sh`](https://github.com/JarryShaw/f2format/blob/master/share/make-demo.sh) provides a +demo script, which may help integrate `f2format` in your development and distribution circle. + +> __NB__: `make-demo.sh` is not an integrated automation script. It should be revised by design. + +  It assumes + +- all source files in `/src` directory +- using GitHub for repository management +- having **release** branch under `/release` directory +- already installed `f2format` and [`twine`](https://github.com/pypa/twine#twine) +- permission to these files and folders granted + +  And it will + +- copy `setup.py` and `src` to `release` directory +- run `f2format` for Python files under `release` +- distribute to [PyPI](https://pypi.org) and [TestPyPI](https://test.pypi.org) using `twine` +- upload to release branch on GitHub +- upload original files to GitHub + +### Environments + +`f2format` currently supports three environment arguments: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) + +### APIs + +#### `f2format` -- wrapper works for conversion + +```python +f2format(filename) +``` + +Args: + +- `filename` -- `str`, file to be converted + +Envs: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### `convert` -- the main conversion process + +```python +convert(string, source='<unknown>') +``` + +Args: + +- `string` -- `str`, context to be converted +- `source` -- `str`, source of the context + +Envs: + +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Returns: + +- `str` -- converted string + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### Internal exceptions + +```python +class ConvertError(SyntaxError): + """Parso syntax error.""" +``` + +### Codec + +> NB: this project is now stalled, because I just cannot figure out how to play w/ codecs :) + +  [`f2format-codec`](https://github.com/JarryShaw/f2format-codec) registers a codec in Python +interpreter, which grants you the compatibility to write directly in Python 3.6 *f-string* syntax +even through running with a previous version of Python. + +## Test + +  The current test samples are under [`/test`](https://github.com/JarryShaw/f2format/blob/master/test) +folder. `test_driver.py` is the main entry point for tests. + +  For unittests, see [`test.py`](https://github.com/JarryShaw/f2format/blob/master/share/test.py). + +## Known issues + +  Since `f2format` is currently based on [`parso`](https://github.com/davidhalter/parso) project, +it had encountered several compatibility and parsing issues. + +* ~~Parsing f-strings with nested format specifiers produces incorrect SyntaxError ([#74](https://github.com/davidhalter/parso/issues/74))~~ + This issue has been resolved since `parso` version __0.5.0__. + +* Parsing f-strings with invalid quotes in expression part does not raise SyntaxError ([#86](https://github.com/davidhalter/parso/issues/86)) + +* Parsing f-strings with seeming assignment expressions produces incorrect SyntaxError ([#87](https://github.com/davidhalter/parso/issues/87)) + +## Contribution + +  Contributions are very welcome, especially fixing bugs and providing test cases, which +[@gousaiyang](https://github.com/gousaiyang) is to help with, so to speak. Note that code must +remain valid and reasonable. + +## See Also + +- [`babel`](https://github.com/jarryshaw/babel) +- [`poseur`](https://github.com/jarryshaw/poseur) +- [`walrus`](https://github.com/jarryshaw/walrus) +- [`vermin`](https://github.com/netromdk/vermin) + + + + +%package -n python3-f2format +Summary: Back-port compiler for Python 3.6 f-string literals. +Provides: python-f2format +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-f2format +# f2format + +[](https://pepy.tech/count/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) + +[](https://travis-ci.org/JarryShaw/f2format) +[](https://codecov.io/gh/JarryShaw/f2format) +[](https://www.apache.org/licenses/LICENSE-2.0.html) +[](https://github.com/996icu/996.ICU/blob/master/LICENSE) + +> Write *f-string* in Python 3.6 flavour, and let `f2format` worry about back-port issues :beer: + +  Since [PEP 498](https://www.python.org/dev/peps/pep-0498/), Python introduced +*[f-string](https://docs.python.org/3/reference/lexical_analysis.html#formatted-string-literals)* +literals in version __3.6__. Though released ever since +[December 23, 2016](https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-0-final), Python +3.6 is still not widely used as expected. For those who are now used to *f-string*s, `f2format` +provides an intelligent, yet imperfect, solution of a **backport compiler** by converting +*f-string*s to `str.format` expressions, which guarantees you to always write *f-string*s in Python +3.6 flavour then compile for compatibility later. + +  `f2format` is inspired and assisted by my good mate [@gousaiyang](https://github.com/gousaiyang). +It functions by tokenising and parsing Python code into multiple abstract syntax trees (AST), +through which it shall synthesise and extract expressions from *f-string* literals, and then +reassemble the original string using `str.format` method. Besides +**[conversion](https://docs.python.org/3/library/string.html#format-string-syntax)** and +**[format specification](https://docs.python.org/3/library/string.html#formatspec)**, `f2format` +also considered and resolved +**[string concatenation](https://docs.python.org/3/reference/lexical_analysis.html#string-literal-concatenation)**. +Also, it always tries to maintain the original layout of source code, and accuracy of syntax. + +## Installation + +> Note that `f2format` only supports Python versions __since 3.3__ 🐍 + +  For macOS users, `f2format` is now available through [Homebrew](https://brew.sh): + +```sh +brew tap jarryshaw/tap +brew install f2format +# or simply, a one-liner +brew install jarryshaw/tap/f2format +``` + +  Simply run the following to install the current version from PyPI: + +```sh +pip install f2format +``` + +  Or install the latest version from the git repository: + +```sh +git clone https://github.com/JarryShaw/f2format.git +cd f2format +pip install -e . +# and to update at any time +git pull +``` + +## Basic Usage + +### CLI + +  It is fairly straightforward to use `f2format`: + +> context in `${...}` changes dynamically according to runtime environment + +```man +usage: f2format [options] <python source files and folders...> + +Convert f-string to str.format for Python 3 compatibility. + +positional arguments: + SOURCE python source files and folders to be converted (${CWD}) + +optional arguments: + -h, --help show this help message and exit + -V, --version show program's version number and exit + -q, --quiet run in quiet mode + +archive options: + duplicate original files in case there's any issue + + -na, --no-archive do not archive original files + -p PATH, --archive-path PATH + path to archive original files (${CWD}/archive) + +convert options: + compatibility configuration for non-unicode files + + -c CODING, --encoding CODING + encoding to open source files (${LOCALE_ENCODING}) + -v VERSION, --python VERSION + convert against Python version (${LATEST_VERSION}) +``` + +  `f2format` will read then convert all *f-string* literals in every Python file under this +path. In case there might be some problems with the conversion, `f2format` will duplicate all +original files it is to modify into `archive` directory ahead of the process, if `-n` not set. + +  For instance, the code will be converted as follows. + +```python +# the original code +var = f'foo{(1+2)*3:>5}bar{"a", "b"!r}boo' +# after `f2format` +var = 'foo{:>5}bar{!r}boo'.format((1+2)*3, ("a", "b")) +``` + +### Docker + +> Well... it's not published to the Docker Hub yet ;) + +  Considering `f2format` may be used in scenarios where Python is not reachable. +We provide also a Docker image for those poor little guys. + +  See +[`Dockerfile`](https://github.com/JarryShaw/f2format/blob/master/docker/Dockerfile) for more +information. + +### Bundled Executable + +> Coming soooooooooooon... + +  For the worst case, we also provide bundled executables of `f2format`. In such case, +you may simply download it then, voilà, it's ready for you. + +  Special thanks to [PyInstaller](https://www.pyinstaller.org) ❤️ + +## Developer Reference + +### Automator + +  [`make-demo.sh`](https://github.com/JarryShaw/f2format/blob/master/share/make-demo.sh) provides a +demo script, which may help integrate `f2format` in your development and distribution circle. + +> __NB__: `make-demo.sh` is not an integrated automation script. It should be revised by design. + +  It assumes + +- all source files in `/src` directory +- using GitHub for repository management +- having **release** branch under `/release` directory +- already installed `f2format` and [`twine`](https://github.com/pypa/twine#twine) +- permission to these files and folders granted + +  And it will + +- copy `setup.py` and `src` to `release` directory +- run `f2format` for Python files under `release` +- distribute to [PyPI](https://pypi.org) and [TestPyPI](https://test.pypi.org) using `twine` +- upload to release branch on GitHub +- upload original files to GitHub + +### Environments + +`f2format` currently supports three environment arguments: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) + +### APIs + +#### `f2format` -- wrapper works for conversion + +```python +f2format(filename) +``` + +Args: + +- `filename` -- `str`, file to be converted + +Envs: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### `convert` -- the main conversion process + +```python +convert(string, source='<unknown>') +``` + +Args: + +- `string` -- `str`, context to be converted +- `source` -- `str`, source of the context + +Envs: + +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Returns: + +- `str` -- converted string + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### Internal exceptions + +```python +class ConvertError(SyntaxError): + """Parso syntax error.""" +``` + +### Codec + +> NB: this project is now stalled, because I just cannot figure out how to play w/ codecs :) + +  [`f2format-codec`](https://github.com/JarryShaw/f2format-codec) registers a codec in Python +interpreter, which grants you the compatibility to write directly in Python 3.6 *f-string* syntax +even through running with a previous version of Python. + +## Test + +  The current test samples are under [`/test`](https://github.com/JarryShaw/f2format/blob/master/test) +folder. `test_driver.py` is the main entry point for tests. + +  For unittests, see [`test.py`](https://github.com/JarryShaw/f2format/blob/master/share/test.py). + +## Known issues + +  Since `f2format` is currently based on [`parso`](https://github.com/davidhalter/parso) project, +it had encountered several compatibility and parsing issues. + +* ~~Parsing f-strings with nested format specifiers produces incorrect SyntaxError ([#74](https://github.com/davidhalter/parso/issues/74))~~ + This issue has been resolved since `parso` version __0.5.0__. + +* Parsing f-strings with invalid quotes in expression part does not raise SyntaxError ([#86](https://github.com/davidhalter/parso/issues/86)) + +* Parsing f-strings with seeming assignment expressions produces incorrect SyntaxError ([#87](https://github.com/davidhalter/parso/issues/87)) + +## Contribution + +  Contributions are very welcome, especially fixing bugs and providing test cases, which +[@gousaiyang](https://github.com/gousaiyang) is to help with, so to speak. Note that code must +remain valid and reasonable. + +## See Also + +- [`babel`](https://github.com/jarryshaw/babel) +- [`poseur`](https://github.com/jarryshaw/poseur) +- [`walrus`](https://github.com/jarryshaw/walrus) +- [`vermin`](https://github.com/netromdk/vermin) + + + + +%package help +Summary: Development documents and examples for f2format +Provides: python3-f2format-doc +%description help +# f2format + +[](https://pepy.tech/count/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) +[](https://pypi.org/project/f2format) + +[](https://travis-ci.org/JarryShaw/f2format) +[](https://codecov.io/gh/JarryShaw/f2format) +[](https://www.apache.org/licenses/LICENSE-2.0.html) +[](https://github.com/996icu/996.ICU/blob/master/LICENSE) + +> Write *f-string* in Python 3.6 flavour, and let `f2format` worry about back-port issues :beer: + +  Since [PEP 498](https://www.python.org/dev/peps/pep-0498/), Python introduced +*[f-string](https://docs.python.org/3/reference/lexical_analysis.html#formatted-string-literals)* +literals in version __3.6__. Though released ever since +[December 23, 2016](https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-0-final), Python +3.6 is still not widely used as expected. For those who are now used to *f-string*s, `f2format` +provides an intelligent, yet imperfect, solution of a **backport compiler** by converting +*f-string*s to `str.format` expressions, which guarantees you to always write *f-string*s in Python +3.6 flavour then compile for compatibility later. + +  `f2format` is inspired and assisted by my good mate [@gousaiyang](https://github.com/gousaiyang). +It functions by tokenising and parsing Python code into multiple abstract syntax trees (AST), +through which it shall synthesise and extract expressions from *f-string* literals, and then +reassemble the original string using `str.format` method. Besides +**[conversion](https://docs.python.org/3/library/string.html#format-string-syntax)** and +**[format specification](https://docs.python.org/3/library/string.html#formatspec)**, `f2format` +also considered and resolved +**[string concatenation](https://docs.python.org/3/reference/lexical_analysis.html#string-literal-concatenation)**. +Also, it always tries to maintain the original layout of source code, and accuracy of syntax. + +## Installation + +> Note that `f2format` only supports Python versions __since 3.3__ 🐍 + +  For macOS users, `f2format` is now available through [Homebrew](https://brew.sh): + +```sh +brew tap jarryshaw/tap +brew install f2format +# or simply, a one-liner +brew install jarryshaw/tap/f2format +``` + +  Simply run the following to install the current version from PyPI: + +```sh +pip install f2format +``` + +  Or install the latest version from the git repository: + +```sh +git clone https://github.com/JarryShaw/f2format.git +cd f2format +pip install -e . +# and to update at any time +git pull +``` + +## Basic Usage + +### CLI + +  It is fairly straightforward to use `f2format`: + +> context in `${...}` changes dynamically according to runtime environment + +```man +usage: f2format [options] <python source files and folders...> + +Convert f-string to str.format for Python 3 compatibility. + +positional arguments: + SOURCE python source files and folders to be converted (${CWD}) + +optional arguments: + -h, --help show this help message and exit + -V, --version show program's version number and exit + -q, --quiet run in quiet mode + +archive options: + duplicate original files in case there's any issue + + -na, --no-archive do not archive original files + -p PATH, --archive-path PATH + path to archive original files (${CWD}/archive) + +convert options: + compatibility configuration for non-unicode files + + -c CODING, --encoding CODING + encoding to open source files (${LOCALE_ENCODING}) + -v VERSION, --python VERSION + convert against Python version (${LATEST_VERSION}) +``` + +  `f2format` will read then convert all *f-string* literals in every Python file under this +path. In case there might be some problems with the conversion, `f2format` will duplicate all +original files it is to modify into `archive` directory ahead of the process, if `-n` not set. + +  For instance, the code will be converted as follows. + +```python +# the original code +var = f'foo{(1+2)*3:>5}bar{"a", "b"!r}boo' +# after `f2format` +var = 'foo{:>5}bar{!r}boo'.format((1+2)*3, ("a", "b")) +``` + +### Docker + +> Well... it's not published to the Docker Hub yet ;) + +  Considering `f2format` may be used in scenarios where Python is not reachable. +We provide also a Docker image for those poor little guys. + +  See +[`Dockerfile`](https://github.com/JarryShaw/f2format/blob/master/docker/Dockerfile) for more +information. + +### Bundled Executable + +> Coming soooooooooooon... + +  For the worst case, we also provide bundled executables of `f2format`. In such case, +you may simply download it then, voilà, it's ready for you. + +  Special thanks to [PyInstaller](https://www.pyinstaller.org) ❤️ + +## Developer Reference + +### Automator + +  [`make-demo.sh`](https://github.com/JarryShaw/f2format/blob/master/share/make-demo.sh) provides a +demo script, which may help integrate `f2format` in your development and distribution circle. + +> __NB__: `make-demo.sh` is not an integrated automation script. It should be revised by design. + +  It assumes + +- all source files in `/src` directory +- using GitHub for repository management +- having **release** branch under `/release` directory +- already installed `f2format` and [`twine`](https://github.com/pypa/twine#twine) +- permission to these files and folders granted + +  And it will + +- copy `setup.py` and `src` to `release` directory +- run `f2format` for Python files under `release` +- distribute to [PyPI](https://pypi.org) and [TestPyPI](https://test.pypi.org) using `twine` +- upload to release branch on GitHub +- upload original files to GitHub + +### Environments + +`f2format` currently supports three environment arguments: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) + +### APIs + +#### `f2format` -- wrapper works for conversion + +```python +f2format(filename) +``` + +Args: + +- `filename` -- `str`, file to be converted + +Envs: + +- `F2FORMAT_QUIET` -- run in quiet mode (same as `--quiet` option in CLI) +- `F2FORMAT_ENCODING` -- encoding to open source files (same as `--encoding` option in CLI) +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### `convert` -- the main conversion process + +```python +convert(string, source='<unknown>') +``` + +Args: + +- `string` -- `str`, context to be converted +- `source` -- `str`, source of the context + +Envs: + +- `F2FORMAT_VERSION` -- convert against Python version (same as `--python` option in CLI) + +Returns: + +- `str` -- converted string + +Raises: + +- `ConvertError` -- when source code contains syntax errors + +#### Internal exceptions + +```python +class ConvertError(SyntaxError): + """Parso syntax error.""" +``` + +### Codec + +> NB: this project is now stalled, because I just cannot figure out how to play w/ codecs :) + +  [`f2format-codec`](https://github.com/JarryShaw/f2format-codec) registers a codec in Python +interpreter, which grants you the compatibility to write directly in Python 3.6 *f-string* syntax +even through running with a previous version of Python. + +## Test + +  The current test samples are under [`/test`](https://github.com/JarryShaw/f2format/blob/master/test) +folder. `test_driver.py` is the main entry point for tests. + +  For unittests, see [`test.py`](https://github.com/JarryShaw/f2format/blob/master/share/test.py). + +## Known issues + +  Since `f2format` is currently based on [`parso`](https://github.com/davidhalter/parso) project, +it had encountered several compatibility and parsing issues. + +* ~~Parsing f-strings with nested format specifiers produces incorrect SyntaxError ([#74](https://github.com/davidhalter/parso/issues/74))~~ + This issue has been resolved since `parso` version __0.5.0__. + +* Parsing f-strings with invalid quotes in expression part does not raise SyntaxError ([#86](https://github.com/davidhalter/parso/issues/86)) + +* Parsing f-strings with seeming assignment expressions produces incorrect SyntaxError ([#87](https://github.com/davidhalter/parso/issues/87)) + +## Contribution + +  Contributions are very welcome, especially fixing bugs and providing test cases, which +[@gousaiyang](https://github.com/gousaiyang) is to help with, so to speak. Note that code must +remain valid and reasonable. + +## See Also + +- [`babel`](https://github.com/jarryshaw/babel) +- [`poseur`](https://github.com/jarryshaw/poseur) +- [`walrus`](https://github.com/jarryshaw/walrus) +- [`vermin`](https://github.com/netromdk/vermin) + + + + +%prep +%autosetup -n f2format-0.8.6 + +%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-f2format -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.8.6-1 +- Package Spec generated |