Re: [sage-devel] Re: sage.6.2 - error building doc

[Anne Schilling]

sage-6.2 build successfully, but perhaps the make doc-clean was not successful

make doc-clean
cd src/doc && make -j4 clean
Deleting generated docs...
rm -rf en/reference/*/sage
rm -rf en/reference/*/sagenb
rm -rf en/reference/sage
rm -rf en/reference/sagenb
rm -rf output
git clean -f -d .
make[1]: git: No such file or directory
make[1]: *** [clean] Error 1
make: *** [doc-clean] Error 2


What am I supposed to do?

Anne

On 5/6/14 11:41 PM, Volker Braun wrote:
> did "make doc-clean" finish successfully and did you actually build sage 6.2?
> 
> On Wednesday, May 7, 2014 4:30:43 AM UTC+2, Anne Schilling wrote:
> 
> 
> Hi Volker,
> 
> I also have trouble building the doc with sage with the latest 
> development version of sage
> 
> lolita-4:sage anne$ sage
> ┌┐
> │ Sage Version 6.2, Release Date: 2014-05-06 │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
> 
> [reference] calculus: 2 todos, 24 index, 2 citations, 23 modules
> [reference] categories: 14 todos, 131 index, 15 citations, 130 modules
> [reference] cmd:
> [reference] WARNING: Unable to fetch 
> /Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle
> Error building the documentation.
> Traceback (most recent call last):
>   File "/Applications/sage/src/doc/common/builder.py", line 1477, in 
> 
> getattr(get_builder(name), type)()
>   File "/Applications/sage/src/doc/common/builder.py", line 276, in 
> _wrapper
> getattr(get_builder(document), 'inventory')(*args, **kwds)
>   File "/Applications/sage/src/doc/common/builder.py", line 500, in 
> _wrapper
> getattr(DocBuilder(self.name , lang), 
> format)(*args, **kwds)
>   File "/Applications/sage/src/doc/common/builder.py", line 94, in f
> execfile(sys.argv[0])
>   File "/Applications/sage/src/doc/common/custom-sphinx-build.py", line 
> 210, in 
> raise OSError(ERROR_MESSAGE)
> OSError: [reference] WARNING: Unable to fetch 
> /Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle
> 
> This is after I ran make doc-clean.
> 
> Best,
> 
> Anne
> make: *** [doc-html] Error 1

-- 
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: sage.6.2 - error building doc

[Volker Braun]

did "make doc-clean" finish successfully and did you actually build sage 
6.2?

On Wednesday, May 7, 2014 4:30:43 AM UTC+2, Anne Schilling wrote:
>
>
> Hi Volker,
>
> I also have trouble building the doc with sage with the latest development 
> version of sage
>
> lolita-4:sage anne$ sage
> ┌┐
> │ Sage Version 6.2, Release Date: 2014-05-06 │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
>
> [reference] calculus: 2 todos, 24 index, 2 citations, 23 modules
> [reference] categories: 14 todos, 131 index, 15 citations, 130 modules
> [reference] cmd:
> [reference] WARNING: Unable to fetch 
> /Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle
> Error building the documentation.
> Traceback (most recent call last):
>   File "/Applications/sage/src/doc/common/builder.py", line 1477, in 
> 
> getattr(get_builder(name), type)()
>   File "/Applications/sage/src/doc/common/builder.py", line 276, in 
> _wrapper
> getattr(get_builder(document), 'inventory')(*args, **kwds)
>   File "/Applications/sage/src/doc/common/builder.py", line 500, in 
> _wrapper
> getattr(DocBuilder(self.name, lang), format)(*args, **kwds)
>   File "/Applications/sage/src/doc/common/builder.py", line 94, in f
> execfile(sys.argv[0])
>   File "/Applications/sage/src/doc/common/custom-sphinx-build.py", line 
> 210, in 
> raise OSError(ERROR_MESSAGE)
> OSError: [reference] WARNING: Unable to fetch 
> /Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle
>
> This is after I ran make doc-clean.
>
> Best,
>
> Anne
> make: *** [doc-html] Error 1
>
>

-- 
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: interact.sagemath.org

[Ivan Andrus]

On May 6, 2014, at 11:47 AM, Jason Grout  wrote:

> On 5/5/14, 14:20, Daniel Bell wrote:
>> Hi
>> 
>> I am one of the students who was selected for working with Sage for
>> Google Summer of Code.  I will be working on the iOS app.  One of the
>> features I want to implement is the ability to interact with
>> interact.sagemath.org 
>> 
>> Is there an API I can use, or a database I can interact with?
> 
> interact.sagemath.org is using Drupal, so I imagine it would be a pretty 
> standard thing to enable a REST API or something of that sort.  Would you 
> like to take over the website and do that?

I take it from this that you were the maintainer, and it will therefore be 
abandoned soon?

-Ivan

-- 
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: sage.6.2 - error building doc

[Anne Schilling]

Hi Volker,

I also have trouble building the doc with sage with the latest development 
version of sage

lolita-4:sage anne$ sage
┌┐
│ Sage Version 6.2, Release Date: 2014-05-06 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘

[reference] calculus: 2 todos, 24 index, 2 citations, 23 modules
[reference] categories: 14 todos, 131 index, 15 citations, 130 modules
[reference] cmd:
[reference] WARNING: Unable to fetch 
/Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle
Error building the documentation.
Traceback (most recent call last):
  File "/Applications/sage/src/doc/common/builder.py", line 1477, in 

