automatic import of python-pyre-check-nightly

1 files changed, 276 insertions, 0 deletions

diff --git a/python-pyre-check-nightly.spec b/python-pyre-check-nightly.spec
new file mode 100644
index 0000000..ae014c1
--- /dev/null
+++ b/python-pyre-check-nightly.spec
@@ -0,0 +1,276 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pyre-check-nightly
+Version:	0.0.101681125095
+Release:	1
+Summary:	A performant type checker for Python
+License:	MIT
+URL:		https://pyre-check.org/
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/35/19/c0ee7c2f6fb488d8ca949bae2b94328183586f106fbb48a329dcdb3ef52b/pyre-check-nightly-0.0.101681125095.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-click
+Requires:	python3-dataclasses-json
+Requires:	python3-intervaltree
+Requires:	python3-libcst
+Requires:	python3-psutil
+Requires:	python3-pyre-extensions
+Requires:	python3-tabulate
+Requires:	python3-testslide
+Requires:	python3-typing-extensions
+
+%description
+[![lint](https://github.com/facebook/pyre-check/workflows/lint/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/lint.yml)
+[![tests](https://github.com/facebook/pyre-check/workflows/tests/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/tests.yml)
+[![pyre](https://github.com/facebook/pyre-check/workflows/pyre/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/pyre.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Gitter](https://badges.gitter.im/pyre-check/community.svg)](https://gitter.im/pyre-check/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/facebook/pyre-check/main/logo.png">
+</p>
+
+Pyre is a performant type checker for Python compliant with [PEP 484](https://www.python.org/dev/peps/pep-0484/). Pyre can analyze codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code. You can try it out on examples in [the Pyre Playground](https://pyre-check.org/play).
+
+Pyre ships with **Pysa**, a security focused static analysis tool we've built on top of Pyre that reasons about data flows in Python applications. Please refer to our [documentation](https://pyre-check.org/docs/pysa-quickstart) to get started with our security analysis.
+
+Pysa is also available on the [GitHub Marketplace as a Github Action](https://github.com/marketplace/actions/pysa-action)
+
+## Requirements
+To get started, you need [Python 3.6 or later](https://www.python.org/getit/) and [watchman](https://facebook.github.io/watchman/) working on your system. On *MacOS* you can get everything with [homebrew](https://brew.sh/):
+```bash
+$ brew install python3 watchman
+```
+On *Ubuntu*, *Mint*, or *Debian*; use `apt-get` and [homebrew](https://brew.sh/):
+```bash
+$ sudo apt-get install python3 python3-pip python3-venv
+$ brew install watchman
+```
+We tested Pyre on *Ubuntu 18.04.5 LTS*, *CentOS 7*, as well as *OSX 10.11* and later.
+
+## Setting up a Project
+We start by creating an empty project directory and setting up a virtual environment:
+
+```bash
+$ mkdir my_project && cd my_project
+$ python3 -m venv ~/.venvs/venv
+$ source ~/.venvs/venv/bin/activate
+(venv) $ pip install pyre-check
+```
+
+Next, we teach Pyre about our new project:
+```bash
+(venv) $ pyre init
+```
+This command will set up a configuration for Pyre (`.pyre_configuration`) as well as watchman (`.watchmanconfig`) in your project's directory. Accept the defaults for now – you can change them later if necessary.
+
+## Running Pyre
+We are now ready to run Pyre:
+```bash
+(venv) $ echo "i: int = 'string'" > test.py
+(venv) $ pyre
+ ƛ Found 1 type error!
+test.py:1:0 Incompatible variable type [9]: i is declared to have type `int` but is used as type `str`.
+```
+This first invocation will start a daemon listening for filesystem changes – type checking your project incrementally as you make edits to the code. You will notice that subsequent invocations of `pyre` will be faster than the first one.
+
+For more detailed documentation, see https://pyre-check.org.
+
+## Join the Pyre community
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for how to help out.
+
+## License
+
+Pyre is licensed under the MIT license.
+
+
+
+
+%package -n python3-pyre-check-nightly
+Summary:	A performant type checker for Python
+Provides:	python-pyre-check-nightly
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pyre-check-nightly
+[![lint](https://github.com/facebook/pyre-check/workflows/lint/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/lint.yml)
+[![tests](https://github.com/facebook/pyre-check/workflows/tests/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/tests.yml)
+[![pyre](https://github.com/facebook/pyre-check/workflows/pyre/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/pyre.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Gitter](https://badges.gitter.im/pyre-check/community.svg)](https://gitter.im/pyre-check/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/facebook/pyre-check/main/logo.png">
+</p>
+
+Pyre is a performant type checker for Python compliant with [PEP 484](https://www.python.org/dev/peps/pep-0484/). Pyre can analyze codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code. You can try it out on examples in [the Pyre Playground](https://pyre-check.org/play).
+
+Pyre ships with **Pysa**, a security focused static analysis tool we've built on top of Pyre that reasons about data flows in Python applications. Please refer to our [documentation](https://pyre-check.org/docs/pysa-quickstart) to get started with our security analysis.
+
+Pysa is also available on the [GitHub Marketplace as a Github Action](https://github.com/marketplace/actions/pysa-action)
+
+## Requirements
+To get started, you need [Python 3.6 or later](https://www.python.org/getit/) and [watchman](https://facebook.github.io/watchman/) working on your system. On *MacOS* you can get everything with [homebrew](https://brew.sh/):
+```bash
+$ brew install python3 watchman
+```
+On *Ubuntu*, *Mint*, or *Debian*; use `apt-get` and [homebrew](https://brew.sh/):
+```bash
+$ sudo apt-get install python3 python3-pip python3-venv
+$ brew install watchman
+```
+We tested Pyre on *Ubuntu 18.04.5 LTS*, *CentOS 7*, as well as *OSX 10.11* and later.
+
+## Setting up a Project
+We start by creating an empty project directory and setting up a virtual environment:
+
+```bash
+$ mkdir my_project && cd my_project
+$ python3 -m venv ~/.venvs/venv
+$ source ~/.venvs/venv/bin/activate
+(venv) $ pip install pyre-check
+```
+
+Next, we teach Pyre about our new project:
+```bash
+(venv) $ pyre init
+```
+This command will set up a configuration for Pyre (`.pyre_configuration`) as well as watchman (`.watchmanconfig`) in your project's directory. Accept the defaults for now – you can change them later if necessary.
+
+## Running Pyre
+We are now ready to run Pyre:
+```bash
+(venv) $ echo "i: int = 'string'" > test.py
+(venv) $ pyre
+ ƛ Found 1 type error!
+test.py:1:0 Incompatible variable type [9]: i is declared to have type `int` but is used as type `str`.
+```
+This first invocation will start a daemon listening for filesystem changes – type checking your project incrementally as you make edits to the code. You will notice that subsequent invocations of `pyre` will be faster than the first one.
+
+For more detailed documentation, see https://pyre-check.org.
+
+## Join the Pyre community
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for how to help out.
+
+## License
+
+Pyre is licensed under the MIT license.
+
+
+
+
+%package help
+Summary:	Development documents and examples for pyre-check-nightly
+Provides:	python3-pyre-check-nightly-doc
+%description help
+[![lint](https://github.com/facebook/pyre-check/workflows/lint/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/lint.yml)
+[![tests](https://github.com/facebook/pyre-check/workflows/tests/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/tests.yml)
+[![pyre](https://github.com/facebook/pyre-check/workflows/pyre/badge.svg)](https://github.com/facebook/pyre-check/actions/workflows/pyre.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Gitter](https://badges.gitter.im/pyre-check/community.svg)](https://gitter.im/pyre-check/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/facebook/pyre-check/main/logo.png">
+</p>
+
+Pyre is a performant type checker for Python compliant with [PEP 484](https://www.python.org/dev/peps/pep-0484/). Pyre can analyze codebases with millions of lines of code incrementally – providing instantaneous feedback to developers as they write code. You can try it out on examples in [the Pyre Playground](https://pyre-check.org/play).
+
+Pyre ships with **Pysa**, a security focused static analysis tool we've built on top of Pyre that reasons about data flows in Python applications. Please refer to our [documentation](https://pyre-check.org/docs/pysa-quickstart) to get started with our security analysis.
+
+Pysa is also available on the [GitHub Marketplace as a Github Action](https://github.com/marketplace/actions/pysa-action)
+
+## Requirements
+To get started, you need [Python 3.6 or later](https://www.python.org/getit/) and [watchman](https://facebook.github.io/watchman/) working on your system. On *MacOS* you can get everything with [homebrew](https://brew.sh/):
+```bash
+$ brew install python3 watchman
+```
+On *Ubuntu*, *Mint*, or *Debian*; use `apt-get` and [homebrew](https://brew.sh/):
+```bash
+$ sudo apt-get install python3 python3-pip python3-venv
+$ brew install watchman
+```
+We tested Pyre on *Ubuntu 18.04.5 LTS*, *CentOS 7*, as well as *OSX 10.11* and later.
+
+## Setting up a Project
+We start by creating an empty project directory and setting up a virtual environment:
+
+```bash
+$ mkdir my_project && cd my_project
+$ python3 -m venv ~/.venvs/venv
+$ source ~/.venvs/venv/bin/activate
+(venv) $ pip install pyre-check
+```
+
+Next, we teach Pyre about our new project:
+```bash
+(venv) $ pyre init
+```
+This command will set up a configuration for Pyre (`.pyre_configuration`) as well as watchman (`.watchmanconfig`) in your project's directory. Accept the defaults for now – you can change them later if necessary.
+
+## Running Pyre
+We are now ready to run Pyre:
+```bash
+(venv) $ echo "i: int = 'string'" > test.py
+(venv) $ pyre
+ ƛ Found 1 type error!
+test.py:1:0 Incompatible variable type [9]: i is declared to have type `int` but is used as type `str`.
+```
+This first invocation will start a daemon listening for filesystem changes – type checking your project incrementally as you make edits to the code. You will notice that subsequent invocations of `pyre` will be faster than the first one.
+
+For more detailed documentation, see https://pyre-check.org.
+
+## Join the Pyre community
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for how to help out.
+
+## License
+
+Pyre is licensed under the MIT license.
+
+
+
+
+%prep
+%autosetup -n pyre-check-nightly-0.0.101681125095
+
+%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-pyre-check-nightly -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.101681125095-1
+- Package Spec generated