i'm afraid i don't know how tickets work. Incidentally, i'll be attending sage-days in marseille next month, is this an occasion to learn about tickets and all that ?
as for the bug, i've been using x.complex_embedding() instead, which doesn't crash. How reliable can its output be, though ? On 14 jan, 19:33, Robert Bradshaw <rober...@math.washington.edu> wrote: > Is there a ticket for this? Sage bug squash is coming up this next > week, so the likelyhood is good that it would get looked at soon. > > - Robert > > On Jan 14, 2010, at 8:41 AM, Pierre wrote: > > > hi, i've just compiled a sage 4.3 from scratch (rather than update), > > and the problem is still there... > > > thoughts anyone ? > > > thanks! > > > On 14 jan, 13:37, Pierre <pierre.guil...@gmail.com> wrote: > >> hello, > > >> this must be the slowest reply in the history of sage. More than a > >> month later, i have upgraded and am now running sage 4.3. When i > >> enter > >> your lines : > > >>> sage: k.<i> = CyclotomicField(4) > >>> sage: R.<x> = k[] > >>> sage: p=3; K.<r> = NumberField(x^2-p) > >>> sage: i = K(k.gen()) > >>> sage: CDF(i) > > >> ... i get a very long error message, starting with > > >> RuntimeError Traceback (most recent call > >> last) > > >> /Users/pedro/.sage/temp/m_guillot.u_strasbg.fr/86998/ > >> _Users_pedro_toto_sage_0.py in <module>() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> complex_double.so in > >> sage.rings.complex_double.ComplexDoubleField_class.__call__ (sage/ > >> rings/complex_double.c:3532)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/structure/ > >> parent.so in sage.structure.parent.Parent.__call__ (sage/structure/ > >> parent.c:4956)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/structure/ > >> coerce_maps.so in > >> sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (sage/ > >> structure/coerce_maps.c:3142)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/structure/ > >> coerce_maps.so in > >> sage.structure.coerce_maps.DefaultConvertMap_unique._call_ (sage/ > >> structure/coerce_maps.c:3040)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> complex_double.so in > >> sage > >> .rings.complex_double.ComplexDoubleField_class._element_constructor_ > >> (sage/rings/complex_double.c:3933)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> number_field/number_field_element.so in > >> sage > >> .rings > >> .number_field > >> .number_field_element.NumberFieldElement._complex_double_ > >> (sage/rings/number_field/number_field_element.cpp:8220)() > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> complex_field.pyc in __call__(self, x, im) > >> 265 if im is not None: > >> 266 x = x, im > >> --> 267 return Parent.__call__(self, x) > >> 268 > >> 269 def _element_constructor_(self, x): > > >> it goes on forever and ends with : > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> polynomial/polynomial_ring.pyc in _element_constructor_(self, x, > >> check, is_gen, construct, **kwds) > >> 310 x = x.Polrev() > >> 311 > >> --> 312 return C(self, x, check, is_gen, construct=construct, > >> **kwds) > >> 313 > >> 314 def is_integral_domain(self, proof = True): > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> polynomial/polynomial_element_generic.pyc in __init__(self, parent, > >> x, > >> check, is_gen, construct) > >> 610 """ > >> 611 def __init__(self, parent, x=None, check=True, > >> is_gen=False, construct=False): > >> --> 612 Polynomial.__init__(self, parent, is_gen=is_gen) > >> 613 > >> 614 if construct: > > >> /Applications/sage/local/lib/python2.6/site-packages/sage/rings/ > >> polynomial/polynomial_element.so in > >> sage.rings.polynomial.polynomial_element.Polynomial.__init__ (sage/ > >> rings/polynomial/polynomial_element.c:3580)() > > >> RuntimeError: maximum recursion depth exceeded while calling a Python > >> object > > >> Does this happen to everyone on sage 4.3 ? the upgrade seems to have > >> worked fine, but for a couple of warnings, like > > >> /Applications/sage/devel/sage/doc/en/reference/sage/rings/polynomial/ > >> pbori.rst:6: (WARNING/2) error while formatting signature for > >> sage.rings.polynomial.pbori.BooleSetIterator.next: arg is not a > >> module, class, method, function, traceback, frame, or code object > >> /Applications/sage/devel/sage/doc/en/reference/sage/rings/polynomial/ > >> pbori.rst:6: (WARNING/2) error while formatting signature for > >> sage.rings.polynomial.pbori.BooleanMonomialIterator.next: arg is > >> not a > >> module, class, method, function, traceback, frame, or code object > >> /Applications/sage/devel/sage/doc/en/reference/sage/rings/polynomial/ > >> pbori.rst:6: (WARNING/2) error while formatting signature for > >> sage.rings.polynomial.pbori.BooleanMonomialMonoid.gen: arg is not a > >> Python function > > >> (21 warnings in total) > > >> thanks for your help > >> pierre > > -- > > To post to this group, send email to sage-support@googlegroups.com > > To unsubscribe from this group, send email to > > sage-support+unsubscr...@googlegroups.com > > For more options, visit this group > > athttp://groups.google.com/group/sage-support > > URL:http://www.sagemath.org
-- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
