diff options
Diffstat (limited to 'python-player.spec')
| -rw-r--r-- | python-player.spec | 168 |
1 files changed, 168 insertions, 0 deletions
diff --git a/python-player.spec b/python-player.spec new file mode 100644 index 0000000..03652a0 --- /dev/null +++ b/python-player.spec @@ -0,0 +1,168 @@ +%global _empty_manifest_terminate_build 0 +Name: python-player +Version: 0.6.1 +Release: 1 +Summary: Pyramid view layers +License: BSD +URL: https://github.com/fafhrd91/player/ +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/66/a9/699a6820e8169d28d1372f28c77e4d3f0086dddc670645edb1ec4671a051/player-0.6.1.tar.gz +BuildArch: noarch + + +%description +player allows to address templates with two parameters, +category and name. Also it is possible to use set of directories +for each layer, in that case `player` searches templates +in each directory. It allows to override templates without changing +code. For example form library can define layer `field`:: + >> ls ./fields/ +In your application you can override any of this template by defining +new layer for `field` category:: + >> ls ./myproject/fields/ +Usually top level directory is a category and file in directory is template. +For example 'form:view.lt':: + `form` - layer category + `view` - template name + `.lt` - custom pyramid renderer factory +Layer can to be defined with `add_layer` config directive: + >> config = Configurator() +`form` directory can contain any template: + >> ./form/ +It is possible to use any of this templates as pyramid renderer path: + >> config.add_view( +or : + >> config.add_view( +It is possible to run python code before rendering template. +There are `add_tmpl_filter` directive and `player.tmpl_filter` +decorator: + >> def form_actions(context, request): + >> config.add_tmpl_filter('form:actions', form_action, name='custom') +or: + >> import player + >> @player.tmpl_filter('form:actions', name='custom') +`form_actions` function gets call just before rendering template. +Layer has to be defined with `add_layer` directve before registering +template filter function. + +%package -n python3-player +Summary: Pyramid view layers +Provides: python-player +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-player +player allows to address templates with two parameters, +category and name. Also it is possible to use set of directories +for each layer, in that case `player` searches templates +in each directory. It allows to override templates without changing +code. For example form library can define layer `field`:: + >> ls ./fields/ +In your application you can override any of this template by defining +new layer for `field` category:: + >> ls ./myproject/fields/ +Usually top level directory is a category and file in directory is template. +For example 'form:view.lt':: + `form` - layer category + `view` - template name + `.lt` - custom pyramid renderer factory +Layer can to be defined with `add_layer` config directive: + >> config = Configurator() +`form` directory can contain any template: + >> ./form/ +It is possible to use any of this templates as pyramid renderer path: + >> config.add_view( +or : + >> config.add_view( +It is possible to run python code before rendering template. +There are `add_tmpl_filter` directive and `player.tmpl_filter` +decorator: + >> def form_actions(context, request): + >> config.add_tmpl_filter('form:actions', form_action, name='custom') +or: + >> import player + >> @player.tmpl_filter('form:actions', name='custom') +`form_actions` function gets call just before rendering template. +Layer has to be defined with `add_layer` directve before registering +template filter function. + +%package help +Summary: Development documents and examples for player +Provides: python3-player-doc +%description help +player allows to address templates with two parameters, +category and name. Also it is possible to use set of directories +for each layer, in that case `player` searches templates +in each directory. It allows to override templates without changing +code. For example form library can define layer `field`:: + >> ls ./fields/ +In your application you can override any of this template by defining +new layer for `field` category:: + >> ls ./myproject/fields/ +Usually top level directory is a category and file in directory is template. +For example 'form:view.lt':: + `form` - layer category + `view` - template name + `.lt` - custom pyramid renderer factory +Layer can to be defined with `add_layer` config directive: + >> config = Configurator() +`form` directory can contain any template: + >> ./form/ +It is possible to use any of this templates as pyramid renderer path: + >> config.add_view( +or : + >> config.add_view( +It is possible to run python code before rendering template. +There are `add_tmpl_filter` directive and `player.tmpl_filter` +decorator: + >> def form_actions(context, request): + >> config.add_tmpl_filter('form:actions', form_action, name='custom') +or: + >> import player + >> @player.tmpl_filter('form:actions', name='custom') +`form_actions` function gets call just before rendering template. +Layer has to be defined with `add_layer` directve before registering +template filter function. + +%prep +%autosetup -n player-0.6.1 + +%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-player -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Thu Mar 09 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6.1-1 +- Package Spec generated |