1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
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.aliyun.com/pypi/web/packages/5e/ff/0e5f8c85c96f9000a998b6bb4d04cfc01e5607104b299706fc461279142e/observ-0.10.0.tar.gz
BuildArch: noarch
Requires: python3-patchdiff
%description
[](https://badge.fury.io/py/observ)
[](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
[](https://badge.fury.io/py/observ)
[](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
[](https://badge.fury.io/py/observ)
[](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
* Thu Jun 08 2023 Python_Bot <Python_Bot@openeuler.org> - 0.10.0-1
- Package Spec generated
|
