Hi,
Currently there is an option repr for the finite field constructor.
For small finite fields, it can take log, which makes finite field
elements printed as a discrete log with base the primitive generator.
So a^14 is printed as 14
It would be very convenient if repr can take power such that
On Jul 8, 12:20 pm, John H Palmieri jhpalmier...@gmail.com wrote:
I'm not sure which finite field constructor you're looking at. In
rings/finite_rings/finite_field_givaro.py, the repr option is
described this way:
repr -- controls the way elements are printed to the
user:
This is now trac #9377.
Thank you.
sage-support is a better place to report bugs.
sage-devel is for discussions about development.
Mariah
I see.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Hi,
On Sage 4.4.4, I have the following bug.
sage: F.a=GF(4)
sage: m=matrix(2,[F(1),2,3,4])
sage: magma(m)
---
TypeError Traceback (most recent call
last)
...
TypeError: unable to coerce
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
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
A related comment:
I like the method name variables for symbolic expressions. On the
other hand, I think the name variable should be avoided in the exact
polynomial rings cases, as in
sage: P.x,y=PolynomialRing(QQ)
sage: P.variable_names()
('x', 'y')
In this case, gen_names() is perhaps
Hi
While I am working on a small patch to a file in sage/gsl/ for the
ticket
http://trac.sagemath.org/sage_trac/ticket/9080
I am wondering why the gsl directory occupy the top-level place in the
Sage library. I suppose that the top-level directories represent big
themes, but gsl is just a
this happen? Why I get a different result in
doctesting? I seek of your expertise. Thank you in advance.
Kwankyu Lee
--
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
Hi Leif,
This doctest failure did not occur without applying my own patch, so I
thought my patch was the cause. A weird bug indeed...
Thank you for the pointers.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Added information to the ticket http://trac.sagemath.org/sage_trac/ticket/9003
Kwankyu Lee
--
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 this group at http
Hi,
No objection. But you need to provide deprecation warnings before
removing any long used things in Sage.
Kwankyu
--
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
Hi,
In Mac OS, latest Magma v2.16-6 fails to load under Sage 4.3.3, with
the following error message:
sage: magma_console()
dyld: Library not loaded: @executable_path/libgmp.3.dylib
Referenced from: /Applications/Magma/bin/magma.exe
Reason: Incompatible library version: magma.exe requires
Hi,
There is no problem on the command line:
sage: r\use
'\\use'
But in the notebook of Sage 4.3.3, the same input produces
Traceback (most recent call last):
File stdin, line 1, in module
File _sage_input_37.py, line 9, in module
open(___code___.py,w).write(# -*- coding: utf-8 -*-\n +
Hi,
I want to raise this issue again.
sage: P.x,y = PolynomialRing(QQ,2)
sage: f = 2*x*y+x+y
sage: f.coefficient({x:1,y:1})
2
sage: c = f.coefficient({x:1,y:1})
sage: c.parent()
Multivariate Polynomial Ring in x, y over Rational Field
sage: c = f.monomial_coefficient(x*y)
sage: c.parent()
Thank you. The article reveals human sides of the origin of the
inhumanly marvelous Sage project and its originator. Quite moving.
Kwankyu
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
As East Asian countries, please include Korea along side with China
and Japan.
Thank you!
--
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 this group at
Hi Harald,
On Nov 19, 12:59 am, Harald Schilly harald.schi...@gmail.com wrote:
They are meant to be included by the dots. It's just for a rough
estimate where you are, nothing specific.
I know. :-)
This survey is nice. Thank you for your work.
Kwankyu
--
To post to this group, send an
On Nov 15, 3:56 am, William Stein wst...@gmail.com wrote:
On Thu, Nov 12, 2009 at 11:43 PM, Kwankyu Lee ekwan...@gmail.com wrote:
Hi,
Is this an expected behavior of the magma interface?
--
| Sage Version 4.2
Hi,
What is the standard way to get a reference to a magma object in Sage?
Is it m._ref() or m.name()? What is their difference?
Kwankyu
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
Hi,
Is this an expected behavior of the magma interface?
--
| Sage Version 4.2, Release Date: 2009-10-24 |
| Type notebook() for the GUI, and license() for information.|
Hi,
I am experiencing the problem exactly that David raised
Then it seems the original idea is good that we add tag (or flag?,
I don't like component as Robert proposed) parameter to verbose
commands. It will default to internal (or system or library or
builtin?) This will not break or change
Hi,
verbose() may be quite useful for user programs, but it seems right
now only oriented for developers. If I place some verbose(...,
level=1) statements in my Sage program, and the verbose level is set
to 1 by set_verbose(1), then the verbose statements of internal Sage
functions are printed,
Oh... I missed the parameter files of set_verbose(). The parameter
already fulfills my wish as in
set_verbose(1,files=myprogram.py)
Sorry for noise...
Kwankyu
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To
Hi,
To get the names of generators of a polynomial ring R, I may use
R.variable_names().
But it seems that the method at least does not fail for other rings.
For example,
sage: GF(2).variable_names()
('x',)
What is the intention? If variable_names() intends to return the names
of generators,
I think generator_names() is a universal name for all structures,
and variable_names should be an alias of that only for polynomial
rings.
I understand William's concerns, but I think there should an official
mechanism to change an inappropriate nomination with what makes sense
as soon as it is
Hi,
The following scares me.
sage: 0^0
1
sage: F.a=GF(5)
sage: F(0)^0
Traceback (most recent call last):
...
ArithmeticError: 0^0 is undefined.
For any x, x^0 is 1 by definition. Isn't it in Sage? I am using Sage
4.1.2
Kwankyu
--~--~-~--~~~---~--~~
To post to
Hi,
sage: A=matrix(2,[1,2,3,3])
sage: A.solve_right(vector([3,6]))
(1, 1)
sage: category(_)
Category of elements of Vector space of dimension 2 over Rational
Field
sage: A.solve_left(vector([3,6]))
[3 0]
sage: category(_)
Category of elements of Full MatrixSpace of 1 by 2 dense matrices over
On Oct 23, 12:11 am, John H Palmieri jhpalmier...@gmail.com wrote:
On Oct 22, 1:25 am, Kwankyu Lee ekwan...@gmail.com wrote:
Hi,
The following scares me.
sage: 0^0
1
sage: F.a=GF(5)
sage: F(0)^0
Traceback (most recent call last):
...
ArithmeticError: 0^0 is undefined
I hope some expert confirm that this is a bug or merely my
misunderstanding.
Kwankyu
--~--~-~--~~~---~--~~
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
701 - 730 of 730 matches
Mail list logo
