Re: [sage-devel] VOTE: move Sage development to Github

[Benjamin Hackl]

+1 for GitHub.



> On 21.09.2022, at 19:23, David Roe  wrote:
> 
> Dear Sage developers,
> Following extensive discussion, both recently 
>  
> (prompted by issues upgrading the trac server) and over 
>  the 
>  last 
>  decade 
> , we are 
> calling a vote on switching Sage development from Trac 
>  to Github .  We've 
> created a summary of the pros and cons of each system 
> , a 
> description of the development model to be used on github 
> , and a 
> trac ticket  for coordinating work on 
> the transition.  More work will need to be done to carry out the actual 
> transition once voting is complete.
> 
> The voting will last until noon Eastern time (16:00 UTC) on Wednesday, 
> October 5.  Please use this thread only for sending votes, to make it easier 
> to count them afterward; there is a parallel thread where you can make 
> arguments in favor of either system.
> 
> Finally, I will close with a plea to be involved in this vote and discussion 
> even if you are not a core Sage developer.  By definition, core Sage 
> developers have become comfortable with trac, and I think that one of the 
> major arguments in favor of github is that it will help bring in new 
> contributors who are not familiar with Sage's development workfow 
> .  Anyone who has ever 
> contributed to the Sage code base or who maintains a Sage user package is 
> welcome to vote.
> David
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAChs6_%3DyvZ869L66E1tFmziWDirbawSEABf_uc_j9Dy8VBFW8w%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/227643AF-8739-4E0E-9B71-BA01EDCBB4DB%40benjamin-hackl.at.

[sage-devel] Symbolic equations and factor

[Benjamin Hackl]

I found some old code that seems to have broken due to a change of behavior 
when calling `factor()` on symbolic equations.

In the old version (can't really tie it to a specific SageMath version; 
maybe 2 years old or so), it would simply factor both sides of an equation, 
i.e., something along the lines of

sage: var('x y')
(x, y)
sage: (x^2 + 2*x + 1 == y^2 + y).factor()
(x + 1)^2 == (y + 1)*y

Currently, however,

sage: (x^2 + 2*x + 1 == y^2 + y).factor()
Traceback (most recent call last):
...
RuntimeError: can't happen in factor

Was this an intentional change at some point? (I did not find a specific 
ticket for it, so I am guessing that the answer is no.)
I liked that there was a convenience method for factoring both sides of an 
equation, and I used this quite a bit at some point; especially for 
improving output from `solve`.

Do you feel that the error is appropriate? (If so, the message needs to be 
improved, though.) Or would you be ok with changing back to factoring both 
sides when calling factor on a symbolic equation?

Benjamin

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1505691a-6b99-43cf-ac50-2d9b0a4ddcad%40googlegroups.com.

[sage-devel] Re: Evaluation of beta() in Sage 7.2

[Benjamin Hackl]

Did you test it for the negative input as well?

Unfortunately, I cannot compile anything after 7.2.beta6 on my machine, so 
I'm stuck with reading the code---but from what I read, numeric evaluation 
from beta in pynac calls numeric evaluation of lgamma in pynac, which in 
turn (correct me if I'm wrong) calls py_lgamma in pynac.pyx, which then 
just calls x.log_gamma(), without conversion to a complex argument. Then, 
the documented behavior (I did miss that, sorry) of log_gamma comes into 
play.

But of course, if everything works in 7.3.beta4, then there is no need to 
discuss or fix this any further. ;-)

Benjamin


Am Dienstag, 14. Juni 2016 10:28:04 UTC+2 schrieb Ralf Stephan:
>
> On Tuesday, June 14, 2016 at 10:18:01 AM UTC+2, Benjamin Hackl wrote:
>>
>> This seems to come from this (7.2.beta6):
>>
>> sage: (-0.9).log_gamma()
>> NaN
>>
>
> No, this is independent and even documented:
> To get evaluation of input for which gamma 
>is negative and the ceiling is even, we must 
>explicitly make the input complex.  This is 
>a known issue, see :trac:`12521`:: 
>
>sage: log_gamma(-2.1) 
>NaN 
>sage: log_gamma(CC(-2.1)) 
>1.53171380819509 + 3.14159265358979*I
>
> The beta() issue works in 7.3beta4 so where is the problem exactly?
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Evaluation of beta() in Sage 7.2

