Re: [sage-devel] message to patchbot breeders

[Dima Pasechnik]

On Wednesday, 15 April 2015 21:55:34 UTC+1, Frédéric Chapoton wrote:
>
> Hello,
>
> As I have said before, I have no machine other than my laptop, so I only 
> test the patchbot on my own sage installation on that laptop.
>

Should we find a machine for you to run patchbot, if your university is too 
poor?
 

> This means that I test it interactively inside an Ipython Session, and 
> only in plugin_only mode, so that it will not run too long and destroy my 
> sage installation (I hate ATLAS recompilation)
> This was working when I proposed the 2.3.3 version. But of course I missed 
> that the compilation step would go astray, because I do not use sage 
> -patchbot
> I am sorry if this causes some inconvenience. I try to do my best to 
> enhance the patchbot, because I care that it works,
> but maybe I am not competent enough. In the lack of a more qualified 
> person, nevertheless...
>
> Frederic
>
> Le mercredi 15 avril 2015 21:28:54 UTC+2, Jeroen Demeyer a écrit :
>>
>> On 2015-04-15 17:41, Frédéric Chapoton wrote:
>> > oops ! Thanks a lot. I was not sure which one of the two lines must 
>> > really be first, so I choose the utf8 one.. 
>>
>> Obvious question: do you actually try the patchbot yourself before 
>> making a new public package? 
>>
>>

-- 
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: Race condition when closing tickets

[Clemens Heuberger]

Out of my previous list, there were some false positives (I somehow mishandled
invalid tickets). Five incompletely merged tickets remained.

Am 2015-04-16 um 07:20 schrieb Clemens Heuberger:
> ticket commit   changed
> 15017 872e2bc0225b6929ed8cc052a63850c892abe723 07/21/14 03:51:36

opened #18218 with the missing commit.

> 17307 7fa0de34aa713520d0fef2a7065581599dfd7bf3 11/09/14 20:40:11

Last commit was an amend changing the author of the commit, this is now 
unfixable.

> 14880 3b6a841dc5f6210a9c0d70b4d6cf24e34788c228 10/02/13 08:35:34

I do not understand that one, was merged in 5.13.beta0

> 15599 08be4423f7703847d4da7c6d8cce4bb0902f93ed 03/13/14 04:38:46

only a merge commit missing, therefore no new ticket.

> 16847 e42ce551e66ff3f854c2424561bc71a075bac67a 08/19/14 12:38:59

opened #18219 with the missing commit.

Both #18218 and #18219 are trivial. I used the authors of the missing authors
for trac's author field and set them to needs_review.

Regards, CH


-- 
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] Broken options of show() in Sage 6.6

[Eric Gourgoulhon]

Hi,

In Sage 6.6, it seems that the options passed to show() for displaying a 3D 
object are not taken into account:

sage: show(sphere(), figsize=10, frame=False, aspect_ratio=(1,1,0.5))

gives the same output as a mere show(sphere()).
 
This issue occurs both with the default viewer (Jmol) as with Tachyon. For 
a 2D object, there is no problem. 

For Sage 6.5, it was OK. 
For Sage 6.6.beta5, the problem was already there (but I've noticed it only 
today, sorry...).

Eric.

-- 
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] installation of optional spkg's on binary Sage releases

[Dima Pasechnik]

It seems to me that binary distributions are not guaranteed to be able to 
build some optional packages.
There were numerous reports on sage-support, and here is another example:
http://trac.sagemath.org/ticket/18198

However, reading http://sagemath.org/doc/installation/quick-guide.html
gives you a false impression to this effect.

Should the text in this link be adjusted to tell people to use source 
distros?

Dima

-- 
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] installation of optional spkg's on binary Sage releases

[William Stein]

On Thu, Apr 16, 2015 at 9:49 AM, Dima Pasechnik  wrote:
> It seems to me that binary distributions are not guaranteed to be able to
> build some optional packages.

Side question -- Is anything guaranteed to build all optional
packages?   What's the current status of testing them?  I keep raising
this issue...

> There were numerous reports on sage-support, and here is another example:
> http://trac.sagemath.org/ticket/18198
>
> However, reading http://sagemath.org/doc/installation/quick-guide.html
> gives you a false impression to this effect.
>
> Should the text in this link be adjusted to tell people to use source
> distros?
>
> Dima
>
> --
> 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.



-- 
William (http://wstein.org)

-- 
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: Race condition when closing tickets

[kcrisman]

 

>
> On Thursday, April 16, 2015 at 7:58:32 AM UTC+2, Jeroen Demeyer wrote:
>>
>> On 2015-04-16 01:33, Nils Bruin wrote: 
>> > The whole meaning of "positive review" goes out of 
>> > the window if one still changes the branch on the ticket. 
>> I disagree. It can easily happen that a problem is found after a ticket 
>> was set to positive_review. Perhaps some corner case doesn't quite work. 
>> Or there could be trivial changes like a documentation typo. 
>>
>>

Then open a new ticket. Which is exactly what you would do if the ticket 
> has been switched to closed, so why is it impossible to do when it is 
> positive_review?
>
>
 Because of the social problem that people probably won't fix it, or at 
least not by the next stable release (surely not all such tickets would 
become blockers).  Then we'll have (for instance) some new behavior in Sage 
with an annoying bug that it totally reproducible but not taken care of, 
instead of just not having that in Sage at all, buggy or no.

That said, now that I see part of the problem is not just people changing 
tickets, but changing *branches* and *keeping* positive review (or 
something analogous to this), I agree that is a different situation.  So, 
here's my possibly buggy suggestion:

* If you actually HAVE a solution to the problem you see in a positive 
review ticket, then open a new ticket and put it there.
* If not, undo positive review and put to "needs work" and presumably it 
won't get fixed fast enough to matter.  Or if someone gets a fix, they 
could put it on a new ticket.  (?)

-- 
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] installation of optional spkg's on binary Sage releases

