Hi John,
On 2012-09-20, John H Palmieri wrote:
> Or ask.sagemath.org (not ideal for reporting bugs, but still).
I for one hardly ever look at ask.sagemath.org (perhaps once
every two months). If a sufficiently large proportion of sage
developers does the same then certainly it is a very bad plac
On Thursday, 20 September 2012 12:34:00 UTC+8, John H Palmieri wrote:
>
>
>
> On Wednesday, September 19, 2012 9:14:41 PM UTC-7, jason wrote:
>>
>> On 9/19/12 11:10 PM, Dima Pasechnik wrote:
>> > This seems to be a googlegroups problem, and something only Google can
>> > fix (or break).
>> > P
On Thursday, 20 September 2012 12:14:41 UTC+8, jason wrote:
>
> On 9/19/12 11:10 PM, Dima Pasechnik wrote:
> > This seems to be a googlegroups problem, and something only Google can
> > fix (or break).
> > Perhaps we indeed need a "real" issue tracker.
> > What about using github for this?
>
Hi, Nils:
Thanks for reply. IMHO, for many physical problems, we just want to know
principal value. As you mentioned, we can use other definition to void this
issue. However, for more complicated formula, it is hard find the healthy
definition. I think it could be better if either (1) sage pro
On Wednesday, September 19, 2012 9:14:41 PM UTC-7, jason wrote:
>
> On 9/19/12 11:10 PM, Dima Pasechnik wrote:
> > This seems to be a googlegroups problem, and something only Google can
> > fix (or break).
> > Perhaps we indeed need a "real" issue tracker.
> > What about using github for this
On 9/19/12 11:10 PM, Dima Pasechnik wrote:
This seems to be a googlegroups problem, and something only Google can
fix (or break).
Perhaps we indeed need a "real" issue tracker.
What about using github for this?
What's wrong with using trac? Or even Harald's google spreadsheet form?
Jason
This seems to be a googlegroups problem, and something only Google can fix
(or break).
Perhaps we indeed need a "real" issue tracker.
What about using github for this?
On Thursday, 20 September 2012 06:16:19 UTC+8, Nathann Cohen wrote:
>
> ---
> Don't take it personally, but sage's bug reporting
On Wednesday, September 19, 2012 1:52:24 PM UTC-7, Robert Bradshaw wrote:
> There is the issue that norm(v) does not always (often?) live in v for
> exact v. Dropping to SR can be really slow, as can dropping to
> QQ[sqrt(norm(v))], especially if several vectors are normalized then
> used toget
---
Don't take it personally, but sage's bug reporting system on
googlegroups totally sucks in my opinion -- it is the worst open
source bug reporting systems i have seen.
Tried to sent 2 mails to sage-support (one was strange/counterintuitive
behavior, the
other was a clear bug). The emails didn
Hello everybody !!
I just received this comment by email, and somehow I think that its place
is on this forum :
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubsc
On Wed, Sep 19, 2012 at 2:02 PM, Jason Grout
wrote:
> On 9/19/12 3:51 PM, Robert Bradshaw wrote:
>>
>> Even better if we can avoid re-using the name.
>
>
> So you mean permanently deprecating .normalize? Or do you mean leaving
> .normalize() and also having .normal_form() and .normalization()? O
On 9/19/12 3:51 PM, Robert Bradshaw wrote:
Even better if we can avoid re-using the name.
So you mean permanently deprecating .normalize? Or do you mean leaving
.normalize() and also having .normal_form() and .normalization()? Or do
you mean something different?
This is similar to .kernel
On Wed, Sep 19, 2012 at 1:39 PM, Jason Grout
wrote:
> On 9/19/12 2:09 PM, Volker Braun wrote:
>>
>> +1 to:
>>
>> * rename v.normalization() -> v.normal_form() unless somebody has a
>> better name
>> * replace v.normalization() with he usual division by L2-norm.
>>
>
> +1, except I think it's v.nor
On 9/19/12 2:09 PM, Volker Braun wrote:
+1 to:
* rename v.normalization() -> v.normal_form() unless somebody has a
better name
* replace v.normalization() with he usual division by L2-norm.
+1, except I think it's v.normalize(), not v.normalization().
Thanks,
Jason
--
You received this
You need to
sudo yum install libffi-devel
and then restart the computation (make distclean && make)
On Wednesday, September 19, 2012 9:10:54 PM UTC+1, Aleksey Rukhlenko wrote:
>
> Greetings, dear colleagues.
>
> I failed to compile Sage-5.3 on OpenSuse 12.2 (gcc 4.7.1) 64 bit.
>
> Before i
On Wednesday, September 19, 2012 8:50:17 PM UTC+1, Robert Bradshaw wrote:
> would we have a period where it gives a warning
>
I think the deprecation warnings should be a help to the user and not a
sacrifice to the gods of backwards compatibility. If the method name
changed and is now something
Greetings, dear colleagues.
I failed to compile Sage-5.3 on OpenSuse 12.2 (gcc 4.7.1) 64 bit.
Before installation I entered:
./sage -i patch
./sage -i openssl
Part of installation log with errror:
;;; gcc -I.
-I/home/aleksey/temp/sage-5.3/spkg/build/ecl-11.1.2.cvs2020.p1/src/build/
-I/h
+1, though it's difficult to change the meaning of an existing
function (would we have a period where it gives a warning?).
On Wed, Sep 19, 2012 at 12:09 PM, Volker Braun wrote:
> +1 to:
>
> * rename v.normalization() -> v.normal_form() unless somebody has a better
> name
> * replace v.normalizat
On Wednesday, September 19, 2012 3:09:34 PM UTC-4, Volker Braun wrote:
>
> +1 to:
>
> * rename v.normalization() -> v.normal_form() unless somebody has a better
> name
> * replace v.normalization() with he usual division by L2-norm.
>
And perhaps have a warning to be printed for the next 12 mon
+1 to:
* rename v.normalization() -> v.normal_form() unless somebody has a better
name
* replace v.normalization() with he usual division by L2-norm.
You can't deprecate the change gradually, but sometimes things have to
change to improve.
On Wednesday, September 19, 2012 7:55:24 PM UTC+1, C
It was pointed out to me that vector normalization in Sage is not doing what
most people would think it should do. Rather than divide by the norm of the
vector, right now the implementation is to divide the vector by the first
non-zero part. This was pointed out to me by someone who teaches unde
Hello Martin,
First of all, thank you very much for answering.
I solved my problem, inspecting the C codes generated by two versions of
Sage, when calling 'eval'.
It is now sufficient (and seemingly necessary), to pass the dictionary
returned by the 'globals ()' function to eval, in compiled func
I have set up a sage server with several users. The "forgot password"
option worked all right, but after upgrading to sage 5.2, it doesn't
work anymore.
When i click on "forgot password" and enter a username, i get the
message "username is invalid". But the username is accepted to login.
Any clue
Hi all,
I report my experience on installing sage-5.3 on CentOS-6.3:
# Problem #1: Missing some libraries
# Solution
yum groupinstall 'Development Tools'
yum install openssl-devel
# Problem 2: error on compiling GMP-ECM
# Solution
export LDFLAGS="-lm" before issuing make
# Inspiration:
https://
24 matches
Mail list logo
