diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-linesman.spec | 108 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 110 insertions, 0 deletions
@@ -0,0 +1 @@ +/linesman-0.3.2.tar.gz diff --git a/python-linesman.spec b/python-linesman.spec new file mode 100644 index 0000000..3cfbd1a --- /dev/null +++ b/python-linesman.spec @@ -0,0 +1,108 @@ +%global _empty_manifest_terminate_build 0 +Name: python-linesman +Version: 0.3.2 +Release: 1 +Summary: WSGI Profiling middleware +License: UNKNOWN +URL: http://pypi.python.org/pypi/linesman +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/00/db/bbe43c0d4622187a4bae2ba8fd176f18a904a0c36c7a2283280fff2a1c9a/linesman-0.3.2.tar.gz +BuildArch: noarch + + +%description +One of my team's stories at work was to investigate existing Python profiling +tools for use with some of our new web stacks (all in Pylons). I looked at a +few--``repoze.profile``, ``kea.profile``, and even ``dozer`` (still in +0.2alpha)--but couldn't find any that suited our use case. We wanted to... +- visualize the flow of our code +- identify bottlenecks quickly and easily +- have the ability to strip out extraneous calls +Many of the tools simply outputted the ``pstats`` object from ``cProfile``, +which can be difficult to parse, and even more difficult to identify the call +order. Considering that ``cProfile`` provided all the information needed, I +figured it would be just as easy to write our own middleware. +``linesman`` is a name given to people who inspect electrical ``Pylons``, and +was a meek attempt at having a relevant library name. + +%package -n python3-linesman +Summary: WSGI Profiling middleware +Provides: python-linesman +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-linesman +One of my team's stories at work was to investigate existing Python profiling +tools for use with some of our new web stacks (all in Pylons). I looked at a +few--``repoze.profile``, ``kea.profile``, and even ``dozer`` (still in +0.2alpha)--but couldn't find any that suited our use case. We wanted to... +- visualize the flow of our code +- identify bottlenecks quickly and easily +- have the ability to strip out extraneous calls +Many of the tools simply outputted the ``pstats`` object from ``cProfile``, +which can be difficult to parse, and even more difficult to identify the call +order. Considering that ``cProfile`` provided all the information needed, I +figured it would be just as easy to write our own middleware. +``linesman`` is a name given to people who inspect electrical ``Pylons``, and +was a meek attempt at having a relevant library name. + +%package help +Summary: Development documents and examples for linesman +Provides: python3-linesman-doc +%description help +One of my team's stories at work was to investigate existing Python profiling +tools for use with some of our new web stacks (all in Pylons). I looked at a +few--``repoze.profile``, ``kea.profile``, and even ``dozer`` (still in +0.2alpha)--but couldn't find any that suited our use case. We wanted to... +- visualize the flow of our code +- identify bottlenecks quickly and easily +- have the ability to strip out extraneous calls +Many of the tools simply outputted the ``pstats`` object from ``cProfile``, +which can be difficult to parse, and even more difficult to identify the call +order. Considering that ``cProfile`` provided all the information needed, I +figured it would be just as easy to write our own middleware. +``linesman`` is a name given to people who inspect electrical ``Pylons``, and +was a meek attempt at having a relevant library name. + +%prep +%autosetup -n linesman-0.3.2 + +%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-linesman -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 17 2023 Python_Bot <Python_Bot@openeuler.org> - 0.3.2-1 +- Package Spec generated @@ -0,0 +1 @@ +8fadb0af5426d3d2b1aa36a3b75419ec linesman-0.3.2.tar.gz |