Karim Belbas asked me Did anybody start working on the removal of
genus2reduction from Sage
packages ? (To switch to the much better one now built in PARI.)
Also after I mentioned that Frederic Chapoton has recently worked on
the Sage interface to Tim Dokchitser's ComputeL package Karim replied
Hi Robert,
Also, this seems like a
lot of busywork--we should be able to automatically generate these
classes for any matrix type when nrows == ncols. But this is exactly
what the category framework gives you (though it could have done so
with a more sophisticated getattr rather than
Hello John,
It would be good to have more people interested in the pari/Sage
interface attending their workshop in early January.
I am definitely interested in going to the workshop. It is clear that the
interface between PARI and Sage is very important; there are many things
that either
I talked to Pascal in Bristol fwiw, and apparently the bnr stuff isn't
wrapped in Sage. We created at quickdirty Cython wrapper for LMFDB, but it
would probably be nice to push that into Sage.
On a related note, Jeroen started a thread about the error handler thing on
pari-dev
On Sat, Sep 21, 2013 at 8:09 AM, Peter Bruin pjbr...@gmail.com wrote:
Hi Robert,
Also, this seems like a
lot of busywork--we should be able to automatically generate these
classes for any matrix type when nrows == ncols. But this is exactly
what the category framework gives you (though
Hello Volker,
I talked to Pascal in Bristol fwiw, and apparently the bnr stuff isn't
wrapped in Sage. We created at quickdirty Cython wrapper for LMFDB, but it
would probably be nice to push that into Sage.
Yes, that is a good example.
On a related note, Jeroen started a thread about
Hello Travis,
So the proposed change isn't really that big after all, just a
renaming and the addition of one level of nesting.
class MyCategory(Cagetory_singleton):
class Object:
...
class Element:
...
I'm against this because that means there
Op woensdag 18 september 2013 10:22:04 UTC+1 schreef Jeroen Demeyer:
On 2013-09-18 07:20, Dima Pasechnik wrote:
accoring to http://www.python.org/dev/peps/pep-0263/
$SAGE_LOCAL/bin/hg might benefit from the 2nd line saying
# -*- coding: latin-1 -*-
(or # -*- coding: utf-8 -*-) ?
PEP 0263 says explicitly that the encoding magic can occur either on the
first or on the second line, presumably for cases like this, so it looks
like it is worth trying.
(If it already tries to decode the first line before looking at the second
line to see if it specifies an encoding,
I'm trying to review #7539 which aims to include the small primesieve
library in Sage, but I'm not quite up to date on what the current policy is
on including new SPKGs. I thought at one point it was decided that all new
SPKGs needed to be optional for a period before becoming standard, however
Not that this bug shouldn't be fixed, and not that there aren't valid reasons
for running sage in an emacs shell, but just in case you didn't know: you can
install the sage_mode spkg and run sage directly using the `sage' command.
-Ivan
On Sep 20, 2013, at 11:54 AM, Bill Janssen
11 matches
Mail list logo