Differences between revisions 139 and 140
Revision 139 as of 2008-06-17 23:42:47
Size: 3686
Editor: DavidRoe
Comment:
Revision 140 as of 2008-06-17 23:46:48
Size: 3443
Editor: robertwb
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
=== Sage has problems starting up with the code in this repository ===
Merge up at http://cython.org/coercion/hgwebdir.cgi/sage-coerce-3.0.3/ (pull on top of 3.0.3 release candidate)

I'm
not quite sure how to fix it.
Merge up at http://cython.org/coercion/hgwebdir.cgi/sage-coerce-3.0.3/ (pull on top of 3.0.3 release candidate) Should build and start without problems.
Line 16: Line 13:
=== Merge Issues ===

 * Matrix constructor rewritten, can't take gens and sequences anymore.
 * finite_field -> finite_field_prime_modn
 * gap_to_sage renamed in finite fields?

Line 30: Line 20:
 * integer_mod (robertwb)
Line 35: Line 26:
 * integer_mod

Merge up at http://cython.org/coercion/hgwebdir.cgi/sage-coerce-3.0.3/ (pull on top of 3.0.3 release candidate) Should build and start without problems.

Hint: If something doesn't work, try typing

sage: coercion_traceback()

which will give a listing of all errors caught in the coercion model.

Doctests

Done

In Progress

  • Integers, Rationals (roed)
  • integer_mod (robertwb)

To Do

  • complex, real
  • qqbar
  • monoids/modules
  • probability
  • games
  • catalogue, dsage, media, stats, server, logic, tests, misc, numerical
  • algebras
  • libs
  • quadratic forms
  • lfunctions
  • plot
  • ext
  • functions
  • databases
  • matrix
  • finite fields
  • coding
  • crypto
  • geometry
  • groups
  • interfaces
  • sets
  • calculus
  • combinat
  • rings/polynomial
  • misc
  • rings/padics
  • modular
  • graphs
  • schemes
  • rings/number_field
  • rings
  • categories

Todo (after merge):

  • abelian_grps
  • gsl ( dft.py -- abelian group failures )

Files to fix (Make all parents conform to the spec)

Useful script to list all parents in a given module that still need work: [attachment:list_parents.sage]

Nothing to do

  • catalogue, dsage, databases, ext, games, media, stats, server, plot, logic, tests lfunctions, misc, numerical,gsl, quadratic_forms

Done

In progress

  • groups
  • modular

Little to do

  • categories

Lots to do

Base classes

  • structure

Coercion doctesting

Comment from William:

teragon:sage was$ sage -coverage categories/action.pyx
structure/element.pyx structure/coerce.pyx |grep SCORE
SCORE categories/action.pyx: 0% (0 of 22)
SCORE structure/element.pyx: 18% (28 of 153)
SCORE structure/coerce.pyx: 2% (1 of 39)

I tried to understand and use the coercion model code to trac down the issue with #2079 and
was amazed at how nonexistent the doctesting and documentation of
functions is there.
In order for people to write lots of coercion code all of Sage, it's critical that they can
read the coercion model code so they can track down -- for themselves -- what is going
wrong when they run into trouble.  I would put getting the coverage of the above files
(and whatever else is related to coercion) up to 100% as the first step in your coercion
model stuff.   Seriously.   And don't say it can't be doctested, since even though there are
a lot of things not easily accessible now from the interpreter, such as the coercion model

Categories to implement

Old notes

To start, get a copy of Sage 2.10.1, install the latest cython spkg (available at http://sage.math.washington.edu/home/robertwb/cython/), pull from http://cython.org/coercion/hgwebdir.cgi/sage-coerce/ and build.

Import [attachment:fix-random.patch] to sage-scripts to ignore random tests.

days7/coercion/todo (last edited 2009-07-29 19:16:15 by robertwb)