[Dima Pasechnik]

On Thursday, 16 April 2015 18:12:16 UTC+1, William wrote:
>
> On Thu, Apr 16, 2015 at 9:49 AM, Dima Pasechnik  > wrote: 
> > It seems to me that binary distributions are not guaranteed to be able 
> to 
> > build some optional packages. 
>
> Side question -- Is anything guaranteed to build all optional 
> packages?   What's the current status of testing them?  I keep raising 
> this issue... 
>

some optional packages are maintained, and tested by maintainers (and/or 
other users) 
on a regular basis. But this is ad hoc, surely. And some are obsolete, like 
gcc 4.6.4 one.

Should we dedicate few patchbots to test optional packages?
 

>
> > There were numerous reports on sage-support, and here is another 
> example: 
> > http://trac.sagemath.org/ticket/18198 
> > 
> > However, reading http://sagemath.org/doc/installation/quick-guide.html 
> > gives you a false impression to this effect. 
> > 
> > Should the text in this link be adjusted to tell people to use source 
> > distros? 
> > 
> > Dima 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at http://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>
> -- 
> William (http://wstein.org) 
>

-- 
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: Race condition when closing tickets

[Clemens Heuberger]

Am 2015-04-16 um 19:28 schrieb kcrisman:
> That said, now that I see part of the problem is not just people changing
> tickets, but changing *branches* and *keeping* positive review (or something
> analogous to this), I agree that is a different situation.  So, here's my
> possibly buggy suggestion:

technically, they do not *keep* positive review. They set it to needs_work,
needs_review, somebody reviews it, sets it to positive_review. So the ticket
went through a full cycle, but the earlier version is merged. And those tickets
where this actually happened were usually very minor issues (where the authors
presumably had the impression that opening an extra ticket is overkill).

The whole discussion was about the semantics of "positive_review". In the
release managers workflow, is actually closer to "closed" than I previously
assumed, but all other proposal essentially boiled down to introducing one more
status of a ticket. Thus it is all about the semantics of the available ticket
status.

We can then as well codify the current workflow.

Therefore, I now created #18228 to change the developer guide to state that one
should not push commits to a ticket set to positive review. This ticket needs
review.

Regards, CH

-- 
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] Please review trac#18229.

[Emmanuel Charpentier]

Small change ticket : upgrade R to 3.1.3. That's trac#18229 
.

HTH,

--
Emmanuel Charpentier

-- 
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: Broken options of show() in Sage 6.6

[Nathann Cohen]

Hell,

This problem is very common with functions that take **args as input. It 
usually isn't hard to fix: you just have to make sure that a function 
taking **args as input will *ALWAYS* call another function with **args as 
argument. At the end of the call there should be some function which does 
not take **args as input, and thus does the job properly. This way, you are 
sure that the content is never lost.

Add me in Cc if you open a ticket, it will be quickly reviewed.

Nathann

On Thursday, April 16, 2015 at 5:24:26 PM UTC+2, Eric Gourgoulhon wrote:
>
> Hi,
>
> In Sage 6.6, it seems that the options passed to show() for displaying a 
> 3D object are not taken into account:
>
> sage: show(sphere(), figsize=10, frame=False, aspect_ratio=(1,1,0.5))
>
> gives the same output as a mere show(sphere()).
>  
> This issue occurs both with the default viewer (Jmol) as with Tachyon. For 
> a 2D object, there is no problem. 
>
> For Sage 6.5, it was OK. 
> For Sage 6.6.beta5, the problem was already there (but I've noticed it 
> only today, sorry...).
>
> Eric.
>

-- 
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] installation of optional spkg's on binary Sage releases

[Nathann Cohen]

>
> Side question -- Is anything guaranteed to build all optional 
> packages?   What's the current status of testing them?  I keep raising 
> this issue... 
>

If you ever get tired of raising the issue, maybe you could try doing 
something about it.

Nathann 

-- 
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] Bad display of tuples in Sage 6.6 notebooks

[Eric Gourgoulhon]

Hi,

In Sage 6.6 notebooks (either Sage notebook or IPython notebook), tuples 
are displayed without parenthesis nor comma (!) when the LaTeX typeset mode 
is turned on (i.e. with 'typeset' box clicked in the Sage notebook or with 
%display latex in the IPython notebook):

input: (1,2)
output: *12*

input: (x,x,x)
output: *xx*x

Eric.

-- 
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.