Open MareoRaft opened 6 years ago
Now using migration
branch for this. Which will probably be merged with master frequently.
how many tests to move over, omit the newest untested functions
START MIGRATING
ask about "this" terminology for classes in ticket. also note about UniqueRepresentation
where sensible in ticket.
Partition.py migrated, waiting on review. We can now create a skew_partition
branch off the partition
branch, a k_shape
branch off the skew_partition
branch, and so forth.
We can work on those branches even though we are waiting on partition. Then merge in changes as necessary.
There are a number of last-minute "cleanup" things to do before adding code to sage itself. So I don't forget, I maintain a list here:
done
algorithm
instead ofmethod
when there is a choice of how to calculate (https://doc.sagemath.org/html/en/developer/coding_basics.html#miscellanous-minor-things) --> donecheck
to decide whether or not to verify input parameters --> donealmost done
dual_k_catalan_function
. stuff after that won't be migrated now anywaycan't do it
UniqueRepresentation
where sensible --> can't get this to workduring migrate
from sage.measure_theory.all import *
for your stuff. (see also https://doc.sagemath.org/html/en/developer/coding_basics.html) --> wait on migratehl_creation_operator
, finite dimensional free algebra, other free algebra) should get a SEEALSO that points to my functionslast of migrate
after migrate