automatic import of python-observ

3 files changed, 222 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..6eff455 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/observ-0.10.0.tar.gz
diff --git a/python-observ.spec b/python-observ.spec
new file mode 100644
index 0000000..222e861
--- /dev/null
+++ b/python-observ.spec
@@ -0,0 +1,220 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-observ
+Version:	0.10.0
+Release:	1
+Summary:	Reactive state management for Python
+License:	MIT
+URL:		https://github.com/fork-tongue/observ
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/5e/ff/0e5f8c85c96f9000a998b6bb4d04cfc01e5607104b299706fc461279142e/observ-0.10.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-patchdiff
+
+%description
+[![PyPI version](https://badge.fury.io/py/observ.svg)](https://badge.fury.io/py/observ)
+[![CI status](https://github.com/fork-tongue/observ/workflows/CI/badge.svg)](https://github.com/fork-tongue/observ/actions)
+
+# Observ 👁
+
+Observ is a Python port of [Vue.js](https://vuejs.org/)' [computed properties and watchers](https://v3.vuejs.org/api/basic-reactivity.html). It is event loop/framework agnostic and has only one pure-python dependency ([patchdiff](https://github.com/Korijn/patchdiff)) so it can be used in any project targeting Python >= 3.7.
+
+Observ provides the following two benefits for stateful applications:
+
+1) You no longer need to manually invalidate and recompute state (e.g. by dirty flags):
+    * computed state is invalidated automatically
+    * computed state is lazily re-evaluated
+2) You can react to changes in state (computed or not), enabling unidirectional flow:
+    * _state changes_ lead to _view changes_ (e.g. a state change callback updates a UI widget)
+    * the _view_ triggers _input events_ (e.g. a mouse event is triggered in the UI)
+    * _input events_ lead to _state changes_ (e.g. a mouse event updates the state)
+
+## API
+
+`from observ import reactive, computed, watch`
+
+* `state = reactive(state)`
+
+Observe nested structures of dicts, lists, tuples and sets. Returns an observable proxy that wraps the state input object.
+
+* `watcher = watch(func, callback, deep=False, immediate=False)`
+
+React to changes in the state accessed in `func` with `callback(old_value, new_value)`. Returns a watcher object. `del`elete it to disable the callback.
+
+* `wrapped_func = computed(func)`
+
+Define computed state based on observable state with `func` and recompute lazily. Returns a wrapped copy of the function which only recomputes the output if any of the state it depends on becomes dirty. Can be used as a function decorator.
+
+**Note:** The API has evolved and become more powerful since the original creation of this README. Track issue #10 to follow updates to observ's documentation.
+
+## Quick start and examples
+
+Install observ with pip/pipenv/poetry:
+
+`pip install observ`
+
+Check out [`examples/observe_qt.py`](https://github.com/Korijn/observ/blob/master/examples/observe_qt.py) for a simple example using observ.
+
+Check out [`examples/store_with_undo_redo.py`](https://github.com/Korijn/observ/blob/master/examples/store_with_undo_redo.py) for a simple example using the included undo/redo-capable Store abstraction.
+
+## Caveat
+
+Observ keeps references to the object passed to the `reactive` in order to keep track of dependencies and proxies for that object. When the object that is passed into `reactive` is not managed by other code, then observ should cleanup its references automatically when the proxy is destroyed. However, if there is another reference to the original object, then observ will only release its own reference when the garbage collector is run and all other references to the object are gone. For this reason, the **best practise** is to keep **no references** to the raw data, and instead work with the reactive proxies **only**.
+
+
+
+%package -n python3-observ
+Summary:	Reactive state management for Python
+Provides:	python-observ
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-observ
+[![PyPI version](https://badge.fury.io/py/observ.svg)](https://badge.fury.io/py/observ)
+[![CI status](https://github.com/fork-tongue/observ/workflows/CI/badge.svg)](https://github.com/fork-tongue/observ/actions)
+
+# Observ 👁
+
+Observ is a Python port of [Vue.js](https://vuejs.org/)' [computed properties and watchers](https://v3.vuejs.org/api/basic-reactivity.html). It is event loop/framework agnostic and has only one pure-python dependency ([patchdiff](https://github.com/Korijn/patchdiff)) so it can be used in any project targeting Python >= 3.7.
+
+Observ provides the following two benefits for stateful applications:
+
+1) You no longer need to manually invalidate and recompute state (e.g. by dirty flags):
+    * computed state is invalidated automatically
+    * computed state is lazily re-evaluated
+2) You can react to changes in state (computed or not), enabling unidirectional flow:
+    * _state changes_ lead to _view changes_ (e.g. a state change callback updates a UI widget)
+    * the _view_ triggers _input events_ (e.g. a mouse event is triggered in the UI)
+    * _input events_ lead to _state changes_ (e.g. a mouse event updates the state)
+
+## API
+
+`from observ import reactive, computed, watch`
+
+* `state = reactive(state)`
+
+Observe nested structures of dicts, lists, tuples and sets. Returns an observable proxy that wraps the state input object.
+
+* `watcher = watch(func, callback, deep=False, immediate=False)`
+
+React to changes in the state accessed in `func` with `callback(old_value, new_value)`. Returns a watcher object. `del`elete it to disable the callback.
+
+* `wrapped_func = computed(func)`
+
+Define computed state based on observable state with `func` and recompute lazily. Returns a wrapped copy of the function which only recomputes the output if any of the state it depends on becomes dirty. Can be used as a function decorator.
+
+**Note:** The API has evolved and become more powerful since the original creation of this README. Track issue #10 to follow updates to observ's documentation.
+
+## Quick start and examples
+
+Install observ with pip/pipenv/poetry:
+
+`pip install observ`
+
+Check out [`examples/observe_qt.py`](https://github.com/Korijn/observ/blob/master/examples/observe_qt.py) for a simple example using observ.
+
+Check out [`examples/store_with_undo_redo.py`](https://github.com/Korijn/observ/blob/master/examples/store_with_undo_redo.py) for a simple example using the included undo/redo-capable Store abstraction.
+
+## Caveat
+
+Observ keeps references to the object passed to the `reactive` in order to keep track of dependencies and proxies for that object. When the object that is passed into `reactive` is not managed by other code, then observ should cleanup its references automatically when the proxy is destroyed. However, if there is another reference to the original object, then observ will only release its own reference when the garbage collector is run and all other references to the object are gone. For this reason, the **best practise** is to keep **no references** to the raw data, and instead work with the reactive proxies **only**.
+
+
+
+%package help
+Summary:	Development documents and examples for observ
+Provides:	python3-observ-doc
+%description help
+[![PyPI version](https://badge.fury.io/py/observ.svg)](https://badge.fury.io/py/observ)
+[![CI status](https://github.com/fork-tongue/observ/workflows/CI/badge.svg)](https://github.com/fork-tongue/observ/actions)
+
+# Observ 👁
+
+Observ is a Python port of [Vue.js](https://vuejs.org/)' [computed properties and watchers](https://v3.vuejs.org/api/basic-reactivity.html). It is event loop/framework agnostic and has only one pure-python dependency ([patchdiff](https://github.com/Korijn/patchdiff)) so it can be used in any project targeting Python >= 3.7.
+
+Observ provides the following two benefits for stateful applications:
+
+1) You no longer need to manually invalidate and recompute state (e.g. by dirty flags):
+    * computed state is invalidated automatically
+    * computed state is lazily re-evaluated
+2) You can react to changes in state (computed or not), enabling unidirectional flow:
+    * _state changes_ lead to _view changes_ (e.g. a state change callback updates a UI widget)
+    * the _view_ triggers _input events_ (e.g. a mouse event is triggered in the UI)
+    * _input events_ lead to _state changes_ (e.g. a mouse event updates the state)
+
+## API
+
+`from observ import reactive, computed, watch`
+
+* `state = reactive(state)`
+
+Observe nested structures of dicts, lists, tuples and sets. Returns an observable proxy that wraps the state input object.
+
+* `watcher = watch(func, callback, deep=False, immediate=False)`
+
+React to changes in the state accessed in `func` with `callback(old_value, new_value)`. Returns a watcher object. `del`elete it to disable the callback.
+
+* `wrapped_func = computed(func)`
+
+Define computed state based on observable state with `func` and recompute lazily. Returns a wrapped copy of the function which only recomputes the output if any of the state it depends on becomes dirty. Can be used as a function decorator.
+
+**Note:** The API has evolved and become more powerful since the original creation of this README. Track issue #10 to follow updates to observ's documentation.
+
+## Quick start and examples
+
+Install observ with pip/pipenv/poetry:
+
+`pip install observ`
+
+Check out [`examples/observe_qt.py`](https://github.com/Korijn/observ/blob/master/examples/observe_qt.py) for a simple example using observ.
+
+Check out [`examples/store_with_undo_redo.py`](https://github.com/Korijn/observ/blob/master/examples/store_with_undo_redo.py) for a simple example using the included undo/redo-capable Store abstraction.
+
+## Caveat
+
+Observ keeps references to the object passed to the `reactive` in order to keep track of dependencies and proxies for that object. When the object that is passed into `reactive` is not managed by other code, then observ should cleanup its references automatically when the proxy is destroyed. However, if there is another reference to the original object, then observ will only release its own reference when the garbage collector is run and all other references to the object are gone. For this reason, the **best practise** is to keep **no references** to the raw data, and instead work with the reactive proxies **only**.
+
+
+
+%prep
+%autosetup -n observ-0.10.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-observ -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed May 17 2023 Python_Bot <Python_Bot@openeuler.org> - 0.10.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..0e30461
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+182b149268e89054ad88c8a0c3e82225  observ-0.10.0.tar.gz