getattr(get_builder(name), type)()
  File "/Applications/sage/src/doc/common/builder.py", line 276, in _wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
  File "/Applications/sage/src/doc/common/builder.py", line 500, in _wrapper
getattr(DocBuilder(self.name, lang), format)(*args, **kwds)
  File "/Applications/sage/src/doc/common/builder.py", line 94, in f
execfile(sys.argv[0])
  File "/Applications/sage/src/doc/common/custom-sphinx-build.py", line 
210, in 
raise OSError(ERROR_MESSAGE)
OSError: [reference] WARNING: Unable to fetch 
/Applications/sage/src/doc/output/doctrees/en/reference/cmd/environment.pickle

This is after I ran make doc-clean.

Best,

Anne
make: *** [doc-html] Error 1

-- 
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: keep getting error building sage

[Volker Braun]

Alternatively, change PATH to exclude your fink install.



On Wednesday, May 7, 2014 12:06:49 AM UTC+2, Anne Schilling wrote:
>
>
>
> On Friday, March 14, 2014 8:05:15 AM UTC-7, kcrisman wrote:
>>
>>
>>
>> On Thursday, March 13, 2014 3:53:53 PM UTC-4, Volker Braun wrote:
>>>
>>> We restored the prereq tests, so that is probably the change. You can 
>>> set SAGE_PORT=yes and see how far you get...
>>>


>> Right, Anne set it to True, not "yes".  But shouldn't "anything nonempty" 
>> work?  So probably she needs to move /sw for now.
>>
>
> I have tried to compile the latest version of Sage and the SAGE_PORT="yes" 
> trick does not work any longer. Now I had to move my
> /sw folder. Is it possible to change the prereq tests? It seems weird to 
> have to move a whole folder just to compile sage ...
>
> Best,
>
> Anne 
>

-- 
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: sage.6.2 - error building doc

[Volker Braun]

Which Sage version? What is at position 2885 of abstract_tree.py?



On Tuesday, May 6, 2014 11:35:43 PM UTC+2, vdelecroix wrote:
>
> Hello, 
>
> I have some trouble building the documentation 
>
>  $ make doc-clean 
>  $ make doc 
>
> stops running after 30secs with 
>
> ... 
> [combinat ] reading sources... [  6%] sage/combinat/abstract_tree 
> [combinat ] Sphinx error: 
> [combinat ] 'ascii' codec can't decode byte 0xc3 in position 2885: 
> ordinal not in range(128) 
> Error building the documentation. 
> Traceback (most recent call last): 
>   File "/opt/sage/src/doc/common/builder.py", line 1477, in  
> getattr(get_builder(name), type)() 
>   File "/opt/sage/src/doc/common/builder.py", line 276, in _wrapper 
> getattr(get_builder(document), 'inventory')(*args, **kwds) 
>   File "/opt/sage/src/doc/common/builder.py", line 487, in _wrapper 
> x.get(9) 
>   File "/opt/sage/local/lib/python/multiprocessing/pool.py", line 554, in 
> get 
> raise self._value 
> OSError: [combinat ] Sphinx error: 
>
> make: *** [doc-html] Erreur 1 
>
> Thanks 
> 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] Re: keep getting error building sage

[Anne Schilling]

On Friday, March 14, 2014 8:05:15 AM UTC-7, kcrisman wrote:
>
>
>
> On Thursday, March 13, 2014 3:53:53 PM UTC-4, Volker Braun wrote:
>>
>> We restored the prereq tests, so that is probably the change. You can set 
>> SAGE_PORT=yes and see how far you get...
>>
>>>
>>>
> Right, Anne set it to True, not "yes".  But shouldn't "anything nonempty" 
> work?  So probably she needs to move /sw for now.
>

I have tried to compile the latest version of Sage and the SAGE_PORT="yes" 
trick does not work any longer. Now I had to move my
/sw folder. Is it possible to change the prereq tests? It seems weird to 
have to move a whole folder just to compile sage ...

Best,

Anne 

-- 
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] sage.6.2 - error building doc

[Vincent Delecroix]

Hello,

I have some trouble building the documentation

 $ make doc-clean
 $ make doc

stops running after 30secs with

...
[combinat ] reading sources... [  6%] sage/combinat/abstract_tree
[combinat ] Sphinx error:
[combinat ] 'ascii' codec can't decode byte 0xc3 in position 2885:
ordinal not in range(128)
Error building the documentation.
Traceback (most recent call last):
  File "/opt/sage/src/doc/common/builder.py", line 1477, in 
getattr(get_builder(name), type)()
  File "/opt/sage/src/doc/common/builder.py", line 276, in _wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
  File "/opt/sage/src/doc/common/builder.py", line 487, in _wrapper
x.get(9)
  File "/opt/sage/local/lib/python/multiprocessing/pool.py", line 554, in get
raise self._value
OSError: [combinat ] Sphinx error:

make: *** [doc-html] Erreur 1

Thanks
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] Re: test message

[Jason Grout]

On 5/6/14, 9:05, Simon King wrote:

I wouldn't mind to stay with google-groups, *IF* one could use it via
gmane (which is currently not the case).


I'm replying to this on gmane (via thunderbird).  If you see this 
message, I guess it shows it is possible.


Jason


--
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: interact.sagemath.org

[Jason Grout]

On 5/5/14, 14:20, Daniel Bell wrote:

Hi

I am one of the students who was selected for working with Sage for
Google Summer of Code.  I will be working on the iOS app.  One of the
features I want to implement is the ability to interact with
interact.sagemath.org 