[Benjamin Hackl]

This seems to come from this (7.2.beta6):

sage: (-0.9).log_gamma()
NaN
sage: (-1.9).log_gamma()
1.71621928121964
sage: (-2.9).log_gamma()
NaN
sage: (-3.9).log_gamma()
-0.709468008908392
sage: (-4.9).log_gamma()
NaN
sage: (-5.9).log_gamma()
-4.07365556493664
sage: (-6.9).log_gamma()
NaN
sage: (-7.9).log_gamma()
-8.07203973601283

As far as I understand, pynac uses this for evaluating numerical arguments.



Am Dienstag, 14. Juni 2016 09:52:55 UTC+2 schrieb Kwankyu Lee:
>
>
> sage: x=-.9
>>
>> sage: y=.1
>>
>> sage: gamma(x)*gamma(y)/gamma(x+y)
>>
>> 17.5241239902668
>>
>> sage: beta(x,y)
>>
>> NaN
>>
>
> I get the same on Sage 7.3 beta3 on Mac.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: no trac mail notifications?

[Benjamin Hackl]

Our mail system alters the subject (probably since today; wasn't like that 
last Thursday) like this:

***EVENTUELL*SPAM*** [4.979 / 4] Re: [sage-trac]

Maybe this helps someone.

All the best,
Benjamin

Am Montag, 20. Juli 2015 19:21:15 UTC+2 schrieb Daniel Krenn:

 Am 2015-07-20 um 19:08 schrieb Benjamin Hackl: 
  ... might be just here at AAU. I found my notifications in the spam 
 folder. 

 I do not use the @aau.at address. 

 Could there have been changes in trac's mails so that some servers do 
 not accept the mails (or declare them as spam)? 



-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: no trac mail notifications?

[Benjamin Hackl]

... might be just here at AAU. I found my notifications in the spam folder.

Benjamin


Am Montag, 20. Juli 2015 18:00:29 UTC+2 schrieb Daniel Krenn:

 I do not get any trac mail notifications (about changes, etc.). Have 
 there been any changes to trac lately? 

 Best 

 Daniel 


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: residue produces incorrect results

[Benjamin Hackl]

Hi Ralf!

Well, no; I wasn't aware of the overview -- thanks for showing me. In 
principle, the wrong behavior of residue can be contributed to 
http://trac.sagemath.org/ticket/9555 -- except for the case where the 
singularity is not recognized, I guess. But that can be fixed in the ticket I 
opened.

Nevertheless, I believe that in order to fix the issue with series expansions 
at singular points (or at least to improve the current situation), the 
implementation in Pynac will have to be adopted. I'm actually quite tempted to 
play around a bit and see if I can make some improvements -- however, there are 
quite a lot of open tasks within my GSoC proposal, and until that project 
starts I'm rather busy with my master's thesis. (Of course, series expansions 
are an integral part of asypmptotic expressions; but everything in due time...)

In any case, as I need singular expansions for my research, I'll most likely 
work on it sooner or later anyhow. Thanks for your support!

Kind regards,
Benjamin

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Expression.series() = PowerSeriesRing(SR)?

[Benjamin Hackl]

I'm strongly in favor of returning an element of PowerSeriesRing -- within 
the current 
implementation, this happens:

sage: (1/(1+x)).series(x, 2) + (1/(1-x)).series(x, 2)
(1 + (-1)*x + Order(x^2)) + (1 + 1*x + Order(x^2))
sage: (1/(1-x)).series(x, 2) * (1/(1+x)).series(x)
(1 + (-1)*x + Order(x^2))*(1 + 1*x + Order(x^2))

