[sage-devel] Re: Piecewise functions in Sage 7.2
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
---
TypeError Traceback (most recent call last)
in ()
4
5
> 6 f=piecewise([ [(Integer(0),Integer(1)), g ] ])
7
/home/sc_serv/sage/src/sage/misc/lazy_import.pyx in
sage.misc.lazy_import.LazyImport.__call__
(/home/sc_serv/sage/src/build/cythonized/sage/misc/lazy_import.c:3628)()
384 True
385 """
--> 386 return self._get_object()(*args, **kwds)
387
388 def __repr__(self):
/home/sc_serv/sage/local/lib/python2.7/site-packages/sage/functions/piecewise.py
in __call__(self, function_pieces, **kwds)
149 function = function()
150 else:
--> 151 function = function(var)
152 function = SR(function)
153 if var is None and len(function.variables()) > 0:
in g(x)
1 def g(x):
2 var('u')
> 3 return numerical_integral(u**Integer(2),Integer(0),x)[Integer(0)]
4
5
/home/sc_serv/sage/src/sage/gsl/integration.pyx in
sage.gsl.integration.numerical_integral
(/home/sc_serv/sage/src/build/cythonized/sage/gsl/integration.c:3387)()
329 else:
330 _a=a
--> 331 _b=b
332 W =
gsl_integration_workspace_alloc(n)
333 sig_on()
/home/sc_serv/sage/src/sage/symbolic/expression.pyx in
sage.symbolic.expression.Expression.__float__
(/home/sc_serv/sage/src/build/cythonized/sage/symbolic/expression.cpp:10403)()
1384 return float(self._eval_self(float))
1385 except TypeError:
-> 1386 raise TypeError("unable to simplify to float approximation")
1387
1388 def __complex__(self):
TypeError: unable to simplify to float approximation
which makes no sense since a numerical integral is already a float. Is
there some other new behavior I'm missing?
--
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] Piecewise functions in Sage 7.2
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 functions. For example, define a > > simple saw tooth with > > > > Piecewise functions were totally rewritten in #14801. Lower-case > "piecewise" now works a little bit different than upper-case "Piecewise" > used to. The new version differentiates between the open interval (1,2) > and the closed interval [1,2]. > > If you need the compatibility, the upper-case version is still there. > > (I noticed piecewise? doesn't give me any useful docs, I get the > docstring for LazyImport.) > > -- 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] Piecewise functions in Sage 7.2
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 a little bit different than upper-case "Piecewise" used to. The new version differentiates between the open interval (1,2) and the closed interval [1,2]. If you need the compatibility, the upper-case version is still there. (I noticed piecewise? doesn't give me any useful docs, I get the docstring for LazyImport.) -- 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: Piecewise functions in Sage 7.2
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 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 evaluate f(1) I get this message:
>
>
> ---
> ValueErrorTraceback (most recent call last)
> in ()
> 2 #show(plot(f))
> 3 f.end_points()
> > 4 f(Integer(1))
>
> /home/sc_serv/sage/local/lib/python2.7/site-packages/sage/symbolic/function_factory.pyc
> in new_f(ex, *args, **kwds)
> 400 new_args = list(ex._unpack_operands())
> 401 new_args.extend(args)
> --> 402 return f(ex, *new_args, **kwds)
> 403 return new_f
>
> /home/sc_serv/sage/local/lib/python2.7/site-packages/sage/functions/piecewise.py
> in __call__(cls, self, parameters, variable, value, **kwds)
> 447 if value is not None:
> 448 substitution[variable] = value
> --> 449 return self.subs(substitution)
> 450
> 451 def _fast_float_(cls, self, *args):
>
> /home/sc_serv/sage/src/sage/symbolic/expression.pyx in
> sage.symbolic.expression.Expression.substitute
> (/home/sc_serv/sage/src/build/cythonized/sage/symbolic/expression.cpp:27845)()
>4883
>4884 return new_Expression_from_GEx(self._parent,
> -> 4885self._gobj.subs_map(smap, 0))
>4886
>4887 subs = substitute
>
> /home/sc_serv/sage/local/lib/python2.7/site-packages/sage/functions/piecewise.py
> in _subs_(self, subs_map, options, parameters, x)
> 228 if domain.contains(point):
> 229 return subs_map.apply_to(func, 0)
> --> 230 raise ValueError('point {} is not in the
> domain'.format(point))
> 231
> 232 @staticmethod
>
> ValueError: point 1 is not in the domain
>
>
> Adding decimal points to the endpoints to coerce them to float values
> doesn't fix the problem.
>
> Sage 7.2 includes http://trac.sagemath.org/ticket/14801 that is supposed
> to fix problems with symbolics. Am I missing some new behavior or is this a
> bug?
>
>
--
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: reset a commit in trac
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, 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 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 >> > -- 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] Piecewise functions in Sage 7.2
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 evaluate f(1) I get this message:
---
ValueErrorTraceback (most recent call last)
in ()
2 #show(plot(f))
3 f.end_points()
> 4 f(Integer(1))
/home/sc_serv/sage/local/lib/python2.7/site-packages/sage/symbolic/function_factory.pyc
in new_f(ex, *args, **kwds)
400 new_args = list(ex._unpack_operands())
401 new_args.extend(args)
--> 402 return f(ex, *new_args, **kwds)
403 return new_f
/home/sc_serv/sage/local/lib/python2.7/site-packages/sage/functions/piecewise.py
in __call__(cls, self, parameters, variable, value, **kwds)
447 if value is not None:
448 substitution[variable] = value
--> 449 return self.subs(substitution)
450
451 def _fast_float_(cls, self, *args):
/home/sc_serv/sage/src/sage/symbolic/expression.pyx in
sage.symbolic.expression.Expression.substitute
(/home/sc_serv/sage/src/build/cythonized/sage/symbolic/expression.cpp:27845)()
4883
4884 return new_Expression_from_GEx(self._parent,
-> 4885self._gobj.subs_map(smap, 0))
4886
4887 subs = substitute
/home/sc_serv/sage/local/lib/python2.7/site-packages/sage/functions/piecewise.py
in _subs_(self, subs_map, options, parameters, x)
228 if domain.contains(point):
229 return subs_map.apply_to(func, 0)
--> 230 raise ValueError('point {} is not in the domain'.format(point))
231
232 @staticmethod
ValueError: point 1 is not in the domain
Adding decimal points to the endpoints to coerce them to float values
doesn't fix the problem.
Sage 7.2 includes http://trac.sagemath.org/ticket/14801 that is supposed to
fix problems with symbolics. Am I missing some new behavior or is this a
bug?
--
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: sagemanifolds error
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 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
>
> ---NotImplementedError
>Traceback (most recent call
> last) in ()> 1 M =
> Manifold(Integer(4), 'M') 2 print M
> /usr/lib/sagemath/src/sage/misc/lazy_import.pyx in
> sage.misc.lazy_import.LazyImport.__call__
> (/usr/lib/sagemath//src/build/cythonized/sage/misc/lazy_import.c:3560)()
> 384 True385 """--> 386 return
> self._get_object()(*args, **kwds)387 388 def __repr__(self):
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/manifolds/manifold.py
> in Manifold(dim, name, latex_name, field, structure, start_index,
> **extra_kwds) 1653 else: 1654 raise
> NotImplementedError("manifolds of type {} are not ".format(structure) +->
> 1655 "implemented") 1656 return
> TopologicalManifold(dim, name, field, structure, 1657
> latex_name=latex_name, start_index=start_index,
> NotImplementedError: manifolds of type smooth are not implemented
>
>
>
--
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: reset a commit in trac
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 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 > -- 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] reset a commit in trac
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 -- 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: sagemanifolds error
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 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 ?
> Any help
> Thanks
> Henri
>
> M = Manifold(4, 'M')
>
> print M
>
> ---NotImplementedError
>Traceback (most recent call
> last) in ()> 1 M =
> Manifold(Integer(4), 'M') 2 print M
> /usr/lib/sagemath/src/sage/misc/lazy_import.pyx in
> sage.misc.lazy_import.LazyImport.__call__
> (/usr/lib/sagemath//src/build/cythonized/sage/misc/lazy_import.c:3560)()
> 384 True385 """--> 386 return
> self._get_object()(*args, **kwds)387 388 def __repr__(self):
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/manifolds/manifold.py
> in Manifold(dim, name, latex_name, field, structure, start_index,
> **extra_kwds) 1653 else: 1654 raise
> NotImplementedError("manifolds of type {} are not ".format(structure) +->
> 1655 "implemented") 1656 return
> TopologicalManifold(dim, name, field, structure, 1657
> latex_name=latex_name, start_index=start_index,
> NotImplementedError: manifolds of type smooth are not implemented
>
>
>
--
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: Bugs silently producing wrong answers
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 them(that I could find) had anything under Branch. Does this mean that >> they have been dealt with? What exactly is the situation with all of those >> tickets? >> > > No, if they were fixed they would be "closed". > Although it is possible that someone has not checked that they do now produce the correct answers. It might also be good to add a doctest verifying these have been fixed (quite possibly incidentally or it was [unknown] symptom of another ticket). Best, Travis -- 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: Should we close all tickets with milestone "sage-duplicate/invalid/wontfix"?
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 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: sagemanifolds error
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 ? > Any help > Thanks > Henri > > M = Manifold(4, 'M') > > print M > > ---NotImplementedError >Traceback (most recent call last)NotImplementedError: > manifolds of type smooth are not implemented > > It seems you are running only the version of SageManifolds which is included in main Sage. For the time being, only topological manifold are implemented in this version, hence the error message. For instance, if you try M = Manifold(4, 'M', structure='topological') it should be OK. Regarding the install of the full SageManifolds, are you sure you have run sm-install.sh from the Sage 7.2 root directory ? Best wishes, 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Python3
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 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 cost to get Sage to work with Python3?" >> >> I don't know. Anybody have any thoughts? Is there anybody reading >> this who wishes they could spend several months getting Sage to fully >> work with Python3 instead of teaching Calculus? >> >> -- William >> >> -- >> 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] sagemanifolds error
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
---NotImplementedError
Traceback (most recent call
last) in ()> 1 M =
Manifold(Integer(4), 'M') 2 print M
/usr/lib/sagemath/src/sage/misc/lazy_import.pyx in
sage.misc.lazy_import.LazyImport.__call__
(/usr/lib/sagemath//src/build/cythonized/sage/misc/lazy_import.c:3560)()384
True385 """--> 386 return
self._get_object()(*args, **kwds)387 388 def __repr__(self):
/usr/lib/sagemath/local/lib/python2.7/site-packages/sage/manifolds/manifold.py
in Manifold(dim, name, latex_name, field, structure, start_index, **extra_kwds)
1653 else: 1654 raise NotImplementedError("manifolds of type {}
are not ".format(structure) +-> 1655
"implemented") 1656 return TopologicalManifold(dim, name, field,
structure, 1657latex_name=latex_name,
start_index=start_index,
NotImplementedError: manifolds of type smooth are not implemented
--
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: Python3
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 forward. Another milestone is surely to run python2 with the -3 switch turned on. E.g. right now: $ echo 'from sage.all import *' | sage -python -3 |& grep Deprecation | cut -d : -f 3- | sort -u DeprecationWarning: Overriding __eq__ blocks inheritance of __hash__ in 3.x DeprecationWarning: the cmp argument is not supported in 3.x DeprecationWarning: type inequality comparisons not supported in 3.x On Saturday, May 21, 2016 at 10:19:17 AM UTC+2, Jeroen Demeyer wrote: > > 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 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: Doctests failures in sage.dev
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 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. -- 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: Doctests failures in sage.dev
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 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: Python3
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 should clean up >> first. Right now Vincent is adding "from __future__ import print_function" >> > -- 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: Python3
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 cost to get Sage to work with Python3?" > > I don't know. Anybody have any thoughts? Is there anybody reading > this who wishes they could spend several months getting Sage to fully > work with Python3 instead of teaching Calculus? > > -- William > > -- > 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Python3
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 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: Bugs silently producing wrong answers
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 > have been dealt with? What exactly is the situation with all of those > tickets? > No, if they were fixed they would be "closed". -- 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: print to python3
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 using the python3 syntax for print. > > This is done by small chunks, using a lot of tiny tickets, according the > folders in sage, mostly. > These tickets can be found at the bottom of > > http://trac.sagemath.org/query?status=!closed&component=python3 > > If some of you could find time to review one of those, that would help to > advance the change. > > Many thanks to those that have already reviewed some of these. > > cheers, > Frederic > -- 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.