Is there an API I can use, or a database I can interact with?



interact.sagemath.org is using Drupal, so I imagine it would be a pretty 
standard thing to enable a REST API or something of that sort.  Would 
you like to take over the website and do that?


Thanks,

Jason


--
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: bug in removing sage: prompts

[Jeroen Demeyer]

On 2014-05-06 18:41, John H Palmieri wrote:

So do we
need to restore the old behavior. sage-devel, what do you think?
+1 to this. I sometimes copy-paste an already copy-pasted session and 
find the stripping of multiple prompts very handy.


--
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: bug in removing sage: prompts

[John H Palmieri]

On Tuesday, May 6, 2014 10:25:24 AM UTC-7, leif wrote:
>
> On Tuesday, May 6, 2014 6:41:58 PM UTC+2, John H Palmieri wrote:
>
>> On Tuesday, May 6, 2014 9:25:09 AM UTC-7, John Cremona wrote:
>>>
>>> It's a bit late to report this now that #16196 is merged and 6.2 
>>> released, but I just cut-and-pasted some lines starting with "sage: 
>>> sage: N=25" etc and it did not work.  This can easliy happen when 
>>> posting examples from posting into a sage session and then copying the 
>>> results back. 
>>>
>>
>> I apologize about that. I asked on that ticket if we needed to maintain 
>> backwards compatibility regarding multiple "sage:" prompts on a line, and I 
>> allowed myself to be convinced that we didn't need to. So do we need to 
>> restore the old behavior. sage-devel, what do you think?
>>
>
> IMHO yes, pasting "sage: sage: sage: foo()" should work...
>
> (I actually thought #16196 would restore that as well.)
>
>
I opened up http://trac.sagemath.org/ticket/16297 for this issue.

-- 
John

-- 
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] RAM to build Sage

[Jeroen Demeyer]

On 2014-05-06 16:53, John Cremona wrote:

In practice, it may be hard to gather the informatino on how much RAM
tests take

You could run them under "ulimit -v" and see when they start to fail.

But personally, I don't consider RAM usage by doctests an issue.

Jeroen.

--
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] RAM to build Sage

[leif]

On Tuesday, May 6, 2014 4:55:54 PM UTC+2, Volker Braun wrote:

> Just like the # optional: internet tests, anything that we don't actually 
> test will be broken. Every different type of # optional tag will lead to 
> fewer tests being done.
>

sage: foo() # optional - RAM
bar

Nice idea.


-leif 

-- 
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: bug in removing sage: prompts

[leif]

On Tuesday, May 6, 2014 6:41:58 PM UTC+2, John H Palmieri wrote:

> On Tuesday, May 6, 2014 9:25:09 AM UTC-7, John Cremona wrote:
>>
>> It's a bit late to report this now that #16196 is merged and 6.2 
>> released, but I just cut-and-pasted some lines starting with "sage: 
>> sage: N=25" etc and it did not work.  This can easliy happen when 
>> posting examples from posting into a sage session and then copying the 
>> results back. 
>>
>
> I apologize about that. I asked on that ticket if we needed to maintain 
> backwards compatibility regarding multiple "sage:" prompts on a line, and I 
> allowed myself to be convinced that we didn't need to. So do we need to 
> restore the old behavior. sage-devel, what do you think?
>

IMHO yes, pasting "sage: sage: sage: foo()" should work...

(I actually thought #16196 would restore that as well.)


-leif

-- 
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: Is there a problem with gmane?

[leif]

On Tuesday, May 6, 2014 1:18:46 PM UTC+2, leif wrote:

> On Tuesday, May 6, 2014 12:39:58 PM UTC+2, Simon King wrote:
>
>> Hi!
>>
>> Since I don't like the new google groups, I switched to using slrn and 
>> read the Sage groups in news.gmane.org.
>>
>> However, no new message has shown up in the Sage-gmane groups since two 
>> days or so. What is the problem? In google-groups (which I use for this 
>> post) I see that there *are* new posts.
>>
>> Best regards,
>> Simon
>>
>
> Yes, there is...
>
> There are no updates on Gmane since about early May 5th; cf.  
> http://gmane.org/stat-day.php .
>

For the record, Gmane starts updating now...


-leif

-- 
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: bug in removing sage: prompts

[John H Palmieri]

On Tuesday, May 6, 2014 9:25:09 AM UTC-7, John Cremona wrote:
>
> It's a bit late to report this now that #16196 is merged and 6.2 
> released, but I just cut-and-pasted some lines starting with "sage: 
> sage: N=25" etc and it did not work.  This can easliy happen when 
> posting examples from posting into a sage session and then copying the 
> results back. 
>

I apologize about that. I asked on that ticket if we needed to maintain 
backwards compatibility regarding multiple "sage:" prompts on a line, and I 
allowed myself to be convinced that we didn't need to. So do we need to 
restore the old behavior. sage-devel, what do you think?

  John

-- 
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] bug in removing sage: prompts

[John Cremona]

It's a bit late to report this now that #16196 is merged and 6.2
released, but I just cut-and-pasted some lines starting with "sage:
sage: N=25" etc and it did not work.  This can easliy happen when
posting examples from posting into a sage session and then copying the
results back.

John

-- 
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] modulo is broken in some (fairly simple) rings

[John Cremona]

