Re: [sage-devel] Trivial changes in pari interface from 9.3 to 9.4 break compatibility

2021-09-20 Thread Nils Bruin
On Monday, 20 September 2021 at 12:58:10 UTC-7 jus...@mac.com wrote: > I’m not sure this is relevant to your issue, but FWIW, I tried in recent > versions of Pari, and noticed two things: > - “?qfminim" documents the use of ‘b’ as the second argument, while > "??qfminim" documents the use of ‘B

Re: [sage-devel] Trivial changes in pari interface from 9.3 to 9.4 break compatibility

2021-09-20 Thread 'Justin C. Walker' via sage-devel
I’m not sure this is relevant to your issue, but FWIW, I tried in recent versions of Pari, and noticed two things: - “?qfminim" documents the use of ‘b’ as the second argument, while "??qfminim" documents the use of ‘B’. - using the forms “b=“ and “B=“ in the calls with a second argument makes no

[sage-devel] Trivial changes in pari interface from 9.3 to 9.4 break compatibility

2021-09-20 Thread Nils Bruin
I noticed that in pari.qfminim; from 9.3 to 9.4 there was a trivial change: the second parameter changed name from 'b' to 'B'. This breaks code that calls it with 'b' as a keyword. I had trouble tracing this change, but it looks like this is in some automatically generated interface. It's gene