Kind regards, Benjamin

Am Sonntag, 10. Mai 2015 09:10:04 UTC+2 schrieb Ralf Stephan:

 Instead of duplicating power series functionality (existing in rings/) in 
 Pynac,
 where there is momentarily only a skeleton implementation that does not 
 even
 play nice with the rest of symbolics, the series method of Expression
 should return an element of PowerSeriesRing(SR).

 I think this would be the right design, and now is the right time to at 
 least
 commit to this decision. So, what can be brought against it?

 http://trac.sagemath.org/ticket/18393



-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] residue produces incorrect results

[Benjamin Hackl]

Hi,

currently, there are some rather unwanted features with respect to the 
residue-function. For example:

sage: f(x) = 1/(x^2 - x - 1)
sage: f(1/2*sqrt(5) + 1/2)
4/((sqrt(5) + 1)^2 - 2*sqrt(5) - 6)

Now, as the pole obviously is not recognized because the radical expression 
is not 
simplified/expanded, also the series expansion (and thus the computation of 
the residue)
is wrong:

sage: f(x).series(x==1/2*sqrt(5) + 1/2, 1)
(4/((sqrt(5) + 1)^2 - 2*sqrt(5) - 6)) + Order(x - 1/2*sqrt(5) - 1/2)
sage: f(x).residue(x==1/2*sqrt(5) + 1/2)
0

This is http://trac.sagemath.org/ticket/18372 -- there I also proposed a 
possible fix for this particular
problem with residue (that is, the situation that the residue is incorrect 
if the singularity is not recognized
after substituting the argument). However, the problem with the series 
expansion remains.

Potentially, these cases could also be handled by substituting {x:x+a}, 
expanding/simplifying the 
resulting expression, letting Pynac expand aorund 0, and then substituting 
{x:x-a}. This approach 
yields

sage: f(x).subs({x:x+1/2*sqrt(5)+1/2}).expand().series(x==0, 
2).subs({x:x-1/2*sqrt(5)-1/2})
1/50*sqrt(5)*(2*x - sqrt(5) - 1) + 2/5*sqrt(5)/(2*x - sqrt(5) - 1) - 1/5

Unfortunately, I do not know how to preserve the Order(...)-term within 
this approach, that is why
I did not mention it on the ticket. 

But it doesn't end there. Take, for example, (gamma(x)^2).residue(x==0) ... 
[fixing this is harder
than the singularity above and would probably require attention from within 
Pynac itself.]

Does anyone have an opinion with respect to this issue? Should we think 
about a stopgap for
the residue -- or even for the series expansion? 

Kind regards,
Benjamin

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: GSoC 2015: 5 projects funded

[Benjamin Hackl]

Thank you very much for the opportunity! I'm looking forward to working on 
my project! :-)

Best wishes,
Benjamin


Am Montag, 27. April 2015 22:07:46 UTC+2 schrieb Harald Schilly:

 Hello students and welcome to SageMath! This years GSoC funds five 
 projects: 

 (Multivariate) Asymptotic Expressions 
 Benjamin Hackl and Daniel Krenn 

 http://www.google-melange.com/gsoc/project/details/google/gsoc2015/behackl/5649050225344512
  

 Performance Improvements for the Graph Module of Sagemath 
 Michele Bborassi and David Coudert 

 http://www.google-melange.com/gsoc/project/details/google/gsoc2015/borassi/5685265389584384
  

 Connectivity and optimization algorithms in matroids 
 Chao Xu and Stefan van Zwam, Michael Welsh 

 http://www.google-melange.com/gsoc/project/details/google/gsoc2015/mgccl/5676830073815040
  

 SageMathCloud personal version 
 Jonathan Lee and William Stein 

 http://www.google-melange.com/gsoc/project/details/google/gsoc2015/jlee27/5668600916475904
  

 Extending Game Theory in Sage 
 Tobenna Peter Igwe and Vince Knight, Dima Pasechnik 

 http://www.google-melange.com/gsoc/project/details/google/gsoc2015/ptigwe/5693417237512192
  

 -- Harald 


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: doctest failure in dyck_word.py