On 6 May 2014 16:24, Charles Bouillaguet  wrote:
> Dear all,
>
> I would like to make a case for the quo_rem() method to actually implement 
> euclidean division when it makes sense, or to raise an exception when the 
> result is not defined. After all, this is what it is **supposed** to do, at 
> least according to the docstring in 
> sage/ring/polynomial/polynomial_element.pyx :
>
> """
> @coerce_binop
> def quo_rem(self, other):
> """
> Returns the quotient and remainder of the Euclidean division of
> ``self`` and ``other``.
>
> Raises ZerodivisionError if ``other`` is zero. Raises ArithmeticError 
> if ``other`` has
> a nonunit leading coefficient.
> """
>
> I personally think that this specification is correct and decent.
>
> Presently, depending on the domain, quo_rem does not always behave the same, 
> and not according to the same specification. Examples :
>
> In ZZ[X] or ZZ[X,Y] :
> ---
>
> sage: R. = ZZ[]
> sage: (X^100).quo_rem(2*X+1)
> (0, X^100)
>
> ---> Result is not defined, but quo_rem() does not complain. It tries to 
> reduce "as much as possible".
>
> in QQ[x][y] :
> 
>
> sage: P. = QQ[]
> sage: R. = P[]
> sage: f = R.random_element(10)
> sage: g = y^5+R.random_element(5)
> sage: q,r = f.quo_rem(g)
> sage: f == q*g + r
> True
> sage: g = x*y^5
> sage: f.quo_rem(g)
> Traceback (most recent call last):
> ...
> ArithmeticError: Nonunit leading coefficient
>
> ---> quo_rem() complains when result is not defined.
>
> So, I suggest that :
> a) we stick to the spec (what happens in QQ[x][y]).
> b) we fix the cases like ZZ[X] that do not stick to the spec
> c) we make sure, eventually by adding a "reduce" method or something like 
> that, that the previous behavior is still available somehow.
>
> I am willing to implement these changes. Do we agree on this?

+1 from me.  Will this replace he current patch/branch at #16276?

John

>
> ---
> Charles Bouillaguet
> http://www.lifl.fr/~bouillaguet/
>
>
>
> --
> 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.

-- 
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] modulo is broken in some (fairly simple) rings

[Charles Bouillaguet]

Dear all,

I would like to make a case for the quo_rem() method to actually implement 
euclidean division when it makes sense, or to raise an exception when the 
result is not defined. After all, this is what it is **supposed** to do, at 
least according to the docstring in sage/ring/polynomial/polynomial_element.pyx 
: 

"""
@coerce_binop
def quo_rem(self, other):
"""
Returns the quotient and remainder of the Euclidean division of
``self`` and ``other``.

Raises ZerodivisionError if ``other`` is zero. Raises ArithmeticError 
if ``other`` has
a nonunit leading coefficient.
"""

I personally think that this specification is correct and decent. 

Presently, depending on the domain, quo_rem does not always behave the same, 
and not according to the same specification. Examples : 

In ZZ[X] or ZZ[X,Y] : 
---

sage: R. = ZZ[]
sage: (X^100).quo_rem(2*X+1)
(0, X^100)

---> Result is not defined, but quo_rem() does not complain. It tries to reduce 
"as much as possible".

in QQ[x][y] :


sage: P. = QQ[]
sage: R. = P[]
sage: f = R.random_element(10)
sage: g = y^5+R.random_element(5)
sage: q,r = f.quo_rem(g)
sage: f == q*g + r
True
sage: g = x*y^5
sage: f.quo_rem(g)
Traceback (most recent call last):
...
ArithmeticError: Nonunit leading coefficient

---> quo_rem() complains when result is not defined.

So, I suggest that : 
a) we stick to the spec (what happens in QQ[x][y]).
b) we fix the cases like ZZ[X] that do not stick to the spec
c) we make sure, eventually by adding a "reduce" method or something like that, 
that the previous behavior is still available somehow.

I am willing to implement these changes. Do we agree on this?

---
Charles Bouillaguet
http://www.lifl.fr/~bouillaguet/



-- 
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: html docbuilder hangs after first pass

[Travis Scrimshaw]

I just retried that and watched my memory usage, but it didn't go anywhere 
close to the total memory available on my machine.

Best,
Travis


On Tuesday, May 6, 2014 12:43:17 AM UTC-7, Volker Braun wrote:
>
> On Tuesday, May 6, 2014 3:18:56 AM UTC+2, Travis Scrimshaw wrote:Hey 
> everyone,
>>
>>As the title states. I've run "make doc-clean" along with all known 
>> variants (including single and multi threaded) "make", "sage -docbuild all 
>> html", "make doc" (I've also run "sage -sync-build" too). I get some "gap: 
>> unable to extend workspace" while trying to build the doc. 
>>
>
> Out of memory...
>
> SAGE_NUM_THREADS=1 make doc
>
>  
>

-- 
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: sage-cleaner issues? clean up .sage/temp?

[John H Palmieri]

On Tuesday, May 6, 2014 12:51:28 AM UTC-7, Volker Braun wrote:
>
> FWIW I wrote the logging precisely because the cleaner used to fail in 
> funny ways that we never noticed because there was no output.
>

And I used it (and added some temporary logger messages to the 'rm_rf' 
function) to debug the problem.

  John

 

