Re: [sage-devel] invisible contour lines in contour plots

[Whitcher, Ursula A.]

On 12/8/2015 4:04 PM, William Stein wrote:
>> Can we change the defaults so that fill=False does not default to
>> white-on-white?  Or add a keyword that will make all contour lines the same
>> color?  Or at least add an example about this to the documentation?
>>
>
> What does Mathematica do?
>
>https://reference.wolfram.com/language/ref/ContourPlot.html

Mathematica defaults to making all of the contour lines the same shade 
of gray, rather than coloring them to match the adjacent fill color.  So 
does Wolfram Alpha:

http://www.wolframalpha.com/input/?i=contour+plot+-10%28x^2%2By^2%29

UAW

-- 
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-edu] Python toolkit for music theory

[Rob Beezer]

lilypond uses TeX to create "engraved sheet music."  So I'd imagine it would 
create PDFs that could be converted to other formats.


From a cursory look it appears that  music21  has good support for MusicXML so 
that might be a way to interoperate between the pieces.


Sample (unencumbered) scores can be found in various formats at:

https://musescore.org/

Rob

On 12/08/2015 02:20 PM, William Stein wrote:

Installing music21 is trivial -- just use "pip install music21".  I
tried with SMC:

https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2015-12-08-141248-music21.sagews

However, to display music, one would need a way to get a png or svg
image written to a file; it would then be easy to display it inline by
doing smc.file('filename.png').

Question: Is there a way to save one of the music formats to an image
file?  How?  What other software (something called lilypond?) has to
be installed?

  -- William



On Tue, Dec 8, 2015 at 11:37 AM, kcrisman  wrote:

Possibly of interest to some people on these lists - I'd love to see Sage or
Jupyter notebooks using this:
http://web.mit.edu/music21/

--
You received this message because you are subscribed to the Google Groups
"sage-edu" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to sage-edu+unsubscr...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-edu.
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-edu] Python toolkit for music theory

[William Stein]

Installing music21 is trivial -- just use "pip install music21".  I
tried with SMC:

https://cloud.sagemath.com/projects/4a5f0542-5873-4eed-a85c-a18c706e8bcd/files/support/2015-12-08-141248-music21.sagews

However, to display music, one would need a way to get a png or svg
image written to a file; it would then be easy to display it inline by
doing smc.file('filename.png').

Question: Is there a way to save one of the music formats to an image
file?  How?  What other software (something called lilypond?) has to
be installed?

 -- William



On Tue, Dec 8, 2015 at 11:37 AM, kcrisman  wrote:
> Possibly of interest to some people on these lists - I'd love to see Sage or
> Jupyter notebooks using this:
> http://web.mit.edu/music21/
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-edu+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-edu.
> For more options, visit https://groups.google.com/d/optout.



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

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] invisible contour lines in contour plots

[William Stein]

On Tue, Dec 8, 2015 at 12:38 PM, Ursula Whitcher  wrote:
> In Sage's contour plots, the default colors shade from black to white.  This
> applies to both the shades used to fill and the actual color of the contour
> lines.  If you turn off the fill color, the highest contour will be
> white-on-white, and thus invisible.  Here's an example (notice the label
> floating apparently in the middle of nowhere):
>
> x,y = var('x,y')
> pl = contour_plot(-10*(x^2+y^2), (x,-1,1), (y,-1,1), fill = False, labels =
> True, label_fontsize = 13).show()
>
> You can fix this by making all the contour lines black.  The keyword
> cmap=[(0,0,0)] worked for me.
>
> Can we change the defaults so that fill=False does not default to
> white-on-white?  Or add a keyword that will make all contour lines the same
> color?  Or at least add an example about this to the documentation?
>

What does Mathematica do?

  https://reference.wolfram.com/language/ref/ContourPlot.html

Originally when implementing Sage graphics, we tried to very roughly
look at what Mathematica does (regarding their public API), and only
diverge from it when we could do something better (e.g., adding
graphics to superimpose them, which is pythonic).   This makes it
easier to switch back (and forth) between Sage and Mathematica. Of
course, many people involved in Sage graphics have never used
Mathematica and didn't even know that Mathematica inspired some of our
design.

 -- William

