summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-05-05 10:20:43 +0000
committerCoprDistGit <infra@openeuler.org>2023-05-05 10:20:43 +0000
commit2e052333f330a6212345e1ec6e24f3feb61ec649 (patch)
tree5c272752e845b23face452bf571ed4f1b8d5b820
parent07c4e9944313576155bdec8ddbf0eadef8e87ba1 (diff)
automatic import of python-grokcore-messageopeneuler20.03
-rw-r--r--.gitignore1
-rw-r--r--python-grokcore-message.spec177
-rw-r--r--sources1
3 files changed, 179 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..9471131 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/grokcore.message-3.0.1.tar.gz
diff --git a/python-grokcore-message.spec b/python-grokcore-message.spec
new file mode 100644
index 0000000..fd26235
--- /dev/null
+++ b/python-grokcore-message.spec
@@ -0,0 +1,177 @@
+%global _empty_manifest_terminate_build 0
+Name: python-grokcore.message
+Version: 3.0.1
+Release: 1
+Summary: Grok messaging machinery
+License: ZPL 2.1
+URL: http://pypi.python.org/pypi/grokcore.message
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/68/2f/4a9713b57f3e12bbb9c8a728167994672ee389ac72624c280f11b59ad7fa/grokcore.message-3.0.1.tar.gz
+BuildArch: noarch
+
+
+%description
+When being grokked, ``grokcore.message`` registers
+* a global session message source named ``session``
+* a global message receiver.
+Grokking of this package happens when the local ``configure.zcml`` is
+executed. In standard Grok-based packages this often happens
+automatically.
+One can, of course, also grok the package manually:
+ >>> import grokcore.component as grok
+ >>> grok.testing.grok('grokcore.message')
+This setups a global message receiver:
+ >>> from z3c.flashmessage.interfaces import IMessageReceiver
+ >>> from zope.component import getUtility
+ >>> getUtility(IMessageReceiver)
+ <z3c.flashmessage.receiver.GlobalMessageReceiver object at 0x...>
+It also setups a session-based message source named ``session``:
+ >>> from z3c.flashmessage.interfaces import IMessageSource
+ >>> getUtility(IMessageSource, name=u'session')
+ <z3c.flashmessage.sources.SessionMessageSource object at 0x...>
+We provide also a RAM-stored message source that can be enabled by
+including ``ram.zcml`` and is not registered by default:
+ >>> getUtility(IMessageSource, name=u'ram')
+ Traceback (most recent call last):
+ zope.interface.interfaces.ComponentLookupError: (<InterfaceClass z3c.flashmessage.interfaces.IMessageSource>, 'ram')
+You can enable this source by including ``ram.zcml`` from
+``grokcore.message`` in your ZCML setup like this::
+ <configure xmlns="http://namespaces.zope.org/zope">
+ <include package="grokcore.message" file="ram.zcml" />
+ </configure>
+or, of course, by registering a RAMMessageSource manually:
+ >>> from zope.component import provideUtility
+ >>> from z3c.flashmessage.sources import RAMMessageSource
+ >>> ram_source = RAMMessageSource()
+ >>> provideUtility(ram_source, name=u'ram')
+Now we can get the RAM source:
+ >>> getUtility(IMessageSource, name=u'ram')
+ <z3c.flashmessage.sources.RAMMessageSource object at 0x...>
+
+%package -n python3-grokcore.message
+Summary: Grok messaging machinery
+Provides: python-grokcore.message
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-grokcore.message
+When being grokked, ``grokcore.message`` registers
+* a global session message source named ``session``
+* a global message receiver.
+Grokking of this package happens when the local ``configure.zcml`` is
+executed. In standard Grok-based packages this often happens
+automatically.
+One can, of course, also grok the package manually:
+ >>> import grokcore.component as grok
+ >>> grok.testing.grok('grokcore.message')
+This setups a global message receiver:
+ >>> from z3c.flashmessage.interfaces import IMessageReceiver
+ >>> from zope.component import getUtility
+ >>> getUtility(IMessageReceiver)
+ <z3c.flashmessage.receiver.GlobalMessageReceiver object at 0x...>
+It also setups a session-based message source named ``session``:
+ >>> from z3c.flashmessage.interfaces import IMessageSource
+ >>> getUtility(IMessageSource, name=u'session')
+ <z3c.flashmessage.sources.SessionMessageSource object at 0x...>
+We provide also a RAM-stored message source that can be enabled by
+including ``ram.zcml`` and is not registered by default:
+ >>> getUtility(IMessageSource, name=u'ram')
+ Traceback (most recent call last):
+ zope.interface.interfaces.ComponentLookupError: (<InterfaceClass z3c.flashmessage.interfaces.IMessageSource>, 'ram')
+You can enable this source by including ``ram.zcml`` from
+``grokcore.message`` in your ZCML setup like this::
+ <configure xmlns="http://namespaces.zope.org/zope">
+ <include package="grokcore.message" file="ram.zcml" />
+ </configure>
+or, of course, by registering a RAMMessageSource manually:
+ >>> from zope.component import provideUtility
+ >>> from z3c.flashmessage.sources import RAMMessageSource
+ >>> ram_source = RAMMessageSource()
+ >>> provideUtility(ram_source, name=u'ram')
+Now we can get the RAM source:
+ >>> getUtility(IMessageSource, name=u'ram')
+ <z3c.flashmessage.sources.RAMMessageSource object at 0x...>
+
+%package help
+Summary: Development documents and examples for grokcore.message
+Provides: python3-grokcore.message-doc
+%description help
+When being grokked, ``grokcore.message`` registers
+* a global session message source named ``session``
+* a global message receiver.
+Grokking of this package happens when the local ``configure.zcml`` is
+executed. In standard Grok-based packages this often happens
+automatically.
+One can, of course, also grok the package manually:
+ >>> import grokcore.component as grok
+ >>> grok.testing.grok('grokcore.message')
+This setups a global message receiver:
+ >>> from z3c.flashmessage.interfaces import IMessageReceiver
+ >>> from zope.component import getUtility
+ >>> getUtility(IMessageReceiver)
+ <z3c.flashmessage.receiver.GlobalMessageReceiver object at 0x...>
+It also setups a session-based message source named ``session``:
+ >>> from z3c.flashmessage.interfaces import IMessageSource
+ >>> getUtility(IMessageSource, name=u'session')
+ <z3c.flashmessage.sources.SessionMessageSource object at 0x...>
+We provide also a RAM-stored message source that can be enabled by
+including ``ram.zcml`` and is not registered by default:
+ >>> getUtility(IMessageSource, name=u'ram')
+ Traceback (most recent call last):
+ zope.interface.interfaces.ComponentLookupError: (<InterfaceClass z3c.flashmessage.interfaces.IMessageSource>, 'ram')
+You can enable this source by including ``ram.zcml`` from
+``grokcore.message`` in your ZCML setup like this::
+ <configure xmlns="http://namespaces.zope.org/zope">
+ <include package="grokcore.message" file="ram.zcml" />
+ </configure>
+or, of course, by registering a RAMMessageSource manually:
+ >>> from zope.component import provideUtility
+ >>> from z3c.flashmessage.sources import RAMMessageSource
+ >>> ram_source = RAMMessageSource()
+ >>> provideUtility(ram_source, name=u'ram')
+Now we can get the RAM source:
+ >>> getUtility(IMessageSource, name=u'ram')
+ <z3c.flashmessage.sources.RAMMessageSource object at 0x...>
+
+%prep
+%autosetup -n grokcore.message-3.0.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-grokcore.message -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 3.0.1-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..de557d4
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+5d3ce03f1e31167a61433a7477260d27 grokcore.message-3.0.1.tar.gz