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
|
Source: dijitso
Section: python
Priority: optional
Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Uploaders:
Johannes Ring <johannr@simula.no>,
Drew Parsons <dparsons@debian.org>
Build-Depends:
debhelper (>= 9),
dh-python,
python-all,
python-setuptools,
python-six,
python-numpy,
python3-all,
python3-setuptools,
python3-six,
python3-numpy
Standards-Version: 3.9.8
Homepage: https://fenicsproject.org
X-Python-Version: >= 2.7
X-Python3-Version: >= 3.4
Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/fenics/dijitso.git
Vcs-Browser: https://anonscm.debian.org/git/debian-science/packages/fenics/dijitso.git/
Testsuite: autopkgtest-pkg-python
Package: python-dijitso
Architecture: all
Depends:
python-numpy,
python-six,
python-mpi4py,
python-subprocess32,
${python:Depends},
${misc:Depends}
Suggests: python-dijitso-doc
Description: distributed just-in-time building of shared libraries (Python 2)
Dijitso was written to improve a core component of the FEniCS
framework, namely the just in time compilation of C++ code that is
generated from Python modules, but is only called from within a C++
library, and thus do not need wrapping in a nice Python interface.
.
The main approach of dijitso is to use ctypes to import the dynamic
shared library directly with no attempt at wrapping it in a Python
interface.
.
As long as the compiled code can provide a simple factory function to
a class implementing a predefined C++ interface, there is no limit to
the complexity of that interface as long as it is only called from
C++ code, If you want a Python interface to your generated code,
dijitso is probably not the answer.
.
Although dijitso serves a very specific role within the FEniCS
project, it does not depend on other FEniCS components.
.
The parallel support depends on the mpi4py interface, although mpi4py
is not actually imported within the dijitso module so it would be
possible to mock the communicator object with a similar interface.
.
This package installs the library for Python 2.
Package: python3-dijitso
Architecture: all
Depends:
python3-numpy,
python3-six,
python3-mpi4py,
${python3:Depends},
${misc:Depends}
Suggests: python-dijitso-doc
Description: distributed just-in-time building of shared libraries (Python 3)
Dijitso was written to improve a core component of the FEniCS
framework, namely the just in time compilation of C++ code that is
generated from Python modules, but is only called from within a C++
library, and thus do not need wrapping in a nice Python interface.
.
The main approach of dijitso is to use ctypes to import the dynamic
shared library directly with no attempt at wrapping it in a Python
interface.
.
As long as the compiled code can provide a simple factory function to
a class implementing a predefined C++ interface, there is no limit to
the complexity of that interface as long as it is only called from
C++ code, If you want a Python interface to your generated code,
dijitso is probably not the answer.
.
Although dijitso serves a very specific role within the FEniCS
project, it does not depend on other FEniCS components.
.
The parallel support depends on the mpi4py interface, although mpi4py
is not actually imported within the dijitso module so it would be
possible to mock the communicator object with a similar interface.
.
This package installs the library for Python 3.
|
