Hi Vivianne,
2014-05-28 19:32 UTC+02:00, Viviane Pons <vivianep...@gmail.com>:
> I think we all agree on this idea now (that the decorator should not wrap
> the method), so there is no point in keeping the argument.
>
> Still, I have asked a few questions on which I'd like you guys opinions:
>
> - what's the best way to store this information? Nathan and Simon mentioned
> database, would this be a run time database? Or something persistent?
I am not sure a real database (e.g. sql or similar) would be the best.
The real question is how many maps you would like to handle ? If the
answer is below 50000 I would go for a pure Python datastructure
(dict, set and so).
> - Where to put the method to get the maps, right now it is a function
> hidden in some folder. I would like people to be able to see it when
> they're on the object, but it seems silly to add it manually to the object
> and yet, it shouldn't be on every object...
For me, it would makes sense on parents directly
{{{
sage: Permutations().known_maps_to(Partitions())
[...]
}}}
And in the methods known_maps_to and known_maps_from there should be
pointer on how to feed the database with more maps. But I would charge
the elements with that.
Vincent
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.