>
>
>
> On Monday, May 5, 2014 8:46:52 PM UTC+2, John H Palmieri wrote:
>>
>> This surprised me a little bit:
>>
>> $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log 
>> 3.6G/Users/palmieri/.sage/temp/jpalmieri/cleaner.log
>>
>> Is there any reason to have such a large file lying around? Should it be 
>> automatically cleaned up every now and then?
>>
>> Also, I've noticed several times a "sage-cleaner" process which was 
>> several days old. That's not supposed to happen anymore. For example, I saw 
>> this today:
>>
>> $ ps ux | grep python
>> palmieri 67905   0.0  0.1  2441608   7244   ??  SSat10AM  59:23.08 
>> python 
>> /Users/palmieri/Desktop/Sage_stuff/sage_builds/clean/sage-6.2.rc1/src/bin/sage-cleaner
>>
>> (Note that this was running in a built-from-tarball Sage 6.2.rc1, which 
>> certainly contains the fix from #15457.)
>>
>> There were also several hundred directories in .sage/temp/jpalmieri/, 
>> with names corresponding to old process IDs, long since dead. Some of these 
>> are empty, some have sub-directories with names like "dir_3SAu4B". 
>> Shouldn't all of these directories have been removed by sage-cleaner? I 
>> have noticed that various Sage processes of mine have been getting killed 
>> mysteriously. I wonder if it's an over-aggressive sage-cleaner, seeing an 
>> old directory in .sage/temp/jpalmieri and killing a new process with the 
>> same pid.
>>
>> For what it's worth, this is on OS X 10.8 (and I think I've also seen it 
>> on OS X 10.9).
>>
>> -- 
>> John
>>
>>

-- 
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] RAM to build Sage

[Volker Braun]

Just like the # optional: internet tests, anything that we don't actually 
test will be broken. Every different type of # optional tag will lead to 
fewer tests being done. I

-- 
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] RAM to build Sage

[John Cremona]

On 6 May 2014 15:43, David Roe  wrote:
>> Anyway, there are certainly (a lot of?) doctests that take quite some time,
>> but don't use extraordinarily much memory, so I think John's idea isn't that
>> bad.
>

I am flattered, since praise from leif is quite hard to earn ;)

In practice, it may be hard to gather the informatino on how much RAM
tests take; at least the --voberse option in testing gives you the
time for every test.

John

> +1
>
>> -leif
>>
>>
>>>
>>> On Tuesday, May 6, 2014 11:26:47 AM UTC+2, John Cremona wrote:

 If these tests are known, they could perhaps be tagged just as we tag
 with "#long time" those which take a long time.  Something like "#
 large RAM" required.  I don't know if this is possible though.

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

-- 
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] RAM to build Sage

[David Roe]

> Anyway, there are certainly (a lot of?) doctests that take quite some time,
> but don't use extraordinarily much memory, so I think John's idea isn't that
> bad.

+1

> -leif
>
>
>>
>> On Tuesday, May 6, 2014 11:26:47 AM UTC+2, John Cremona wrote:
>>>
>>> If these tests are known, they could perhaps be tagged just as we tag
>>> with "#long time" those which take a long time.  Something like "#
>>> large RAM" required.  I don't know if this is possible though.
>>>
>>> John
>
> --
> 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.

-- 
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: naive question on build process/patchbot

[Niles Johnson]

On Monday, May 5, 2014 10:10:27 AM UTC-4, Ralf Stephan wrote:
>
>
> 3. why not show the sage version the ticket was based and tested on
>by patchbot on the trac blob? What reason is there to show "6.1.1"
>when the ticket was tested by patchbots both a) by merging a develop
>version into 6.1.1 (so it's develop anyway) and b) based on current
>develop.
>

The functionality to create the blobs you want is already there, e.g.

http://patchbot.sagemath.org/ticket/11719/status.png?base=6.2.rc2

I agree it would be nice to display the latest non-trivial blob by default. 
 To do this, you could improve the function which makes the blob so that, 
when no base is given, it checks to see which is the latest base the ticket 
was tested on and returns the corresponding blob.  I believe that function 
is create_status_image:

https://github.com/robertwb/sage-patchbot/blob/3482b9d7f7fa76dbdb8553b3a3eab5acf2aedb9f/src/serve.py#L462
 

To support this, and maybe other patchbot interfacing, it would help to 
have a function which returns the most recent base on which the ticket was 
tested.  I'm not quite sure what "recent bases" should be checked -- maybe 
the list of tagged commits ordered by containment?  Maybe going back only 
to the most recent official release?

-Niles

-- 
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 #16282

[Martin Albrecht]

Hi all,

sage: P = PolynomialRing(GF(127),10, 'x')
sage: magma(P)

should work, but it doesn't. Here's the small fix: 

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

Cheers,
Martin

signature.asc
Description: This is a digitally signed message part.

Re: [sage-devel] test message

[Simon King]

Hi William,

Am Dienstag, 6. Mai 2014 15:41:46 UTC+2 schrieb William:
>
> That said, it's probably worth having the every-few-years discussion 
> about whether Google Groups are still the optimal choice for all of 
> the Sage mailing lists.  I personally can't think of anything 
> better... 
>

I wouldn't mind to stay with google-groups, *IF* one could use it via gmane 
(which is currently not the case).

Best regards,
Simon 

-- 
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] test message

[William Stein]

On Tue, May 6, 2014 at 6:38 AM, William A Stein  wrote:
> Hi,
>
> If this works, then posting from @uw.edu addresses works.  If not,
> then we should migrate to another mailing list provider.

It works :-)

That said, it's probably worth having the every-few-years discussion
about whether Google Groups are still the optimal choice for all of
the Sage mailing lists.  I personally can't think of anything
better...

William

-- 
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] test message

[William A Stein]