> --Ursula.
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



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

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] sage4 patchbot failure on #16929

[Dima Pasechnik]

I get a strange patchbot sage4 failure here: 
patchbot.sagemath.org/ticket/16929/
Looks like this is gentoo-specific. 
Jeroen, could you perhaps have a look at it offline and send me the 
detailed log, or
arrange for a login for me?

Dima

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] errors even in "make dist-clean"

[John Cremona]

On 8 Dec 2015 17:48, "Vincent Delecroix" <20100.delecr...@gmail.com> wrote:
>
> Try "make distclean" (there is no "-").
>

Ok, I'm not sure if i did that so will try.  Ubuntu.

>
> On 08/12/15 14:43, John Cremona wrote:
>>
>> I gave up trying to build a newly updated (from 6.9 to 6.10.beta7)
>> Sage from source since I got so many errors.  Even "make dist-clean"
>> fails as follows:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make dist-clean'):
>>
>> * package: backports_ssl_match_hostname-3.4.0.2
>>log file:
/home/jec/sage/logs/pkgs/backports_ssl_match_hostname-3.4.0.2.log
>>build directory:
>>
/home/jec/sage/local/var/tmp/sage/build/backports_ssl_match_hostname-3.4.0.2
>>
>> * package: certifi-14.05.14
>>log file: /home/jec/sage/logs/pkgs/certifi-14.05.14.log
>>build directory:
/home/jec/sage/local/var/tmp/sage/build/certifi-14.05.14
>>
>> * package: decorator-4.0.2
>>log file: /home/jec/sage/logs/pkgs/decorator-4.0.2.log
>>build directory:
/home/jec/sage/local/var/tmp/sage/build/decorator-4.0.2
>>
>> * package: jsonschema-2.4.0
>>log file: /home/jec/sage/logs/pkgs/jsonschema-2.4.0.log
>>build directory:
/home/jec/sage/local/var/tmp/sage/build/jsonschema-2.4.0
>>
>> * package: markupsafe-0.23
>>log file: /home/jec/sage/logs/pkgs/markupsafe-0.23.log
>>build directory:
/home/jec/sage/local/var/tmp/sage/build/markupsafe-0.23
>>
>> * package: setuptools_scm-1.7.0
>>log file: /home/jec/sage/logs/pkgs/setuptools_scm-1.7.0.log
>>build directory:
/home/jec/sage/local/var/tmp/sage/build/setuptools_scm-1.7.0
>>
>> * package: six-1.9.0
>>log file: /home/jec/sage/logs/pkgs/six-1.9.0.log
>>build directory: /home/jec/sage/local/var/tmp/sage/build/six-1.9.0
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> If I cannot even make dist-clean, what can I do?  I have no idea how
>> this situation was reached.  Should I just delete the entire directory
>> and start again?
>>
>> This is the reward I get for not building any versions of Sage for a
>> month or two and then trying to fix a bug!
>>
>> 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] invisible contour lines in contour plots

[Ursula Whitcher]

In Sage's contour plots, the default colors shade from black to white.  
This applies to both the shades used to fill and the actual color of the 
contour lines.  If you turn off the fill color, the highest contour will be 
white-on-white, and thus invisible.  Here's an example (notice the label 
floating apparently in the middle of nowhere):

x,y = var('x,y')
pl = contour_plot(-10*(x^2+y^2), (x,-1,1), (y,-1,1), fill = False, labels = 
True, label_fontsize = 13).show()

You can fix this by making all the contour lines black.  The keyword 
cmap=[(0,0,0)] worked for me.

Can we change the defaults so that fill=False does not default to 
white-on-white?  Or add a keyword that will make all contour lines the same 
color?  Or at least add an example about this to the documentation?

--Ursula.

-- 
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] Python toolkit for music theory

[kcrisman]

