Your message dated Sat, 11 Mar 2006 06:45:28 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356343: quantlib-python: heston MC engine not exported ?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: quantlib-python
Version: 0.3.11-3+b1
Severity: normal
Hi,
I am learning quantlib hoping to use it in python rather than C++. In
the process, I am studying the test-suite in the source package and
found that there is a heston model. However, it seems that they are not
present in the interface.
Is this intended ?
regards,
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.32-xbox-chimpanzee-vs-ll
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages quantlib-python depends on:
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-10 GCC support library
ii libquantlib-0.3.11c2a 0.3.11-2.1+b1 Quantitative Finance Library -- de
ii libstdc++6 4.0.2-10 The GNU Standard C++ Library v3
quantlib-python recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Gary,
On 11 March 2006 at 19:22, [EMAIL PROTECTED] wrote:
| Package: quantlib-python
| Version: 0.3.11-3+b1
| Severity: normal
|
| Hi,
|
| I am learning quantlib hoping to use it in python rather than C++. In
| the process, I am studying the test-suite in the source package and
| found that there is a heston model. However, it seems that they are not
| present in the interface.
|
| Is this intended ?
I suggest you ask that on the quantlib mailing list. The package simply
builds what is there, no more, no less. So no bug here, really. If you feel
really strongly that this feature request / upstream question should remain
open, send me a note.
A personal observation: Years ago, I uses to use the quantlib-python examples
as blueprints to derive my RQuantlib examples from. Quantlib's internal
changed a few times over the years and the number of functions exposed to
Python has not been the same. So Quantlib could probably do with a
contributor who keeps the Swig interface up to date ...
Dirk
| regards,
|
|
| -- System Information:
| Debian Release: testing/unstable
| APT prefers unstable
| APT policy: (500, 'unstable')
| Architecture: i386 (i686)
| Shell: /bin/sh linked to /bin/bash
| Kernel: Linux 2.4.32-xbox-chimpanzee-vs-ll
| Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
|
| Versions of packages quantlib-python depends on:
| ii libc6 2.3.6-3 GNU C Library: Shared libraries
an
| ii libgcc1 1:4.0.2-10 GCC support library
| ii libquantlib-0.3.11c2a 0.3.11-2.1+b1 Quantitative Finance Library --
de
| ii libstdc++6 4.0.2-10 The GNU Standard C++ Library v3
|
| quantlib-python recommends no packages.
|
| -- no debconf information
|
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--- End Message ---