Hi,

If this works, then posting from @uw.edu addresses works.  If not,
then we should migrate to another mailing list provider.

William

-- 
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: near-field

[leif]

On Tuesday, May 6, 2014 3:01:54 PM UTC+2, Dima Pasechnik wrote:

> apparently I didn't cross-post this to sage-devel. Just in case, Dima
>

Interestingly, it showed up in sage-devel on Gmane (on May 3rd), so you 
presumably did...


-leif


On Saturday, 3 May 2014 22:22:22 UTC+2, Dima Pasechnik wrote:
>>
>> On 2014-05-03, Vincent Delecroix <> wrote: 
>> > Hello, 
>> > 
>> > I would like more projective planes seen as incidence structure. In 
>> > order to do so I need to introduce what are called near-field [1]. 
>> > Which is not exactly a division ring: the distributivity fail on one 
>> > of the side. 
>> > 
>> > Does anybody has some implementation already? Do you think I need a 
>> > proper category for the near fields? It would be fine to me to set the 
>> > category to "Rings" but perhaps it is more appropriate to have the 
>> > corresponding category. 
>>
>> Aren't Sage rings meant to have distributivity on both sides? 
>> Probably it might be fun (depending on your notion of fun :)) 
>> to have a category of structures with a ternary operation, 
>> as needed for coordinatizaton of even more general finite 
>> projective planes (then one will also have semi-fields, etc) 
>>
>> HTH, 
>> Dima 
>>
>> > Comments might also go on the ticket #16283. 
>> > 
>> > Best 
>> > Vincent 
>> > 
>> >   [1] http://en.wikipedia.org/wiki/Near-field_%28mathematics%29 
>> > 
>>
>>

-- 
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] Fwd: near-field

[Dima Pasechnik]

apparently I didn't cross-post this to sage-devel. Just in case, Dima

On Saturday, 3 May 2014 22:22:22 UTC+2, Dima Pasechnik wrote:
>
> On 2014-05-03, Vincent Delecroix <> wrote: 
> > Hello, 
> > 
> > I would like more projective planes seen as incidence structure. In 
> > order to do so I need to introduce what are called near-field [1]. 
> > Which is not exactly a division ring: the distributivity fail on one 
> > of the side. 
> > 
> > Does anybody has some implementation already? Do you think I need a 
> > proper category for the near fields? It would be fine to me to set the 
> > category to "Rings" but perhaps it is more appropriate to have the 
> > corresponding category. 
>
> Aren't Sage rings meant to have distributivity on both sides? 
> Probably it might be fun (depending on your notion of fun :)) 
> to have a category of structures with a ternary operation, 
> as needed for coordinatizaton of even more general finite 
> projective planes (then one will also have semi-fields, etc) 
>
> HTH, 
> Dima 
>
> > Comments might also go on the ticket #16283. 
> > 
> > Best 
> > Vincent 
> > 
> >   [1] http://en.wikipedia.org/wiki/Near-field_%28mathematics%29 
> > 
>
>

-- 
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] bug "make doc-pdf" fatal error

[Daniel Krenn]

Am 2014-05-05 14:55, schrieb Дима Щербаков:
> System is Debian amd64 testing.
> Hardware: Intel i7 4700MQ, 8Gb RAM, Nvidia 765M with proprietary driver.
> Trouble:  make doc-pdf fails with many errors (see attached file for log)
> Software installed - doxygen, all Sage's dependencies from
> sagemath.org/wiki, texlive-base, texlive-latex-base
> Is it bug? or what are dependencies of "make doc-pdf"
> If i missed something, please post what is it here :)
> Thanks in advance

No error here; 6.2.rc2 on Debian Wheezy; called "make doc-pdf" after
  make distclean
  make

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.

Re: [sage-devel] RAM to build Sage

[leif]

On Tuesday, May 6, 2014 12:53:21 PM UTC+2, Volker Braun wrote:

> Just "# long time" would be enough IMHO. It should be understood that long 
> doctests tend to consume more memory.
>

Which is another argument for *not* sorting doctests by previous runtime, 
i.e., *don't* run all of these first, at the same time... ;-)

Anyway, there are certainly (a lot of?) doctests that take quite some time, 
but don't use extraordinarily much memory, so I think John's idea isn't 
that bad.


-leif

 

> On Tuesday, May 6, 2014 11:26:47 AM UTC+2, John Cremona wrote:
>>
>> If these tests are known, they could perhaps be tagged just as we tag 
>> with "#long time" those which take a long time.  Something like "# 
>> large RAM" required.  I don't know if this is possible though. 
>>
>> John 
>>
>

-- 
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: Is there a problem with gmane?

[leif]

On Tuesday, May 6, 2014 12:39:58 PM UTC+2, Simon King wrote:

> Hi!
>
> Since I don't like the new google groups, I switched to using slrn and 
> read the Sage groups in news.gmane.org.
>
> However, no new message has shown up in the Sage-gmane groups since two 
> days or so. What is the problem? In google-groups (which I use for this 
> post) I see that there *are* new posts.
>
> Best regards,
> Simon
>

Yes, there is...

There are no updates on Gmane since about early May 5th; cf.  
http://gmane.org/stat-day.php .

But surprisingly it's not G**gle's fault, as other (non-G**gle) groups 
don't get updated either.


-leif

-- 
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] RAM to build Sage

[Volker Braun]

Just "# long time" would be enough IMHO. It should be understood that long 
doctests tend to consume more memory.



