Another problem I've encountered concerns including numerical integrals in
piecewise functions. This used to work in Sage 6.9:
def g(x):
var('u')
return numerical_integral(u^2,0,x)[0]
f=piecewise([ [(0,1), g ] ])
but now gives the error message
Thanks for clearing that up. This is definitely new behavior.
On Saturday, May 21, 2016 at 3:58:27 PM UTC-7, Michael Orlitzky wrote:
>
> On 05/21/2016 06:06 PM, paulmasson wrote:
> > Since the SageMathCell server has been updated to Sage 7.2, I've been
> > experiencing issues with piecewise func
On 05/21/2016 06:06 PM, paulmasson wrote:
> Since the SageMathCell server has been updated to Sage 7.2, I've been
> experiencing issues with piecewise functions. For example, define a
> simple saw tooth with
>
Piecewise functions were totally rewritten in #14801. Lower-case
"piecewise" now works
Thats the expected output since 1 is not in the domain:
sage: f.domain()
(0, 1) + (1, 3) + (3, 4)
You probably want
sage: g = piecewise([[(0,1),x], [[1,3],2-x], [(3,4),x-4]])
sage: g.domain()
(0, 4)
sage: g.plot([0,4])
On Sunday, May 22, 2016 at 12:06:27 AM UTC+2, paulmasson wrote:
>
> Since
thank you Volker. I think it did go ok.
El sábado, 21 de mayo de 2016, 20:32:19 (UTC+2), Volker Braun escribió:
>
> Assuming that you have the branch checked out:
>
> git reset --hard HEAD~ # go back one commit
> git trac push --force # if you use the git-trac script
>
> On Saturday
Since the SageMathCell server has been updated to Sage 7.2, I've been
experiencing issues with piecewise functions. For example, define a simple
saw tooth with
f=piecewise([[(0,1),x],[(1,3),2-x],[(3,4),x-4]])
The endpoints appear to be defined just fine,
f.end_points()
[0, 1, 3, 4]
but if I
Solve
I took the linux binary 16.04 and in local I bash sm-install
Everything is working fine now.
thanks
Henri
Le samedi 21 mai 2016 16:30:14 UTC+2, aishen a écrit :
>
> Hi,
> I am on ubuntu 16.10 (16.04 +1), and I can't compile sage 7.2 (flint error)
> Si I install ppa version 7.1 and
> sudo
Assuming that you have the branch checked out:
git reset --hard HEAD~ # go back one commit
git trac push --force # if you use the git-trac script
On Saturday, May 21, 2016 at 8:04:04 PM UTC+2, jhonrubia6 wrote:
>
> Is there a way to reset the last (erroneous) commit in trac ticket
Is there a way to reset the last (erroneous) commit in trac ticket 20636?
I forgot to checkout the correct branch before doing the changes and I
committed and pushed a commit that does not belong to this ticket. I posted
a comment, but I do not know how to revert the situation if possible
Javier
It's getting worse... ppa sage is seg fault and I can't compile 7.2 because
flint error, I wonder if I downgrade to 16.04 but I don't think that 's the
problem.
At the moment I don't have sage any more. I purge all and I will try to
restore that !
Thanks
Henri
Le samedi 21 mai 2016 16:30:14 UT
On Saturday, May 21, 2016 at 2:41:49 AM UTC-5, Ralf Stephan wrote:
>
> On Friday, May 20, 2016 at 11:53:52 PM UTC+2, saad khalid wrote:
>>
>> I was on trac, looking at the tickets under "Bugs silently producing
>> wrong answers". All of them seemed quite old, for the most part, and none
>> of the
My 2 cents: Leave any wishlist items open; people may be looking for things
to implement and someone might not know this was something somebody (at one
point) was interested in having.
+1 to closing all positively reviewed duplicate/invalid/wontfix tickets.
Best,
Travis
--
You received this m
Hi,
Le samedi 21 mai 2016 16:30:14 UTC+2, aishen a écrit :
>
> Hi,
> I am on ubuntu 16.10 (16.04 +1), and I can't compile sage 7.2 (flint error)
> Si I install ppa version 7.1 and
> sudo bash sm-install.sh everythink went well. Typing this in a console or in
> sage -n=jupyter get the following ?
Twisted should work under Python3 now. Some modules are missing but sagenb
might not depend on the more obscure stuff...
On Saturday, May 21, 2016 at 10:27:53 AM UTC+2, Dima Pasechnik wrote:
>
> Given the snail speed of twised is ported to Python 3, sagenb won't be
> ready in another year or mo
Hi,
I am on ubuntu 16.10 (16.04 +1), and I can't compile sage 7.2 (flint error)
Si I install ppa version 7.1 and
sudo bash sm-install.sh everythink went well. Typing this in a console or in
sage -n=jupyter get the following ?
Any help
Thanks
Henri
M = Manifold(4, 'M')
print M
---
There are some potential speed bumps, e.g. a minor change in how cyclic
imports are treated could become a huge headache. But at this point I don't
know of any real issue. Its probably more of a matter of deploying all the
2/3 testing tools that already exist and slowly bring every module forwar
On Sat, May 21, 2016 at 03:48:49AM -0700, Volker Braun wrote:
> Removing sagedev is now http://trac.sagemath.org/ticket/20645
+1 too, those scripts used to broke the patchbots running within a VM and
seem not to be used at all.
Ciao,
Thierry
>
> --
> You received this message because you are
Removing sagedev is now http://trac.sagemath.org/ticket/20645
--
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 t
My apologies! In my defense, it was really late last night ;-)
On Saturday, May 21, 2016 at 8:23:07 AM UTC+2, Frédéric Chapoton wrote:
>
> Sorry, but I am not Vincent.
>
> Le samedi 21 mai 2016 01:11:12 UTC+2, Volker Braun a écrit :
>>
>> I think there are a couple of low-hanging fruits that we s
Given the snail speed of twised is ported to Python 3, sagenb won't be
ready in another year or more (assuming it's still relevant then).
On Friday, May 20, 2016 at 7:05:01 PM UTC+1, William wrote:
>
> Hi,
>
> Somebody with possibly substantial grant funds asked me today: "How
> much might it
On 2016-05-21 01:11, Volker Braun wrote:
I think there are a couple of low-hanging fruits that we should clean up
first.
Yes, there is a huge amount of low-hanging fruit. But what scares me is
the high-hanging fruit.
--
You received this message because you are subscribed to the Google Group
On Friday, May 20, 2016 at 11:53:52 PM UTC+2, saad khalid wrote:
>
> I was on trac, looking at the tickets under "Bugs silently producing wrong
> answers". All of them seemed quite old, for the most part, and none of
> them(that I could find) had anything under Branch. Does this mean that they
>
Hello,
concerning changing the behaviour of print to python3 style,
There are still a few tickets needing review:
http://trac.sagemath.org/query?status=!closed&component=python3
Frederic
Le mardi 3 mai 2016 20:50:21 UTC+2, Frédéric Chapoton a écrit :
>
> Hello,
>
> I am trying to move toward
23 matches
Mail list logo
