summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-06-20 08:11:13 +0000
committerCoprDistGit <infra@openeuler.org>2023-06-20 08:11:13 +0000
commitfc390d3595ce54bee682a75f25c9b9fdf52a42e1 (patch)
tree430dd724b4b811bdb15ec88764ad0582d262d5f1
parentd4048dc4efb6db5f90f7c880a9cbe1e471c8df6a (diff)
automatic import of python-barium-mealopeneuler20.03
-rw-r--r--.gitignore1
-rw-r--r--python-barium-meal.spec180
-rw-r--r--sources1
3 files changed, 182 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..d27d35c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/barium-meal-0.0.13.macosx-10.15-x86_64.tar.gz
diff --git a/python-barium-meal.spec b/python-barium-meal.spec
new file mode 100644
index 0000000..03ebe05
--- /dev/null
+++ b/python-barium-meal.spec
@@ -0,0 +1,180 @@
+%global _empty_manifest_terminate_build 0
+Name: python-barium-meal
+Version: 0.0.13
+Release: 1
+Summary: Convenience wrapper for OpenTelemetry
+License: MIT
+URL: https://github.com/peckhamdata/barium-meal
+Source0: https://mirrors.aliyun.com/pypi/web/packages/4e/99/e9278b6c0ce1694fa25ebfe640f8af956e50c50b32bc0e04e4d5fcc9984f/barium-meal-0.0.13.macosx-10.15-x86_64.tar.gz
+BuildArch: noarch
+
+
+%description
+# barium-meal
+
+Python Wrapper for [OpenTelemetry](https://opentelemetry.io/) written to scratch the itch
+of needing to use the same / similar code across several [Google Cloud Functions](https://cloud.google.com/functions)
+and wanting to abstract away from tracing / logging so I can mix and match the two.
+
+Some of these cloud functions are invoked via HTTP, others from [Pub/Sub](https://cloud.google.com/pubsub) messages.
+
+For Pub/Sub I have jury-rigged persisting
+[the state of a Span to propagate between processes](https://opentelemetry-python.readthedocs.io/en/stable/api/trace.html#opentelemetry.trace.SpanContext).
+To ensure that a trace that goes from function to function via pub/sub remains contiguous.
+
+I'm *sure* there is a better way of doing this but this is good enough for my purposes and by putting my solution
+out in the wild I'm hoping to get feedback to help improve it.
+
+For http I have used the [W3C Trace Context Level1 Recommendation]( https://www.w3.org/TR/trace-context/)
+from 6 February 2020. I rolled my own here as I didn't find an existing Python implementation. Again if I have
+missed something and someone would like to put me right that would be great!
+
+# Installation
+
+```
+pip install barium-meal
+```
+
+# Usage
+
+The tests are the best guide to usage. In the interests of keeping things DRY please take a look there.
+
+# Running the tests
+
+In a new virtual environment:
+
+```
+python setup.py develop
+pytest
+```
+
+%package -n python3-barium-meal
+Summary: Convenience wrapper for OpenTelemetry
+Provides: python-barium-meal
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-barium-meal
+# barium-meal
+
+Python Wrapper for [OpenTelemetry](https://opentelemetry.io/) written to scratch the itch
+of needing to use the same / similar code across several [Google Cloud Functions](https://cloud.google.com/functions)
+and wanting to abstract away from tracing / logging so I can mix and match the two.
+
+Some of these cloud functions are invoked via HTTP, others from [Pub/Sub](https://cloud.google.com/pubsub) messages.
+
+For Pub/Sub I have jury-rigged persisting
+[the state of a Span to propagate between processes](https://opentelemetry-python.readthedocs.io/en/stable/api/trace.html#opentelemetry.trace.SpanContext).
+To ensure that a trace that goes from function to function via pub/sub remains contiguous.
+
+I'm *sure* there is a better way of doing this but this is good enough for my purposes and by putting my solution
+out in the wild I'm hoping to get feedback to help improve it.
+
+For http I have used the [W3C Trace Context Level1 Recommendation]( https://www.w3.org/TR/trace-context/)
+from 6 February 2020. I rolled my own here as I didn't find an existing Python implementation. Again if I have
+missed something and someone would like to put me right that would be great!
+
+# Installation
+
+```
+pip install barium-meal
+```
+
+# Usage
+
+The tests are the best guide to usage. In the interests of keeping things DRY please take a look there.
+
+# Running the tests
+
+In a new virtual environment:
+
+```
+python setup.py develop
+pytest
+```
+
+%package help
+Summary: Development documents and examples for barium-meal
+Provides: python3-barium-meal-doc
+%description help
+# barium-meal
+
+Python Wrapper for [OpenTelemetry](https://opentelemetry.io/) written to scratch the itch
+of needing to use the same / similar code across several [Google Cloud Functions](https://cloud.google.com/functions)
+and wanting to abstract away from tracing / logging so I can mix and match the two.
+
+Some of these cloud functions are invoked via HTTP, others from [Pub/Sub](https://cloud.google.com/pubsub) messages.
+
+For Pub/Sub I have jury-rigged persisting
+[the state of a Span to propagate between processes](https://opentelemetry-python.readthedocs.io/en/stable/api/trace.html#opentelemetry.trace.SpanContext).
+To ensure that a trace that goes from function to function via pub/sub remains contiguous.
+
+I'm *sure* there is a better way of doing this but this is good enough for my purposes and by putting my solution
+out in the wild I'm hoping to get feedback to help improve it.
+
+For http I have used the [W3C Trace Context Level1 Recommendation]( https://www.w3.org/TR/trace-context/)
+from 6 February 2020. I rolled my own here as I didn't find an existing Python implementation. Again if I have
+missed something and someone would like to put me right that would be great!
+
+# Installation
+
+```
+pip install barium-meal
+```
+
+# Usage
+
+The tests are the best guide to usage. In the interests of keeping things DRY please take a look there.
+
+# Running the tests
+
+In a new virtual environment:
+
+```
+python setup.py develop
+pytest
+```
+
+%prep
+%autosetup -n barium-meal.macosx-10.15-x86_64-0.0.13
+
+%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-barium-meal -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.13-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..600133a
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+27c198ea83cbe4f4c886e007ec2eb515 barium-meal-0.0.13.macosx-10.15-x86_64.tar.gz