1 | initial version |

It seems that `integral`

never returns in this use case, at least with `Maxima`

's (default) integrator. This is a bug (now Trac#31351).

Workaround : use `algorithm="sympy", which seems to be exempt of this particular quirk.

Or use numerical integration (the current code uses symbolic integration with numerical rather than symbolic constants).

2 | No.2 Revision |

It seems that `integral`

never returns in this use case, at least with `Maxima`

's (default) integrator. This is a bug (now Trac#31351).

Workaround : use `algorithm="sympy", which seems to be exempt of this particular quirk.

Or use numerical integration (the current code uses symbolic integration with numerical rather than symbolic constants).

**EDIT :** Further exploration shows that the problem is Maxima's (see ticket...).

3 | No.3 Revision |

It seems that `integral`

never returns in this use case, at least with `Maxima`

's (default) integrator. This is a bug (now Trac#31351).

Workaround : use ~~`algorithm="sympy", ~~`algorithm="sympy"`

, which seems to be exempt of this particular quirk.

Or use numerical integration (the current code uses symbolic integration with numerical rather than symbolic constants).

**EDIT :** Further exploration shows that the problem is Maxima's (see ticket...).

4 | No.4 Revision |

`integral`

never returns in this use case, at least with `Maxima`

's (default) integrator. This is a bug (now Trac#31351).

Workaround : use `algorithm="sympy"`

, which seems to be exempt of this particular quirk.

**EDIT :** Further exploration shows that the problem is Maxima's (see ticket...).

**EDIT :** Problem reported upstream (see ticket...).

Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.