[Benjamin Hackl]

I had a discussion regarding the use of python integers some time ago with 
Daniel Krenn. 

Basically, range and xrange produce Python integers, whereas srange and 
sxrange (from sage.misc.misc) produce
Integers. Also, when dealing with lists, len usually produces Python int's. 
(Maybe Daniel has some more common
pitfalls?)

In any case, after trying to change all range and xrange to srange and 
sxrange in dyck_word.py, the error
still occurred. It seems that directly after building sage, something 
happens such that the parameters 4,2 in the doctest

sage: TestSuite(DyckWords(4,2)).run()

are being treated as Python integers, rather than sage integers. Then, when 
the TestSuite comes to the test where
it checks that cardinality actually returns an Integer, it fails because 
the Python int's 4 and 2 cause the cardinality
to be a Python int, too.

Vincent has cured the symptom of these mysteriously occurring int's 
in http://trac.sagemath.org/ticket/18244 -- but the
nature of the original problem (i.e. that there are Python int's in the 
first place only with ./sage -bt and *not* with
./sage -t -- and this also not on all platforms) suggests that this might 
be something that runs deep.


Am Samstag, 18. April 2015 05:54:29 UTC+2 schrieb Darij Grinberg:

 This stuff is spooky... I've always been treating int and Integer as 
 interchangeable when coding for Sage. Maybe I've introduced several such 
 bugs.

 Can anyone explain in a noob-friendly way how an implementer should decide 
 between returning ints and Integers, when it is OK to treat them as 
 equivalent, and in what cases an explicit conversion into Integer needs to 
 be made? Thanks a lot!


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: doctest failure in dyck_word.py

[Benjamin Hackl]

Hi Vincent,

well, at least I'm not the only one. For now, I don't really have a clue 
regarding where this could come from.
I'm still compiling a clean version of 6.7.beta1, but now I guess that 
won't change much.

The circumstance that this error only seems to appear after a series of 
doctests (I suppose you ran make 
ptestlong too?) confuses me. Could this point towards something like 
caching or memory leak?

