dijitso 2017.2.0.0-2 source package in Ubuntu
Changelog
dijitso (2017.2.0.0-2) unstable; urgency=medium * debian/control: update VCS tags to salsa.debian.org -- Drew Parsons <email address hidden> Wed, 21 Feb 2018 22:43:50 +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 | |
---|---|---|---|---|
Bionic | release | universe | misc |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
dijitso_2017.2.0.0-2.dsc | 2.4 KiB | 54dd875bf058348373125e78c54e96c067784db41d7313aad462db6ad3b2665d |
dijitso_2017.2.0.0.orig.tar.gz | 51.2 KiB | 05a893d17f8a50067d303b232e41592dce2840d6499677ad8b457ba58a679b58 |
dijitso_2017.2.0.0.orig.tar.gz.asc | 473 bytes | 0c01c71da55825afe37e42c80c30036067508d2ed55d9a32814b5e0b34e18c91 |
dijitso_2017.2.0.0-2.debian.tar.xz | 4.3 KiB | 8557b9b68e68fa079ae8c666c36304232602dce3d3bdedfd5506b8611119bfc9 |
Available diffs
- diff from 2017.1.0-3 to 2017.2.0.0-2 (12.1 KiB)
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.