Ask Your Question

Monkey-patching PARI calls

asked 2017-11-27 00:37:25 +0200

orangejake gravatar image

updated 2017-11-27 05:06:40 +0200

I'm currently trying to implement some number field computations on a very particular number field (specifically, $K = \mathbb{Q}(\zeta_{n-1},n^{1/(n-1)})$). The code I've written so far has some bottlenecks that profiling via %prun has identified, namely:

  1. {method '_nf_rnfeq' of 'sage.libs.cypari2.gen.gen' objects}, which seems to compute the minimal polynomial of $K$ (currently I'm defining $K$ via F.<u> = CyclotomicField(n-1), and then K.<a> = F.extension(x^(n-1) - n), so $K$ is a relative extension. _nf_rnfeq seems to compute the absolute minimal polynomial of a given relative extension (via PARI).

  2. {method 'discriminant' of 'sage.rings.polynomial.polynomial_integer_dense_flint.Polynomial_integer_dense_flint' objects}, which appears to just be the polynomial discriminant computation.

Assume I've done analysis by hand gives me a much faster computation of the absolute minimal polynomial for this particular number field. I'd then want a version of _nf_rnfeq that:

  1. Checks if it's being called on my special case, where better algorithms exist. If so, run that.
  2. Otherwise, run the traditional algorithm.

Of course, I'd prefer to make this modification without modifying the source code, as that seems to be an especially ugly solution.

One way to implement this is to change is by modifying the relevant method at run-time, via a technique known as "Monkey-Patching" (see (here)).

The issue I'm having now is that attempting to monkey-patch the PARI call gives me the error:

TypeError: can't set attributes of built-in/extension type 'sage.libs.cypari2.gen.gen'

The code I'm using (in the first cell of my IPython notebook) is below:

import sage.libs.cypari2.gen
orig_nf_rnfeq = sage.libs.cypari2.gen.gen._nf_rnfeq
def _nf_rnfeq(*args, **kwargs):
    print("Rnfeq works!")
    return orig_nf_rnfeq(*args, **kwargs)

sage.libs.cypari2.gen.gen._nf_rnfeq = _nf_rnfeq
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2017-11-27 10:10:24 +0200

vdelecroix gravatar image

Monkey patching does not apply to extension modules (that is compiled Python module from C source code). And sage.libs.cypari2 is an extension module written in Cython.

The best way to go in your situation is to use a home compiled version of Sage and start modifying its source code. The procedure is described in the developer manual. Note that the cypari2 code is an external package of Sage (see that you clearly do not want to modify.

edit flag offensive delete link more


Could something like forebidden fruit let me avoid modifying source? That'd make it more difficult to distribute my code later.

orangejake gravatar imageorangejake ( 2017-11-27 10:23:46 +0200 )edit

No. Forebidden fruit would allow you to use monkey patching on C objects. To modify the source code you just need a text editor.

vdelecroix gravatar imagevdelecroix ( 2017-11-27 10:37:46 +0200 )edit

Does monkey patching work for purely sage libraries?

orangejake gravatar imageorangejake ( 2017-11-29 07:53:37 +0200 )edit

The distinction between "pure Sage library" and "external library" is just a matter of distribution (Sage is directly responsible of its library but not directly to the external ones). They are the very same from Python point of view.

vdelecroix gravatar imagevdelecroix ( 2017-11-30 21:13:17 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-11-27 00:37:25 +0200

Seen: 321 times

Last updated: Nov 27 '17