Possibly of interest to some people on these lists - I'd love to see Sage 
or Jupyter notebooks using this:
http://web.mit.edu/music21/

-- 
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: make distclean fails

[Jeroen Demeyer]

There is still this:

On 2015-12-07 20:55, David Coudert wrote:

configure: error: "found MacPorts in /opt/local/bin/port. Either:
(1) rename /opt/local and /sw, or
(2) change PATH and DYLD_LIBRARY_PATH
(Once Sage is built, you can restore them.)


--
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] errors even in "make dist-clean"

[Vincent Delecroix]

Try "make distclean" (there is no "-").

On 08/12/15 14:43, John Cremona wrote:

I gave up trying to build a newly updated (from 6.9 to 6.10.beta7)
Sage from source since I got so many errors.  Even "make dist-clean"
fails as follows:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make dist-clean'):

* package: backports_ssl_match_hostname-3.4.0.2
   log file: /home/jec/sage/logs/pkgs/backports_ssl_match_hostname-3.4.0.2.log
   build directory:
/home/jec/sage/local/var/tmp/sage/build/backports_ssl_match_hostname-3.4.0.2

* package: certifi-14.05.14
   log file: /home/jec/sage/logs/pkgs/certifi-14.05.14.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/certifi-14.05.14

* package: decorator-4.0.2
   log file: /home/jec/sage/logs/pkgs/decorator-4.0.2.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/decorator-4.0.2

* package: jsonschema-2.4.0
   log file: /home/jec/sage/logs/pkgs/jsonschema-2.4.0.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/jsonschema-2.4.0

* package: markupsafe-0.23
   log file: /home/jec/sage/logs/pkgs/markupsafe-0.23.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/markupsafe-0.23

* package: setuptools_scm-1.7.0
   log file: /home/jec/sage/logs/pkgs/setuptools_scm-1.7.0.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/setuptools_scm-1.7.0

* package: six-1.9.0
   log file: /home/jec/sage/logs/pkgs/six-1.9.0.log
   build directory: /home/jec/sage/local/var/tmp/sage/build/six-1.9.0

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

If I cannot even make dist-clean, what can I do?  I have no idea how
this situation was reached.  Should I just delete the entire directory
and start again?

This is the reward I get for not building any versions of Sage for a
month or two and then trying to fix a bug!

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] errors even in "make dist-clean"

[Nathann Cohen]

Are you using Mac OSX by any chance ?

David Coudert seems to have the same problem.

https://groups.google.com/d/topic/sage-devel/mjWgReiXIAc/discussion

It "started" with missing header files whose include directories were
removed recently from module_list.py (lrcalc and flint if I remember
correctly).

Nathann

On 8 December 2015 at 18:43, John Cremona  wrote:
> I gave up trying to build a newly updated (from 6.9 to 6.10.beta7)
> Sage from source since I got so many errors.  Even "make dist-clean"
> fails as follows:
>
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make dist-clean'):
>
> * package: backports_ssl_match_hostname-3.4.0.2
>   log file: /home/jec/sage/logs/pkgs/backports_ssl_match_hostname-3.4.0.2.log
>   build directory:
> /home/jec/sage/local/var/tmp/sage/build/backports_ssl_match_hostname-3.4.0.2
>
> * package: certifi-14.05.14
>   log file: /home/jec/sage/logs/pkgs/certifi-14.05.14.log
>   build directory: /home/jec/sage/local/var/tmp/sage/build/certifi-14.05.14
>
> * package: decorator-4.0.2
>   log file: /home/jec/sage/logs/pkgs/decorator-4.0.2.log
>   build directory: /home/jec/sage/local/var/tmp/sage/build/decorator-4.0.2
>
> * package: jsonschema-2.4.0
>   log file: /home/jec/sage/logs/pkgs/jsonschema-2.4.0.log
>   build directory: /home/jec/sage/local/var/tmp/sage/build/jsonschema-2.4.0
>
> * package: markupsafe-0.23
>   log file: /home/jec/sage/logs/pkgs/markupsafe-0.23.log
>   build directory: /home/jec/sage/local/var/tmp/sage/build/markupsafe-0.23
>
> * package: setuptools_scm-1.7.0
>   log file: /home/jec/sage/logs/pkgs/setuptools_scm-1.7.0.log
>   build directory: 
> /home/jec/sage/local/var/tmp/sage/build/setuptools_scm-1.7.0
>
> * package: six-1.9.0
>   log file: /home/jec/sage/logs/pkgs/six-1.9.0.log
>   build directory: /home/jec/sage/local/var/tmp/sage/build/six-1.9.0
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> If I cannot even make dist-clean, what can I do?  I have no idea how
> this situation was reached.  Should I just delete the entire directory
> and start again?
>
> This is the reward I get for not building any versions of Sage for a
> month or two and then trying to fix a bug!
>
> 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] errors even in "make dist-clean"

