dijitso 2017.1.0-3 source package in Ubuntu
Changelog
dijitso (2017.1.0-3) unstable; urgency=medium * Team upload. * Depends: python-pkg-resources. Closes: #879988. * Standards-Version: 4.1.1 -- Drew Parsons <email address hidden> Sun, 29 Oct 2017 02:10:31 +0800
Upload details
- Uploaded by:
- Debian Science Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Science Team
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| dijitso_2017.1.0-3.dsc | 2.2 KiB | e4e4be9a33f56dddabccb731e8f20db8c4be19d1b2ca03856da802f829c26660 |
| dijitso_2017.1.0.orig.tar.gz | 50.0 KiB | ef23952539d349fbd384d41302abc94413d485ca7e8c29e8a0debc2aadaf8657 |
| dijitso_2017.1.0-3.debian.tar.xz | 8.4 KiB | 167b2076e59f9591ae109ea71c0acc161f079a5cead473f7f01acd3cea3315b5 |
Available diffs
- diff from 2016.2.0-1 to 2017.1.0-3 (3.6 KiB)
- diff from 2017.1.0-2 to 2017.1.0-3 (579 bytes)
No changes file available.
Binary packages built by this source
- python-dijitso: 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.
- python3-dijitso: 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.
