blob: 1fe4b4b3af4dba98342d672964f8f3f8269959f7 (
plain)
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
|
%global _empty_manifest_terminate_build 0
Name: python-linode-python
Version: 1.1.1
Release: 1
Summary: Python bindings for Linode API
License: UNKNOWN
URL: https://github.com/tjfontaine/linode-python
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/4b/74/e488eb310b266e679e9e5095563be08185f2923802fb87be8f5cad652b74/linode-python-1.1.1.tar.gz
BuildArch: noarch
%description
# Linode Python Bindings
The bindings consist of three pieces:
- api.py: Core library that manages authentication and api calls
- shell.py: A command line interface to api.py that allows you to invoke
a specific api command quickly
- oop.py: An object oriented interface to api.py inspired by django
For definitive documentation on how the api works please visit:
https://www.linode.com/api
## API Keys
When creating an api object you may specify the key manually, or use the
Api.user_getapikey which will return your apikey as well as set the internal
key that will be used for subsequent api calls.
Both the shell.py and oop.py have mechanisms to pull the api key from the
environment variable LINODE_API_KEY as well.
## Batching
Batching should be used with care, once enabled all api calls are cached until
Api.batchFlush() is called, however you must remember the order in which calls
were made as that's the order of the list returned to you
## License
This code is provided under an MIT-style license. Please refer to the LICENSE
file in the root of the project for specifics.
%package -n python3-linode-python
Summary: Python bindings for Linode API
Provides: python-linode-python
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-linode-python
# Linode Python Bindings
The bindings consist of three pieces:
- api.py: Core library that manages authentication and api calls
- shell.py: A command line interface to api.py that allows you to invoke
a specific api command quickly
- oop.py: An object oriented interface to api.py inspired by django
For definitive documentation on how the api works please visit:
https://www.linode.com/api
## API Keys
When creating an api object you may specify the key manually, or use the
Api.user_getapikey which will return your apikey as well as set the internal
key that will be used for subsequent api calls.
Both the shell.py and oop.py have mechanisms to pull the api key from the
environment variable LINODE_API_KEY as well.
## Batching
Batching should be used with care, once enabled all api calls are cached until
Api.batchFlush() is called, however you must remember the order in which calls
were made as that's the order of the list returned to you
## License
This code is provided under an MIT-style license. Please refer to the LICENSE
file in the root of the project for specifics.
%package help
Summary: Development documents and examples for linode-python
Provides: python3-linode-python-doc
%description help
# Linode Python Bindings
The bindings consist of three pieces:
- api.py: Core library that manages authentication and api calls
- shell.py: A command line interface to api.py that allows you to invoke
a specific api command quickly
- oop.py: An object oriented interface to api.py inspired by django
For definitive documentation on how the api works please visit:
https://www.linode.com/api
## API Keys
When creating an api object you may specify the key manually, or use the
Api.user_getapikey which will return your apikey as well as set the internal
key that will be used for subsequent api calls.
Both the shell.py and oop.py have mechanisms to pull the api key from the
environment variable LINODE_API_KEY as well.
## Batching
Batching should be used with care, once enabled all api calls are cached until
Api.batchFlush() is called, however you must remember the order in which calls
were made as that's the order of the list returned to you
## License
This code is provided under an MIT-style license. Please refer to the LICENSE
file in the root of the project for specifics.
%prep
%autosetup -n linode-python-1.1.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-linode-python -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Apr 25 2023 Python_Bot <Python_Bot@openeuler.org> - 1.1.1-1
- Package Spec generated
|
