Dear William, On 19 Jun., 15:28, William Stein <[email protected]> wrote: > __init__.py and all.py weren't tested because I never put code and > examples in there, and didn't think anybody else would ever either, > and wanted to avoid wasting Sage startup time.
I see. The reason for me putting actual code into __init__.py is the layout of my package: The top level is a package "pGroupCohomology", that contains a constructor function for cohomology rings. This is how the user is supposed to create cohomology rings, and it does caching, so that cohomology rings become unique parents structures. The package also contains five Cython extension modules whose purpose is to provide all underlying basic classes (cohomology rings, cochains, chain maps, resolutions, ...); they are supposed to be in the background, and the user is supposed to not use them directly. Also, as a user, I prefer to have from pGroupCohomology import CohomologyRing instead of a lengthy from pGroupCohomology.cohomology import CohomologyRing By consequence, the documentation (including doc tests, of course) is on the level of the package, and further details can then be found on the level of the modules in the package. > Obviously I was wrong. See > > http://trac.sagemath.org/sage_trac/ticket/6108 Thank you! I hope that the problems with testing .pyx files that I mentioned in the other thread can be easily solved as well! Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