On Tuesday, May 6, 2014 11:26:47 AM UTC+2, John Cremona wrote:
>
> On 6 May 2014 10:15, Jeroen Demeyer > 
> wrote: 
> > On 2014-05-06 10:59, Julien Puydt wrote: 
> >> 
> >> The ARM chromebook I use has 2Gb RAM and some swap ; it can build sage, 
> >> but some tests can't run. I complained about it last year... 
> > 
> > Some tests (in particular, some related to elliptic curves) *do* need 
> more 
> > than 2GB of RAM. This is a known fact and I don't think it is considered 
> to 
> > be a bug. 
>
> If these tests are known, they could perhaps be tagged just as we tag 
> with "#long time" those which take a long time.  Something like "# 
> large RAM" required.  I don't know if this is possible though. 
>
> John 
>
> > 
> > Jeroen. 
> > 
> > 
> > -- 
> > 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. 
>

-- 
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] RAM to build Sage

[Volker Braun]

Just "# long time" would be enough IMHO. It should be understood that long 
doctests tend to consume more memory.



On Tuesday, May 6, 2014 11:26:47 AM UTC+2, John Cremona wrote:
>
> On 6 May 2014 10:15, Jeroen Demeyer > 
> wrote: 
> > On 2014-05-06 10:59, Julien Puydt wrote: 
> >> 
> >> The ARM chromebook I use has 2Gb RAM and some swap ; it can build sage, 
> >> but some tests can't run. I complained about it last year... 
> > 
> > Some tests (in particular, some related to elliptic curves) *do* need 
> more 
> > than 2GB of RAM. This is a known fact and I don't think it is considered 
> to 
> > be a bug. 
>
> If these tests are known, they could perhaps be tagged just as we tag 
> with "#long time" those which take a long time.  Something like "# 
> large RAM" required.  I don't know if this is possible though. 
>
> John 
>
> > 
> > Jeroen. 
> > 
> > 
> > -- 
> > 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. 
>

-- 
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: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

[Volker Braun]

If "make distclean" fails then $SAGE_LOCAL is not being deleted (it is the 
last command in the "distclean" target)



On Tuesday, May 6, 2014 9:36:59 AM UTC+2, Andrew wrote:
>
> Well, I'm completely confused as to why one of your recommendations above 
> was:
> I think you half-built Sage gcc conflicts with Apple gcc. Just "rm 
> -rf /usr/local/src/sage/local" and try again.
> A.
>
> On Tuesday, 6 May 2014 17:32:49 UTC+10, Volker Braun wrote:
>>
>> From the Makefile:
>>
>> distclean: clean doc-clean lib-clean bdist-clean
>> @echo "Deleting all remaining output from build system ..."
>> rm -rf local
>>
>>
>>
>> On Tuesday, May 6, 2014 9:30:03 AM UTC+2, Andrew wrote:
>>>
>>>
>>> Can you clarify what you mean here? "make distclean" should indeed 
 return the code to its pristine download state, except that it won't clean 
 up files in the "upstream" directory. Are there other things it doesn't 
 clean up which it should?

>>>
>>>  It doesn't remove the $SAGE_ROOT/local subdirectory either. I had the 
>>> impression that it was also running the configure script(s), but perhaps I 
>>> was wrong.
>>>
>>> Andrew
>>>
>>

-- 
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] Is there a problem with gmane?

[Simon King]

Hi!

Since I don't like the new google groups, I switched to using slrn and read 
the Sage groups in news.gmane.org.

However, no new message has shown up in the Sage-gmane groups since two 
days or so. What is the problem? In google-groups (which I use for this 
post) I see that there *are* new posts.

Best regards,
Simon

-- 
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] RAM to build Sage

[John Cremona]

On 6 May 2014 10:15, Jeroen Demeyer  wrote:
> On 2014-05-06 10:59, Julien Puydt wrote:
>>
>> The ARM chromebook I use has 2Gb RAM and some swap ; it can build sage,
>> but some tests can't run. I complained about it last year...
>
> Some tests (in particular, some related to elliptic curves) *do* need more
> than 2GB of RAM. This is a known fact and I don't think it is considered to
> be a bug.

If these tests are known, they could perhaps be tagged just as we tag
with "#long time" those which take a long time.  Something like "#
large RAM" required.  I don't know if this is possible though.

John

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

-- 
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] RAM to build Sage

[Jeroen Demeyer]

On 2014-05-06 10:59, Julien Puydt wrote:

The ARM chromebook I use has 2Gb RAM and some swap ; it can build sage,
but some tests can't run. I complained about it last year...
Some tests (in particular, some related to elliptic curves) *do* need 
more than 2GB of RAM. This is a known fact and I don't think it is 
considered to be a bug.


Jeroen.

--
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] RAM to build Sage

[Julien Puydt]

Hi,

Le 06/05/2014 00:14, William Stein a écrit :

Does anybody know how much RAM is required to build Sage these days.
  With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB
RAM results in failure (see below).  Of course, I'm not using swap,
and of course with swap you can do anything if you're willing to wait.
  That said, it would be very useful to have some sort of statement
about required RAM, like we now have for disk space: "Make sure you
have the dependencies and 5 GB of free disk space."


The ARM chromebook I use has 2Gb RAM and some swap ; it can build sage, 
but some tests can't run. I complained about it last year...


Snark on #sagemath

--
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: bug "make doc-pdf" fatal error

[John Cremona]