[John Cremona]

I gave up trying to build a newly updated (from 6.9 to 6.10.beta7)
Sage from source since I got so many errors.  Even "make dist-clean"
fails as follows:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make dist-clean'):

* package: backports_ssl_match_hostname-3.4.0.2
  log file: /home/jec/sage/logs/pkgs/backports_ssl_match_hostname-3.4.0.2.log
  build directory:
/home/jec/sage/local/var/tmp/sage/build/backports_ssl_match_hostname-3.4.0.2

* package: certifi-14.05.14
  log file: /home/jec/sage/logs/pkgs/certifi-14.05.14.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/certifi-14.05.14

* package: decorator-4.0.2
  log file: /home/jec/sage/logs/pkgs/decorator-4.0.2.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/decorator-4.0.2

* package: jsonschema-2.4.0
  log file: /home/jec/sage/logs/pkgs/jsonschema-2.4.0.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/jsonschema-2.4.0

* package: markupsafe-0.23
  log file: /home/jec/sage/logs/pkgs/markupsafe-0.23.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/markupsafe-0.23

* package: setuptools_scm-1.7.0
  log file: /home/jec/sage/logs/pkgs/setuptools_scm-1.7.0.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/setuptools_scm-1.7.0

* package: six-1.9.0
  log file: /home/jec/sage/logs/pkgs/six-1.9.0.log
  build directory: /home/jec/sage/local/var/tmp/sage/build/six-1.9.0

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

If I cannot even make dist-clean, what can I do?  I have no idea how
this situation was reached.  Should I just delete the entire directory
and start again?

This is the reward I get for not building any versions of Sage for a
month or two and then trying to fix a bug!

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] Re: Definition of multifactorial #5415

[Nils Bruin]

On Tuesday, December 8, 2015 at 5:56:36 AM UTC-8, prateek sharma wrote:
>
> Can you please summarize me what I basically need to do?
>
>
Read this:
 
http://doc.sagemath.org/html/en/developer/ 

and follow the workflow there to push a branch incorporating your changes 
to trac.sagemath.org.
The sage development workflow doesn't currently involve "pull requests" on 
github. Instead, you should make sure there's a branch on trac.sagemath.org 
and that that branch is registered on the relevant ticket. Then a potential 
reviewer knows where to find the code to be reviewed.

The "git-trac" command (documented there) helps performing a lot of the 
required steps. If you're more comfortable with using git directly then 
"git the hard way" might be useful doc.

Make sure you read "Sage Development Process" and "Sage Trac and tickets".

-- 
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: Definition of multifactorial #5415

[prateek sharma]

Can you please summarize me what I basically need to do?

On Saturday, December 5, 2015 at 3:30:33 PM UTC+5:30, Nathann Cohen wrote:
>
> > Please review the changes made. 
> > 
> https://github.com/prateekcs14/sage/commit/1d70630b6f878752fa342150d1e4c2e6c4777c4a
>  
>
> You may want to read this: 
> http://doc.sagemath.org/html/en/developer/index.html 
> 
>  
>
> Nathann 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] git trac timeout

[John Cremona]

I am getting timeouts from  g...@trac.sagemath.org -- is it just me?

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.