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
|
%global _empty_manifest_terminate_build 0
Name: python-i2
Version: 0.0.183
Release: 1
Summary: Creating manipulating and applying mint (Meta-INTerface)
License: Apache Software License
URL: https://github.com/i2mint/i2
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/06/b7/8af2a381a305eee0c5d5f8b8b77d4cfaead9f0d3475dd223c5c7603fd147/i2-0.0.183.tar.gz
BuildArch: noarch
%description
# i2
Core tools for minting code.
[Documentation here.](https://i2mint.github.io/i2/)
## What's mint?
Mint stands for "Meta-INTerface".
Minting is core technique of i2i: It can be seen as the encapsulation of a construct’s interface into a (data)
structure that contains everything one needs to know about the construct to perform a specific action
with or on the construct.
A little note on the use of “encapsulation”. The term is widely used in computer science,
and is typically tied to object oriented programming. Wikipedia provides two definitions:
* A language mechanism for restricting direct access to some of the object's components.
* A language construct that facilitates the bundling of data with the methods (or other functions)
operating on that data.
Though both these definitions apply to minting,
the original sense of the word “encapsulate” is even more relevant (from google definitions):
* express the essential features of (something) succinctly
* enclose (something) in or as if in a capsule
Indeed, minting is the process of enclosing a construct into a “mint” (for “Meta INTerface”)
that will express the features of the construct that are essential to the task at hand.
The mint provides a declarative layer of the construct that allows one to write code that operates with this layer,
which is designed to be (as) consistent (as possible) from one system/language to another.
For example, whether a (non-anonymous) function was written in C, Python, or JavaScript,
it will at least have a name, and it’s arguments will (most often) have names, and may have types.
Similarly with “data objects”: The data of both JavaScript and Python objects can be represented by a tree whose
leaves are base types, which can in turn be represented by a C struct.
%package -n python3-i2
Summary: Creating manipulating and applying mint (Meta-INTerface)
Provides: python-i2
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-i2
# i2
Core tools for minting code.
[Documentation here.](https://i2mint.github.io/i2/)
## What's mint?
Mint stands for "Meta-INTerface".
Minting is core technique of i2i: It can be seen as the encapsulation of a construct’s interface into a (data)
structure that contains everything one needs to know about the construct to perform a specific action
with or on the construct.
A little note on the use of “encapsulation”. The term is widely used in computer science,
and is typically tied to object oriented programming. Wikipedia provides two definitions:
* A language mechanism for restricting direct access to some of the object's components.
* A language construct that facilitates the bundling of data with the methods (or other functions)
operating on that data.
Though both these definitions apply to minting,
the original sense of the word “encapsulate” is even more relevant (from google definitions):
* express the essential features of (something) succinctly
* enclose (something) in or as if in a capsule
Indeed, minting is the process of enclosing a construct into a “mint” (for “Meta INTerface”)
that will express the features of the construct that are essential to the task at hand.
The mint provides a declarative layer of the construct that allows one to write code that operates with this layer,
which is designed to be (as) consistent (as possible) from one system/language to another.
For example, whether a (non-anonymous) function was written in C, Python, or JavaScript,
it will at least have a name, and it’s arguments will (most often) have names, and may have types.
Similarly with “data objects”: The data of both JavaScript and Python objects can be represented by a tree whose
leaves are base types, which can in turn be represented by a C struct.
%package help
Summary: Development documents and examples for i2
Provides: python3-i2-doc
%description help
# i2
Core tools for minting code.
[Documentation here.](https://i2mint.github.io/i2/)
## What's mint?
Mint stands for "Meta-INTerface".
Minting is core technique of i2i: It can be seen as the encapsulation of a construct’s interface into a (data)
structure that contains everything one needs to know about the construct to perform a specific action
with or on the construct.
A little note on the use of “encapsulation”. The term is widely used in computer science,
and is typically tied to object oriented programming. Wikipedia provides two definitions:
* A language mechanism for restricting direct access to some of the object's components.
* A language construct that facilitates the bundling of data with the methods (or other functions)
operating on that data.
Though both these definitions apply to minting,
the original sense of the word “encapsulate” is even more relevant (from google definitions):
* express the essential features of (something) succinctly
* enclose (something) in or as if in a capsule
Indeed, minting is the process of enclosing a construct into a “mint” (for “Meta INTerface”)
that will express the features of the construct that are essential to the task at hand.
The mint provides a declarative layer of the construct that allows one to write code that operates with this layer,
which is designed to be (as) consistent (as possible) from one system/language to another.
For example, whether a (non-anonymous) function was written in C, Python, or JavaScript,
it will at least have a name, and it’s arguments will (most often) have names, and may have types.
Similarly with “data objects”: The data of both JavaScript and Python objects can be represented by a tree whose
leaves are base types, which can in turn be represented by a C struct.
%prep
%autosetup -n i2-0.0.183
%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-i2 -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.183-1
- Package Spec generated
|
