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
|
%global _empty_manifest_terminate_build 0
Name: python-logx
Version: 0.1.1579232358
Release: 1
Summary: best practice python logging with zero config
License: Unlicense
URL: https://github.com/djrobstep/logx
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/a3/34/e155c7865cb52120190def8bbe76e874f7a8100567ca7d66009cd6dab078/logx-0.1.1579232358.tar.gz
BuildArch: noarch
Requires: python3-pyyaml
Requires: python3-logging_tree
%description
# logx: best practice python logging with zero config
Configuring logging is tedious. Reading the logging module docs makes me tired.
Wouldn't it be nice to log as easily as doing a print statement, without any upfront config?
## Obligatory example
Enter `logx`. It's as simple as:
>>> from logx import log
>>> log.info('hello world')
hello world
>>> log.set_default_format()
>>> log.warn('warning!')
[2018-02-26 21:51:16,971] WARNING [__main__.<module>:1] warning!
Logs get logged automatically to the logger whose name matches the current module.
## List of sweet features
- Creates loggers lazily/as needed/on demand and **logs to the appropriate logger automatically**. If you're in the "acme" module it'll log to a log called "acme", no need worry about logger names and instances.
- **Shows all log messages by default**, which follows the principle of least surprise and is probably what you want when debugging.
- Included default handler **logs to the appropriate standard output stream by default**: Errors and warnings to stderr, the rest to stdout.
- Allows easy following of best practice when including log statements in a library: **Just call log.create_null_handler() in your module.**
- **Uses the standard logging library**, so you can still customize your setup as much as you want/need. Plays nicely with your existing logging config files.
- **Includes the very useful logging_tree module** for viewing your current logging configuration. `logx.print_diagram()`
## Install
>>> pip install logx
## Contribute
Issues and pull requests welcome, hit me. Am I doing logging completely wrong? Critique welcome, even if very pedantic.
%package -n python3-logx
Summary: best practice python logging with zero config
Provides: python-logx
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-logx
# logx: best practice python logging with zero config
Configuring logging is tedious. Reading the logging module docs makes me tired.
Wouldn't it be nice to log as easily as doing a print statement, without any upfront config?
## Obligatory example
Enter `logx`. It's as simple as:
>>> from logx import log
>>> log.info('hello world')
hello world
>>> log.set_default_format()
>>> log.warn('warning!')
[2018-02-26 21:51:16,971] WARNING [__main__.<module>:1] warning!
Logs get logged automatically to the logger whose name matches the current module.
## List of sweet features
- Creates loggers lazily/as needed/on demand and **logs to the appropriate logger automatically**. If you're in the "acme" module it'll log to a log called "acme", no need worry about logger names and instances.
- **Shows all log messages by default**, which follows the principle of least surprise and is probably what you want when debugging.
- Included default handler **logs to the appropriate standard output stream by default**: Errors and warnings to stderr, the rest to stdout.
- Allows easy following of best practice when including log statements in a library: **Just call log.create_null_handler() in your module.**
- **Uses the standard logging library**, so you can still customize your setup as much as you want/need. Plays nicely with your existing logging config files.
- **Includes the very useful logging_tree module** for viewing your current logging configuration. `logx.print_diagram()`
## Install
>>> pip install logx
## Contribute
Issues and pull requests welcome, hit me. Am I doing logging completely wrong? Critique welcome, even if very pedantic.
%package help
Summary: Development documents and examples for logx
Provides: python3-logx-doc
%description help
# logx: best practice python logging with zero config
Configuring logging is tedious. Reading the logging module docs makes me tired.
Wouldn't it be nice to log as easily as doing a print statement, without any upfront config?
## Obligatory example
Enter `logx`. It's as simple as:
>>> from logx import log
>>> log.info('hello world')
hello world
>>> log.set_default_format()
>>> log.warn('warning!')
[2018-02-26 21:51:16,971] WARNING [__main__.<module>:1] warning!
Logs get logged automatically to the logger whose name matches the current module.
## List of sweet features
- Creates loggers lazily/as needed/on demand and **logs to the appropriate logger automatically**. If you're in the "acme" module it'll log to a log called "acme", no need worry about logger names and instances.
- **Shows all log messages by default**, which follows the principle of least surprise and is probably what you want when debugging.
- Included default handler **logs to the appropriate standard output stream by default**: Errors and warnings to stderr, the rest to stdout.
- Allows easy following of best practice when including log statements in a library: **Just call log.create_null_handler() in your module.**
- **Uses the standard logging library**, so you can still customize your setup as much as you want/need. Plays nicely with your existing logging config files.
- **Includes the very useful logging_tree module** for viewing your current logging configuration. `logx.print_diagram()`
## Install
>>> pip install logx
## Contribute
Issues and pull requests welcome, hit me. Am I doing logging completely wrong? Critique welcome, even if very pedantic.
%prep
%autosetup -n logx-0.1.1579232358
%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-logx -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Thu Jun 08 2023 Python_Bot <Python_Bot@openeuler.org> - 0.1.1579232358-1
- Package Spec generated
|