Benjamin


Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix:

 Hello, 

 It seems that I am not the only one to have troubles with Dyck words... 

 sage -t --long --warn-long 81.8 src/sage/combinat/dyck_word.py 
 ** 
 File src/sage/combinat/dyck_word.py, line 3501, in 
 sage.combinat.dyck_word.DyckWords_size.__init__ 
 Failed example: 
   TestSuite(DyckWords(4,2)).run() 
 Expected nothing 
 Got: 
   ... 
   tester.assert_(isinstance(card, Integer)) 
   ... 
    
   The following tests failed: _test_enumerated_set_iter_cardinality 
 ** 
 1 item had failures: 

 It occurs several time on my computer (and at least one on Benjamin 
 Hackl's). See 

  http://trac.sagemath.org/ticket/16352#comment:18 
  http://trac.sagemath.org/ticket/18237#comment:4 

 Vincent 


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: doctest failure in dyck_word.py

[Benjamin Hackl]

Strange. I'm also trying to find out what triggers the error, no success 
yet.

Jan Keitel also encountered this error 
(http://trac.sagemath.org/ticket/18237#comment:6) 
-- and I'm sure
that there are others with the same problem.

Benjamin

Am Freitag, 17. April 2015 21:17:10 UTC+2 schrieb vdelecroix:

 Hello Benjamin, 

 Indeed, it was after a make ptestlong or something similar. And it 
 reproduced on both sage-6.7.beta0 and sage-6.7.beta1. 

 The error is very strange since it corresponds to a test of some return 
 type. I will try to get something more verbose. And there is no caching 
 involved as far as I can tell... 

 Vincent 

 On 17/04/15 19:48, Benjamin Hackl wrote: 
  Hi Vincent, 
  
  well, at least I'm not the only one. For now, I don't really have a clue 
  regarding where this could come from. 
  I'm still compiling a clean version of 6.7.beta1, but now I guess that 
  won't change much. 
  
  The circumstance that this error only seems to appear after a series of 
  doctests (I suppose you ran make 
  ptestlong too?) confuses me. Could this point towards something like 
  caching or memory leak? 
  
  Benjamin 
  
  
  Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix: 
  
  Hello, 
  
  It seems that I am not the only one to have troubles with Dyck words... 
  
  sage -t --long --warn-long 81.8 src/sage/combinat/dyck_word.py 
  ** 
  File src/sage/combinat/dyck_word.py, line 3501, in 
  sage.combinat.dyck_word.DyckWords_size.__init__ 
  Failed example: 
 TestSuite(DyckWords(4,2)).run() 
  Expected nothing 
  Got: 
 ... 
 tester.assert_(isinstance(card, Integer)) 
 ... 
  
 The following tests failed: 
 _test_enumerated_set_iter_cardinality 
  ** 
  1 item had failures: 
  
  It occurs several time on my computer (and at least one on Benjamin 
  Hackl's). See 
  
http://trac.sagemath.org/ticket/16352#comment:18 
http://trac.sagemath.org/ticket/18237#comment:4 
  
  Vincent 
  
  


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: doctest failure in dyck_word.py

[Benjamin Hackl]

Vincent, did you also upgrade to 6.7.beta0 or 6.7.beta1 from a previous 
version?

I just finished building 6.7.beta1 after make distclean, and this time I 
can't reproduce the error. 
Unfortunately, this doesn't really explain what happened earlier, and there 
is still the possibilty that
the error is random.

I will continue to investigate this by running ptestlong a few more times; 
if I find something out of the
ordinary I'll report back here.

Benjamin

Am Freitag, 17. April 2015 21:38:18 UTC+2 schrieb Benjamin Hackl:

 Strange. I'm also trying to find out what triggers the error, no success 
 yet.

 Jan Keitel also encountered this error (
 http://trac.sagemath.org/ticket/18237#comment:6) -- and I'm sure
 that there are others with the same problem.

 Benjamin

 Am Freitag, 17. April 2015 21:17:10 UTC+2 schrieb vdelecroix:

 Hello Benjamin, 

 Indeed, it was after a make ptestlong or something similar. And it 
 reproduced on both sage-6.7.beta0 and sage-6.7.beta1. 

 The error is very strange since it corresponds to a test of some return 
 type. I will try to get something more verbose. And there is no caching 
 involved as far as I can tell... 

 Vincent 

 On 17/04/15 19:48, Benjamin Hackl wrote: 
  Hi Vincent, 
  
  well, at least I'm not the only one. For now, I don't really have a 
 clue 
  regarding where this could come from. 
  I'm still compiling a clean version of 6.7.beta1, but now I guess that 
  won't change much. 
  
  The circumstance that this error only seems to appear after a series of 
  doctests (I suppose you ran make 
  ptestlong too?) confuses me. Could this point towards something like 
  caching or memory leak? 
  
  Benjamin 
  
  
  Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix: 
  
  Hello, 
  
  It seems that I am not the only one to have troubles with Dyck 
 words... 
  
  sage -t --long --warn-long 81.8 src/sage/combinat/dyck_word.py 
  ** 
  File src/sage/combinat/dyck_word.py, line 3501, in 
  sage.combinat.dyck_word.DyckWords_size.__init__ 
  Failed example: 
 TestSuite(DyckWords(4,2)).run() 
  Expected nothing 
  Got: 
 ... 
 tester.assert_(isinstance(card, Integer)) 
 ... 
  
 The following tests failed: 
 _test_enumerated_set_iter_cardinality 
  ** 
  1 item had failures: 
  
  It occurs several time on my computer (and at least one on Benjamin 
  Hackl's). See 
  
http://trac.sagemath.org/ticket/16352#comment:18 
http://trac.sagemath.org/ticket/18237#comment:4 
  
  Vincent 
  
  



-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: doctest failure in dyck_word.py

[Benjamin Hackl]

I take everything back; I have no idea how I passed make ptestlong 
earlier -- but 
the failure is still very much here. I think it can be triggered somewhat 
reliably with

./sage -bt src/sage/combinat/dyck_word.py

while at the same time

./sage -t src/sage/combinat/dyck_word.py

passes without error. This is really strange.

Benjamin

Am Samstag, 18. April 2015 00:13:59 UTC+2 schrieb vdelecroix:

 At least I opened #18244... 

 On 18/04/15 00:02, Benjamin Hackl wrote: 
  Vincent, did you also upgrade to 6.7.beta0 or 6.7.beta1 from a previous 
  version? 
  
  I just finished building 6.7.beta1 after make distclean, and this time 
 I 
  can't reproduce the error. 
  Unfortunately, this doesn't really explain what happened earlier, and 
 there 
  is still the possibilty that 
  the error is random. 
  
  I will continue to investigate this by running ptestlong a few more 
 times; 
  if I find something out of the 
  ordinary I'll report back here. 
  
  Benjamin 
  
  Am Freitag, 17. April 2015 21:38:18 UTC+2 schrieb Benjamin Hackl: 
  
  Strange. I'm also trying to find out what triggers the error, no 
 success 
  yet. 
  
  Jan Keitel also encountered this error ( 
  http://trac.sagemath.org/ticket/18237#comment:6) -- and I'm sure 
  that there are others with the same problem. 
  
  Benjamin 
  
  Am Freitag, 17. April 2015 21:17:10 UTC+2 schrieb vdelecroix: 
  
  Hello Benjamin, 
  
  Indeed, it was after a make ptestlong or something similar. And it 
  reproduced on both sage-6.7.beta0 and sage-6.7.beta1. 
  
  The error is very strange since it corresponds to a test of some 
 return 
  type. I will try to get something more verbose. And there is no 
 caching 
  involved as far as I can tell... 
  
  Vincent 
  
  On 17/04/15 19:48, Benjamin Hackl wrote: 
  Hi Vincent, 
  
  well, at least I'm not the only one. For now, I don't really have a 
  clue 
  regarding where this could come from. 
  I'm still compiling a clean version of 6.7.beta1, but now I guess 
 that 
  won't change much. 
  
  The circumstance that this error only seems to appear after a series 
 of 
  doctests (I suppose you ran make 
  ptestlong too?) confuses me. Could this point towards something like 
  caching or memory leak? 
  
  Benjamin 
  
  
  Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix: 
  
  Hello, 
  
  It seems that I am not the only one to have troubles with Dyck 
  words... 
  
  sage -t --long --warn-long 81.8 src/sage/combinat/dyck_word.py 
  
 ** 
  File src/sage/combinat/dyck_word.py, line 3501, in 
  sage.combinat.dyck_word.DyckWords_size.__init__ 
  Failed example: 
  TestSuite(DyckWords(4,2)).run() 
  Expected nothing 
  Got: 
  ... 
  tester.assert_(isinstance(card, Integer)) 
  ... 
   
  The following tests failed: 
  _test_enumerated_set_iter_cardinality 
  
 ** 
  1 item had failures: 
  
  It occurs several time on my computer (and at least one on Benjamin 
  Hackl's). See 
  
 http://trac.sagemath.org/ticket/16352#comment:18 
 http://trac.sagemath.org/ticket/18237#comment:4 
  
  Vincent 
  
  
  
  
  


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] #15846 + testing local changes to upstream-packages?

[Benjamin Hackl]

Hello everybody,

today I had a look at http://trac.sagemath.org/ticket/15846 and I think I 
may have tracked down the issue to SymPy (details in the comments of the 
ticket).
Assuming what I found actually is the problem, I'm not quite sure how to 
proceed from there (i.e. reporting the issue upstream to SymPy etc.). Could 
someone help me with that?

Also, is there a way to test how changes to, say, 
local/lib/python/site-packages/sympy/functions/special/zeta_functions.py 
affect my sage installation?

Thanks!

Kind regards,
Benjamin

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] #15846 + testing local changes to upstream-packages?

[Benjamin Hackl]

... turns out that not only SymPy, but also GiNaC has a problem when 
expanding zeta around 1. However, it is more likely for the error to come 
from GiNaC -- so I'll do some more investigations, and then report the 
issue there as well.

In any case, thanks for help!

Best wishes,
Benjamin

Am Dienstag, 7. April 2015 18:26:09 UTC+2 schrieb vdelecroix:

 Hello, 

 On 07/04/2015, Benjamin Hackl benjami...@aau.at javascript: wrote: 
  Hello everybody, 
  
  today I had a look at http://trac.sagemath.org/ticket/15846 and I think 
 I 
  may have tracked down the issue to SymPy (details in the comments of the 
  ticket). 
  Assuming what I found actually is the problem, I'm not quite sure how to 
  proceed from there (i.e. reporting the issue upstream to SymPy etc.). 
 Could 
  
  someone help me with that? 

 As far as I know, sympy works with github and you can provide pull 
 requests. This is what has been done in #18085. 

  Also, is there a way to test how changes to, say, 
  local/lib/python/site-packages/sympy/functions/special/zeta_functions.py 
  affect my sage installation? 

 As soon as you changed it, just restart sage and you get the new sympy 
 version when doing import sympy. 
 The more Sagish way to do it is to provide a tarball and modify the 
 install scripts in $SAGE_ROOT/build/pkgs/sympy/ accordingly. You can 
 also have a look in the developer guide 
 http://sagemath.org/doc/developer/packaging.html 

 Vincent 


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Asymptotic Expressions in Sage

[Benjamin Hackl]

Hello everyone!

I just wanted to let you know -- as suggested 
in https://groups.google.com/forum/#!topic/sage-devel/uR_bv7PrZpk -- that 
Clemens Heuberger, Daniel Krenn, and myself are currently working on 
improving the situation of asymptotic expressions in Sage. In order to do 
so, we have created some tickets, all of which can be found at the 
respective meta-ticket (#17601, http://trac.sagemath.org/ticket/17601). 
This ticket also contains the basic structure for our implementation.

Several question (and answers) which came up during a discussion of the 
data structure we want to use can be found in the comments of the 
respective ticket (#17693, http://trac.sagemath.org/ticket/17693), and in 
the description of the ticket belonging to our AsymptoticExpression-class 
(#17716, http://trac.sagemath.org/ticket/17716).

Let us know if you have an opinion about this, we would be happy to 
exchange some thoughts or explain our plan in more detail! :-)

Kind regards,
Benjamin

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] What are we unable to do right now ?

[Benjamin Hackl]

Am Freitag, 5. Dezember 2014 16:31:33 UTC+1 schrieb Martin R:

 3) asymptotics.


Hello everyone!

I just wanted to let everyone know that Clemens Heuberger, Daniel Krenn, 
and myself are currently working on improving the situation of asymptotic 
expressions in Sage. Ticket #17601 (http://trac.sagemath.org/ticket/17601) 
contains the basic structure for our implementation, and some questions 
(which came up during a discussion via mail with Nathann) regarding the 
data structure we want to use are illustrated withinin the comments of the 
respective ticket (#17716, http://trac.sagemath.org/ticket/17693).

Let us know if you have an opinion about this, we would be happy to 
exchange some thoughts or explain our plan in more detail! :-)

Benjamin


PS: sorry for digging out this old thread, but making a new one seemed to 
be sort of an overkill. 

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.