Doesn't adding
# not tested
work?
John
On 23 June 2010 13:39, John H Palmieri wrote:
> In the file misc/sagedocs.py, there are some methods which are one-
> liners: they just open up a piece of the documentation in a web
> browser:
>
> def tutorial(self):
> """
> The Sage tutori
I am a M.Sc. math student at the University of Mainz, Germany. I would
be interested in working on a SAGE project as a master thesis, e.g.
related to number theory (eg. elliptic curves, although it doesn't
have to be number theory exclusively). Are there tasks in SAGE
available as a master thesis f
Hello, Bill.
You wrote 22 июня 2010 г., 3:30:30:
> BSDNT
> ..
> scratch. One idea I had was to write all the low level routines in
> LLVM instead of assembly, then just build suitable optimisations into
> LLVM so that nice assembly is automatically produced. This is entirely
> feasible and wou
How about
sage: tutorial() # optional
with no return value? It would be better if the tag optional can be
removed as the doctest mechanism prevent a web browser from opening.
Your cheating is a bad idea.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubs
On Wed, Jun 23, 2010 at 6:29 PM, Kwankyu Lee wrote:
> Hi,
>
> I might be a beginner of the toric geometry package in Sage.
>
> I prefer long and explicit names for method names. However, I also
> prefer to see those methods have docstrings that are written using the
> traditional N and M notations
I would vote for more descriptive names in general, while making some
effort to control their length.
-Marshall
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit
On Wed, 23 Jun 2010 18:29:02 -0700 (PDT), Kwankyu Lee
wrote:
> I also want to mention that N reminds me of the Mathematica N()
> command to get a numerical value.
Not just Mathematica. In Sage:
sage: N?
Base Class:
String Form:
Namespace: Interactive
File:
/home/ghitza
Hi,
I might be a beginner of the toric geometry package in Sage.
I prefer long and explicit names for method names. However, I also
prefer to see those methods have docstrings that are written using the
traditional N and M notations.
I also want to mention that N reminds me of the Mathematica N(
On Wed, 23 Jun 2010 16:12:45 -0700 (PDT), Rob Beezer
wrote:
> "Python doesn't have an "end" statement!", I hear you say.
>
> Try in the notebook, as a colleague new to Sage basically did with a
> more serious purpose,
>
> a = 3
> if a == 1:
> a = a+1
> else:
> a = 6
> end
> a += 1
>
>
On 23 June 2010 22:17, William Stein wrote:
> On Wed, Jun 23, 2010 at 11:41 AM, Andrey Novoseltsev
> wrote:
>> I have no idea what is wrong, but I have had the same problem for a
>> while (but was too lazy to report it, since I usually use geom
>> anyway).
>>
>
> I've seen it too, and I have no
> "end" is a Sage function that constructs an endomorphism. So the
> "statement" above is harmless. Is this enough reason to give this
> function a new, less-confusion-causing name?
Nope. Newbies will make mistakes, we can't avoid 'em all (or bend
over backwards for many). I think end is a per
Hi David,
On Wed, 23 Jun 2010 22:24:44 +0100, "Dr. David Kirkby"
wrote:
> So far, on 3 systems where this has been tested, there are 5 failures on
> each,
> though the 5 failures differ between systems - with one exception
> (test_distutils) which seems to fail on all systems.
On:
[ghi...@
"Python doesn't have an "end" statement!", I hear you say.
Try in the notebook, as a colleague new to Sage basically did with a
more serious purpose,
a = 3
if a == 1:
a = a+1
else:
a = 6
end
a += 1
"end" is a Sage function that constructs an endomorphism. So the
"statement" above is har
The difference between the toric lattice computations and the root
lattices is that the (co)weight lattices are one of the main features
of interest to the end user, while the various toric lattices are
mostly of internal use for computing something else.
I don't have a strong opinion against long
Python plays a pretty big role in Sage, when it is built, the Python self-tests
are not run. Neither are they run if you build Sage with SAGE_CHECK=yes.
If you want to see if Python builds ok on your system, try this package
http://boxen.math.washington.edu/home/kirkby/revised-patches/python-2
On Wed, Jun 23, 2010 at 11:41 AM, Andrey Novoseltsev wrote:
> I have no idea what is wrong, but I have had the same problem for a
> while (but was too lazy to report it, since I usually use geom
> anyway).
>
I've seen it too, and I have no clue how to fix it either.
William
> Andrey
>
> On Jun
In the file misc/sagedocs.py, there are some methods which are one-
liners: they just open up a piece of the documentation in a web
browser:
def tutorial(self):
"""
The Sage tutorial. To get started with Sage, start here.
"""
self._open("tutorial")
How can thi
Since there is a plan to add GLPK as a standard package, and it did not build
build on 64-bit Solaris due to the lack of suitable compiler flags being added,
Robert Miller created a ticket to fix the compiler flag issue.
On inspection, I found so many things wrong with this that I basically re-
> My general two cents: explicit (=long) is better than implicit
> (=short). However it should be easy for the user to define its own short
> names.
My proposal in the ticket was to add a function that will create short
synonims for all such methods, if a user so desires. Of course, if
this is don
Hi Andrey,
> Volker and I have some disagreement on names used in
> http://trac.sagemath.org/sage_trac/ticket/9296 and it would be VERY
> nice to get other people opinions. I'll try to be short.
First of all, a general comment:
+1 to have those question more frequently discussed on sage-de
Hi,
Any chance to get an answer on that one ? For short:
- should we
1- upgrade pigment from 0.11.1 to 1.3.1 (I already have an spkg) ?
2- upgrade docutils from 0.5 to 0.6 ?
3- upgrade Sphinx to 1.0 as soon as it is out (I have an experimental spkg
1.0beta2) ?
Florent
> In the pro
Hello everybody,
Volker and I have some disagreement on names used in
http://trac.sagemath.org/sage_trac/ticket/9296 and it would be VERY
nice to get other people opinions. I'll try to be short.
In toric geometry it is important/convenient to distinguish a lattice
and its dual. Standard names for
On 06/23/10 07:05 PM, Robert Bradshaw wrote:
On Jun 23, 2010, at 10:43 AM, Dr. David Kirkby wrote:
IANAL, but I doubt that is true in all cases.
I was leaving this distinction out to simplicity the discussion--the
Sage codebase is v2+, which can be mixed with v3+.
OK. I thought you were ta
I have no idea what is wrong, but I have had the same problem for a
while (but was too lazy to report it, since I usually use geom
anyway).
Andrey
On Jun 23, 2:36 pm, Robert Miller wrote:
> I have an installation of sage-4.4.4.alpha1 on geom.math for which the
> following command works:
>
> note
I have an installation of sage-4.4.4.alpha1 on geom.math for which the
following command works:
notebook(interface='geom.math.washington.edu', port=9876, secure=True,
open_viewer=False)
But on sage.math, the same command:
notebook(interface='sage.math.washington.edu', port=9876, secure=True,
ope
same result :-/
Nathann
On 22 June 2010 17:06, David Kirkby wrote:
> On 22 June 2010 08:36, Nathann Cohen wrote:
>> Hello Everybody !
>>
>> I have been trying to install the Graphviz package recently, though it
>> ended up with an error precisely when all seemed to have been compiled
>> success
I agree. I'm looking at it now.
David
On Wed, Jun 23, 2010 at 2:11 PM, Robert Bradshaw <
rober...@math.washington.edu> wrote:
> On Jun 23, 2010, at 10:32 AM, Robert Miller wrote:
>
> I'm curious about the following behavior:
>>
>> sage: E = EllipticCurve('37a')
>> sage: R = E.padic_regulator(7)
On Jun 23, 2010, at 10:32 AM, Robert Miller wrote:
I'm curious about the following behavior:
sage: E = EllipticCurve('37a')
sage: R = E.padic_regulator(7)
sage: len(R.list())
37
sage: s = str(R)
sage: len(R.list())
19
(PS - The default precision for padic_regulator is 20).
The documentation d
On Jun 23, 2010, at 10:43 AM, Dr. David Kirkby wrote:
On 06/23/10 05:49 PM, Robert Bradshaw wrote:
(v2 code can be used in a v3 project, but not the other
way around).
- Robert
IANAL, but I doubt that is true in all cases.
I was leaving this distinction out to simplicity the discussion--t
On 06/23/10 05:49 PM, Robert Bradshaw wrote:
(v2 code can be used in a v3 project, but not the other
way around).
- Robert
IANAL, but I doubt that is true in all cases.
If someone says the code is "GPL 2", then I don't believe you can necessarily
use it in GLP 3 software.
http://www.gnu.o
I'm curious about the following behavior:
sage: E = EllipticCurve('37a')
sage: R = E.padic_regulator(7)
sage: len(R.list())
37
sage: s = str(R)
sage: len(R.list())
19
(PS - The default precision for padic_regulator is 20).
The documentation doesn't say anything about what length to expect the
ou
Hi Ralf,
as far as I know, ECL hardcodes some paths to its internals in some
non-standard way.
That is not a problem, unless the Sage install is moved to a different
directory than it was built in.
Then, an environment variable "ECL_DIR" (or something like that) has
to be set, in order for
ECL to
On Jun 23, 2010, at 6:44 AM, v...@ukr.net wrote:
Hello!
On Tue, 22 Jun 2010 18:45:43 -0700
William Stein wrote:
...
The core Sage library, since we control it and many people don't like
GPL3 so much.
Excuse me for interrupting a technical discussion, but I just wanted
to ask what is wrong
> Excuse me for interrupting a technical discussion, but I just wanted
> to ask what is wrong with licensing Sage under GPLv3? Sage is a free
> software, am I right. I thought that all GPLs are for free software and
> that all of them do guarantee freedom to use and modify the software.
For one,
On 6/23/10 6:05 AM, David Poetzsch-Heffter wrote:
Hi!
I found (and fixed) a few Bugs in the file local/bin/sage-preparse.
These are the things I fixed:
* The module docstrings disappeared when preparsing because the
preparse_file function inserted those numeric_literals definitions before
the
Dear David,
These fixes sound great! Why not head on over to
http://trac.sagemath.org/sage_trac/
and make yourself an account, open a ticket, and post a patch file
there? This will require using Mercurial, which is easiest to use (if
not familiar from elsewhere) via hg_scripts.[tab] from within
Hello!
On Tue, 22 Jun 2010 18:45:43 -0700
William Stein wrote:
> ...
> The core Sage library, since we control it and many people don't like
> GPL3 so much.
>
Excuse me for interrupting a technical discussion, but I just wanted
to ask what is wrong with licensing Sage under GPLv3? Sage is a
On Jun 23, 8:40 am, hemmecke wrote:
> followup to my previous message...
>
> I tried
>
> sage -f ecl
> sage -f maxima
>
> That seemed to have finished without reporting an error. Only the last
> two lines looked a bit strange.
>
> installing Maxima library as /home/hemmecke/software/sage-source/
Some packages have quite extensive test suites and so running the test suite
every time Sage builds would not be popular. That is what SAGE_CHECK is for.
But other packages seem to have trivial tests, which take very little time to
execute. Would it not be better if these were run every time Sa
Hi!
I found (and fixed) a few Bugs in the file local/bin/sage-preparse.
These are the things I fixed:
* The module docstrings disappeared when preparsing because the
preparse_file function inserted those numeric_literals definitions before
the docstrings.
* Now also unicode-docstrings (e.g. u""
Hello !!!
> Hi Nathan, just for future reference, it would have helped had you replied
> below
> my questions, with some context, rather than start effectively a new message.
Got it ! :-)
>> OK, so lets add --with-gmp and --with-zlib, both of which give increased
> performance.
+1
> On a rel
followup to my previous message...
I tried
sage -f ecl
sage -f maxima
That seemed to have finished without reporting an error. Only the last
two lines looked a bit strange.
installing Maxima library as /home/hemmecke/software/sage-source/local/
lib/ecl//maxima.fas
cp: cannot stat `maxima.fasb':
I've just run a sage -upgrade which complained that some .fas file was
not existing or too old.
;;; Internal error: Unable to find include directory
; - Binary file binary-ecl/maxima-package.fas is old or does not
exist.
;Compile (and load) source file
/home/hemmecke/software/sage-sou
On 06/23/10 07:02 AM, Nathann Cohen wrote:
Hello Dave !!!
I feel I can give bad answers to each of your question, as I may be at
fault for each of them :-)
Hi Nathan, just for future reference, it would have helped had you replied below
my questions, with some context, rather than start effec
On Tue, Jun 22, 2010 at 09:20:44PM -0700, William Stein wrote:
> Hi Willem (and Sage-devel),
>
> People have been reporting some weird "file not found" errors after
> doing "make test". This is caused by your #7793, I think. See
>
>http://trac.sagemath.org/sage_trac/ticket/9316
>
> for th
On Thu, Jun 3, 2010 at 1:11 PM, Jason B Hill wrote:
>
> Sorry, I was in the mountains for a bit and missed some conversation.
>
> Mike H: Do you want any assistance in your current task?
I have two patches up on the combinat patch server which add domains
to permutation groups.
The first is
htt
46 matches
Mail list logo