On 5 May 2014 22:06, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> 2014-05-05 20:47 UTC+02:00, John H Palmieri :
>>
>>
>> On Monday, May 5, 2014 11:01:37 AM UTC-7, John H Palmieri wrote:
>>>
>>> I think this bug has been fixed: see
>>> http://trac.sagemath.org/ticket/16153.
>>> As Vincent says, though, there seem to be other problems with the PDF
>>> documentation.
>>>
>>
>> Actually, I take that back. I just built the PDF docs for 6.2.rc1 without
>> any problems.
>
> Strange... I tried on 6.2.rc2...

I had no problems with make doc-pdf on 6.2.rc2 (ubuntu 12.04).

John

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

-- 
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: sage-cleaner issues? clean up .sage/temp?

[Volker Braun]

FWIW I wrote the logging precisely because the cleaner used to fail in 
funny ways that we never noticed because there was no output.



On Monday, May 5, 2014 8:46:52 PM UTC+2, John H Palmieri wrote:
>
> This surprised me a little bit:
>
> $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log 
> 3.6G/Users/palmieri/.sage/temp/jpalmieri/cleaner.log
>
> Is there any reason to have such a large file lying around? Should it be 
> automatically cleaned up every now and then?
>
> Also, I've noticed several times a "sage-cleaner" process which was 
> several days old. That's not supposed to happen anymore. For example, I saw 
> this today:
>
> $ ps ux | grep python
> palmieri 67905   0.0  0.1  2441608   7244   ??  SSat10AM  59:23.08 
> python 
> /Users/palmieri/Desktop/Sage_stuff/sage_builds/clean/sage-6.2.rc1/src/bin/sage-cleaner
>
> (Note that this was running in a built-from-tarball Sage 6.2.rc1, which 
> certainly contains the fix from #15457.)
>
> There were also several hundred directories in .sage/temp/jpalmieri/, with 
> names corresponding to old process IDs, long since dead. Some of these are 
> empty, some have sub-directories with names like "dir_3SAu4B". Shouldn't 
> all of these directories have been removed by sage-cleaner? I have noticed 
> that various Sage processes of mine have been getting killed mysteriously. 
> I wonder if it's an over-aggressive sage-cleaner, seeing an old directory 
> in .sage/temp/jpalmieri and killing a new process with the same pid.
>
> For what it's worth, this is on OS X 10.8 (and I think I've also seen it 
> on OS X 10.9).
>
> -- 
> John
>
>

-- 
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: html docbuilder hangs after first pass

[Volker Braun]

On Tuesday, May 6, 2014 3:18:56 AM UTC+2, Travis Scrimshaw wrote:Hey 
everyone,
>
>As the title states. I've run "make doc-clean" along with all known 
> variants (including single and multi threaded) "make", "sage -docbuild all 
> html", "make doc" (I've also run "sage -sync-build" too). I get some "gap: 
> unable to extend workspace" while trying to build the doc. 
>

Out of memory...

SAGE_NUM_THREADS=1 make doc

 

-- 
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: RAM to build Sage

[Volker Braun]

On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote:
>
> RAM results in failure (see below).  Of course, I'm not using swap, 
> and of course with swap you can do anything if you're willing to wait. 
>

Unix needs swap to back anon mmaps even if nothing is actually written to 
disk. Not having swap means you'll leave real ram unused (namely, the 
unused part of anno mmaps is forced into ram)

-- 
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: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

[Andrew]

Well, I'm completely confused as to why one of your recommendations above 
was:
I think you half-built Sage gcc conflicts with Apple gcc. Just "rm 
-rf /usr/local/src/sage/local" and try again.
A.

On Tuesday, 6 May 2014 17:32:49 UTC+10, Volker Braun wrote:
>
> From the Makefile:
>
> distclean: clean doc-clean lib-clean bdist-clean
> @echo "Deleting all remaining output from build system ..."
> rm -rf local
>
>
>
> On Tuesday, May 6, 2014 9:30:03 AM UTC+2, Andrew wrote:
>>
>>
>> Can you clarify what you mean here? "make distclean" should indeed return 
>>> the code to its pristine download state, except that it won't clean up 
>>> files in the "upstream" directory. Are there other things it doesn't clean 
>>> up which it should?
>>>
>>
>>  It doesn't remove the $SAGE_ROOT/local subdirectory either. I had the 
>> impression that it was also running the configure script(s), but perhaps I 
>> was wrong.
>>
>> Andrew
>>
>

-- 
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: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

[Volker Braun]

>From the Makefile:

distclean: clean doc-clean lib-clean bdist-clean
@echo "Deleting all remaining output from build system ..."
rm -rf local



On Tuesday, May 6, 2014 9:30:03 AM UTC+2, Andrew wrote:
>
>
> Can you clarify what you mean here? "make distclean" should indeed return 
>> the code to its pristine download state, except that it won't clean up 
>> files in the "upstream" directory. Are there other things it doesn't clean 
>> up which it should?
>>
>
>  It doesn't remove the $SAGE_ROOT/local subdirectory either. I had the 
> impression that it was also running the configure script(s), but perhaps I 
> was wrong.
>
> Andrew
>

-- 
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: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

[Andrew]

> Can you clarify what you mean here? "make distclean" should indeed return 
> the code to its pristine download state, except that it won't clean up 
> files in the "upstream" directory. Are there other things it doesn't clean 
> up which it should?
>

 It doesn't remove the $SAGE_ROOT/local subdirectory either. I had the 
impression that it was also running the configure script(s), but perhaps I 
was wrong.

Andrew

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